[PATCH 13/13] drm/radeon: rework recursive gpu reset handling

Dave Airlie airlied at gmail.com
Thu Apr 19 23:57:09 PDT 2012

2012/4/19 Christian König <deathsimple at vodafone.de>:
> Instead of all this humpy pumpy with recursive
> mutex (which also fixes only halve of the problem)
> move the actual gpu reset out of the fence code,
> return -EDEADLK and then reset the gpu in the
> calling ioctl function.

I'm trying to figure out if this has any disadvantages over doing what
I proposed before and just kicking a thread to reset the gpu.

It seems like this should also avoid the locking problems, I'd like to
make sure we don't return -EDEADLK to userspace by accident anywhere,
since I don't think it prepared for it and it would be an ABI change.


More information about the dri-devel mailing list