[Nouveau] [PATCH 09/17] drm/radeon: use common fence implementation for fences

Daniel Vetter daniel.vetter at ffwll.ch
Wed Jul 23 01:42:14 PDT 2014


On Wed, Jul 23, 2014 at 10:25 AM, Maarten Lankhorst
<maarten.lankhorst at canonical.com> wrote:
> In this case if the sync was to i915 the i915 lockup procedure would take care of itself. It wouldn't fix radeon, but it would at least unblock your intel card again. I haven't specifically added a special case to attempt to unblock external fences, but I've considered it. :-)

Actually the i915 reset stuff relies crucially on being able to kick
all waiters holding driver locks. Since the current fence code only
exposes an opaque wait function without exposing the underlying wait
queue we won't be able to sleep on both the fence queue and the reset
queue. So would pose a problem if we add fence_wait calls to our
driver.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch


More information about the dri-devel mailing list