lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAKMK7uGLqzePAREsWhX0D1oN4FdqKwPgAL6x8sULpJSqYH5LwA@mail.gmail.com> Date: Wed, 23 Jul 2014 10:42:14 +0200 From: Daniel Vetter <daniel.vetter@...ll.ch> To: Maarten Lankhorst <maarten.lankhorst@...onical.com> Cc: Christian König <christian.koenig@....com>, Christian König <deathsimple@...afone.de>, Thomas Hellstrom <thellstrom@...are.com>, nouveau <nouveau@...ts.freedesktop.org>, LKML <linux-kernel@...r.kernel.org>, dri-devel <dri-devel@...ts.freedesktop.org>, Ben Skeggs <bskeggs@...hat.com>, "Deucher, Alexander" <alexander.deucher@....com> Subject: Re: [Nouveau] [PATCH 09/17] drm/radeon: use common fence implementation for fences On Wed, Jul 23, 2014 at 10:25 AM, Maarten Lankhorst <maarten.lankhorst@...onical.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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists