Am 23.07.2014 10:42, schrieb Daniel Vetter: > 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.
And apart from that I really think that I misunderstood Maarten. But his explanation sounds like i915 would do a reset because Radeon is locked up, right? Well if that's really the case then I would question the interface even more, cause that is really nonsense. Christian. > -Daniel
