Am 23.07.2014 10:07, schrieb Daniel Vetter:
On Wed, Jul 23, 2014 at 9:58 AM, Christian König
<deathsimple@xxxxxxxxxxx> 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.
Yeah, especially with multimedia application. But I don't really care
about this problem because the next time an application tries to use the
block in question we actually do the reset and everything is fine.
In your example we would do the reset when the next X server starts,
before that point nobody would care because nobody uses the hardware.
An additional problem here is that resets are something perfect normal
for radeon. For example UVD can "crash" when you feed it with invalid
bitstream data, (ok actually it send an interrupt and stops any
processing for the driver to investigate). To continue processing you
need to go through a rather complicated reset procedure.
Christian.
-Daniel
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel
