GEM - radeon cs ioctl deadlock
airlied at redhat.com
Wed Oct 13 15:14:58 PDT 2010
On Wed, 2010-10-13 at 17:57 -0400, Jerome Glisse wrote:
> So we are facing a deadlock with the radeon cs ioctl. When a buffer is given
> a name (with flink) we could endup with 2 handle pointing to the same
> object (flink object and open it from same file descriptor). Would it be ok
> if i change gem open to first look if we already have an handle for the
> object and to use that handle instead of creating a new one ? Or could
> this break intel driver ?
I think r300g worked around this already, maybe we should just avoid
doing it from userspace if possible.
More information about the dri-devel