All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@redhat.com>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: GEM - radeon cs ioctl deadlock
Date: Thu, 14 Oct 2010 08:14:58 +1000	[thread overview]
Message-ID: <1287008098.4928.9.camel@clockmaker-el6> (raw)
In-Reply-To: <AANLkTimbZ8E7pWD3SnCs6vnnG3U93X7AmzrJVtRPVuEJ@mail.gmail.com>

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.

Dave.

  reply	other threads:[~2010-10-13 22:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 21:57 GEM - radeon cs ioctl deadlock Jerome Glisse
2010-10-13 22:14 ` Dave Airlie [this message]
2010-10-14  1:47   ` Ben Skeggs
2010-10-18 15:16     ` Thomas Hellstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1287008098.4928.9.camel@clockmaker-el6 \
    --to=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=j.glisse@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.