Messages in this thread | | | Date | Wed, 23 Jul 2014 10:07:09 +0200 | Subject | Re: [Nouveau] [PATCH 09/17] drm/radeon: use common fence implementation for fences | From | Daniel Vetter <> |
| |
On Wed, Jul 23, 2014 at 9:58 AM, Christian König <deathsimple@vodafone.de> wrote: > Just imagine an application using prime is locking up Radeon and because of > that gets killed by the user. Nothing else in the system would use the > Radeon hardware any more and so radeon gets only called by another driver > waiting patiently for radeon to finish rendering which never happens because > the whole thing is locked up and we don't get a chance to recover.
But isn't that possible already without fences? X hangs radeon, user crashes X for unrelated reasons before radeon will notice the hang. Then no one uses radeon any longer and the hang stays undetected. -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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |