Nicolai Haehnle wrote:
I think the simplest solution would look something like this:
Whenever DRM(lock) is called by a privileged client (i.e. the X server), and it needs to sleep because the lock is held by an unprivileged client, a watchdog timer is started before we schedule. DRM(unlock) unconditionally stops this watchdog timer.
When the watchdog timer fires, it releases the lock and/or kills the offending DRI client.
This sounds reasonable to me. This will help with /some/ buggy driver cases that end-users may see. Like Keith said, it won't help developers much. Like Michel said, it won't help at all when the chip is "crashed". Unfortunately, that is the most common case where the lock is held for a long time.
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
