From: Chris Wilson <chris@chris-wilson.co.uk>
To: Dave Airlie <airlied@gmail.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/prime: add exported buffers to current fprivs imported buffer list
Date: Mon, 21 May 2012 09:36:56 +0100 [thread overview]
Message-ID: <1337589423_155137@CP5-2952> (raw)
In-Reply-To: <1337585114-22148-1-git-send-email-airlied@gmail.com>
On Mon, 21 May 2012 08:25:14 +0100, Dave Airlie <airlied@gmail.com> wrote:
> From: Dave Airlie <airlied@redhat.com>
>
> If userspace attempts to import a buffer it exported on the same device,
> we need to return the same GEM handle for it, not a new handle pointing
> at the same GEM object.
>
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> ---
> drivers/gpu/drm/drm_gem.c | 16 ++++++++++++++--
> drivers/gpu/drm/drm_prime.c | 12 ++++++++++++
> 2 files changed, 26 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c
> index 1ab29a7..9cc3761 100644
> --- a/drivers/gpu/drm/drm_gem.c
> +++ b/drivers/gpu/drm/drm_gem.c
> @@ -233,9 +233,15 @@ drm_gem_handle_delete(struct drm_file *filp, u32 handle)
> idr_remove(&filp->object_idr, handle);
> spin_unlock(&filp->table_lock);
>
> - if (obj->import_attach)
> + if (obj->import_attach) {
> drm_prime_remove_imported_buf_handle(&filp->prime,
> obj->import_attach->dmabuf);
> + }
> + if (obj->export_dma_buf) {
> + drm_prime_remove_imported_buf_handle(&filp->prime,
> + obj->export_dma_buf);
> + obj->export_dma_buf = NULL;
Any particular reason for nullifying the pointer here and nowhere else
along this free path?
> + }
>
> if (dev->driver->gem_close_object)
> dev->driver->gem_close_object(obj, filp);
> @@ -530,9 +536,15 @@ drm_gem_object_release_handle(int id, void *ptr, void *data)
> struct drm_gem_object *obj = ptr;
> struct drm_device *dev = obj->dev;
>
> - if (obj->import_attach)
> + if (obj->import_attach) {
> drm_prime_remove_imported_buf_handle(&file_priv->prime,
> obj->import_attach->dmabuf);
> + }
> + if (obj->export_dma_buf) {
> + drm_prime_remove_imported_buf_handle(&file_priv->prime,
> + obj->export_dma_buf);
> + obj->export_dma_buf = NULL;
> + }
Strongly suggests wrapping this into a small function to undo prime for
a handle and avoiding the duplicate code.
>
> if (dev->driver->gem_close_object)
> dev->driver->gem_close_object(obj, file_priv);
> diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c
> index c35e585..c06f0f0 100644
> --- a/drivers/gpu/drm/drm_prime.c
> +++ b/drivers/gpu/drm/drm_prime.c
> @@ -68,6 +68,7 @@ int drm_gem_prime_handle_to_fd(struct drm_device *dev,
> {
> struct drm_gem_object *obj;
> void *buf;
> + int ret;
>
> obj = drm_gem_object_lookup(dev, file_priv, handle);
> if (!obj)
> @@ -100,6 +101,17 @@ int drm_gem_prime_handle_to_fd(struct drm_device *dev,
> obj->export_dma_buf = buf;
> *prime_fd = dma_buf_fd(buf, flags);
> }
> + /* if we've exported this buffer the cheat and add it to the import list
> + * so we get the correct handle back
> + */
s/the/then/
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2012-05-21 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 7:25 [PATCH] drm/prime: add exported buffers to current fprivs imported buffer list Dave Airlie
2012-05-21 8:36 ` Chris Wilson [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=1337589423_155137@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
/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.