From: Daniel Vetter <daniel@ffwll.ch>
To: John Cox <jc@kynesim.co.uk>
Cc: Simon Ser <contact@emersion.fr>, dri-devel@lists.freedesktop.org
Subject: Re: Should multiple PRIME_FD_TO_HANDLE ioctls on the same fd require multiple GEM_CLOSE?
Date: Wed, 13 Oct 2021 15:28:35 +0200 [thread overview]
Message-ID: <YWbfA+8tp5FuKh2s@phenom.ffwll.local> (raw)
In-Reply-To: <oalbmg9okjpuieqo8fl8b890h1a7sflv94@4ax.com>
On Tue, Oct 12, 2021 at 07:37:11PM +0100, John Cox wrote:
> On Tue, 12 Oct 2021 17:33:18 +0000, you wrote:
>
> >Yes, this is expected behavior, even if it's not intuitive. For more
> >details, see:
> >
> >https://gitlab.freedesktop.org/mesa/drm/-/merge_requests/110
>
> Thanks - as noted in that discussion the behaviour is a bit unhelpful
> but just knowing that it is expected means I can deal with it.
kerneldoc in that uapi header to explain precisely what and why is going
on would be good too.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2021-10-13 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 13:42 Should multiple PRIME_FD_TO_HANDLE ioctls on the same fd require multiple GEM_CLOSE? John Cox
2021-10-12 17:33 ` Simon Ser
2021-10-12 18:37 ` John Cox
2021-10-13 13:28 ` Daniel Vetter [this message]
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=YWbfA+8tp5FuKh2s@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=jc@kynesim.co.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox