dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/9] drm: remove prime sg_table caching
Date: Wed, 8 May 2019 11:57:50 +0200	[thread overview]
Message-ID: <20190508095749.GW17751@phenom.ffwll.local> (raw)
In-Reply-To: <20190507081338.2571-3-christian.koenig@amd.com>

On Tue, May 07, 2019 at 10:13:32AM +0200, Christian König wrote:
> That is now done by the DMA-buf helpers instead.
> 
> Signed-off-by: Christian König <christian.koenig@amd.com>
> ---
>  drivers/gpu/drm/drm_prime.c | 76 ++++++++-----------------------------
>  1 file changed, 16 insertions(+), 60 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c
> index 231e3f6d5f41..90f5230cc0d5 100644
> --- a/drivers/gpu/drm/drm_prime.c
> +++ b/drivers/gpu/drm/drm_prime.c
> @@ -86,11 +86,6 @@ struct drm_prime_member {
>  	struct rb_node handle_rb;
>  };
>  
> -struct drm_prime_attachment {
> -	struct sg_table *sgt;
> -	enum dma_data_direction dir;
> -};
> -
>  static int drm_prime_add_buf_handle(struct drm_prime_file_private *prime_fpriv,
>  				    struct dma_buf *dma_buf, uint32_t handle)
>  {
> @@ -188,25 +183,16 @@ static int drm_prime_lookup_buf_handle(struct drm_prime_file_private *prime_fpri
>   * @dma_buf: buffer to attach device to
>   * @attach: buffer attachment data
>   *
> - * Allocates &drm_prime_attachment and calls &drm_driver.gem_prime_pin for
> - * device specific attachment. This can be used as the &dma_buf_ops.attach
> - * callback.
> + * Calls &drm_driver.gem_prime_pin for device specific handling. This can be
> + * used as the &dma_buf_ops.attach callback.
>   *
>   * Returns 0 on success, negative error code on failure.
>   */
>  int drm_gem_map_attach(struct dma_buf *dma_buf,
>  		       struct dma_buf_attachment *attach)
>  {
> -	struct drm_prime_attachment *prime_attach;
>  	struct drm_gem_object *obj = dma_buf->priv;
>  
> -	prime_attach = kzalloc(sizeof(*prime_attach), GFP_KERNEL);
> -	if (!prime_attach)
> -		return -ENOMEM;
> -
> -	prime_attach->dir = DMA_NONE;
> -	attach->priv = prime_attach;
> -
>  	return drm_gem_pin(obj);
>  }
>  EXPORT_SYMBOL(drm_gem_map_attach);
> @@ -222,26 +208,8 @@ EXPORT_SYMBOL(drm_gem_map_attach);
>  void drm_gem_map_detach(struct dma_buf *dma_buf,
>  			struct dma_buf_attachment *attach)
>  {
> -	struct drm_prime_attachment *prime_attach = attach->priv;
>  	struct drm_gem_object *obj = dma_buf->priv;
>  
> -	if (prime_attach) {
> -		struct sg_table *sgt = prime_attach->sgt;
> -
> -		if (sgt) {
> -			if (prime_attach->dir != DMA_NONE)
> -				dma_unmap_sg_attrs(attach->dev, sgt->sgl,
> -						   sgt->nents,
> -						   prime_attach->dir,
> -						   DMA_ATTR_SKIP_CPU_SYNC);
> -			sg_free_table(sgt);
> -		}
> -
> -		kfree(sgt);
> -		kfree(prime_attach);
> -		attach->priv = NULL;
> -	}
> -
>  	drm_gem_unpin(obj);
>  }
>  EXPORT_SYMBOL(drm_gem_map_detach);
> @@ -286,39 +254,22 @@ void drm_prime_remove_buf_handle_locked(struct drm_prime_file_private *prime_fpr
>  struct sg_table *drm_gem_map_dma_buf(struct dma_buf_attachment *attach,
>  				     enum dma_data_direction dir)
>  {
> -	struct drm_prime_attachment *prime_attach = attach->priv;
>  	struct drm_gem_object *obj = attach->dmabuf->priv;
>  	struct sg_table *sgt;
>  
> -	if (WARN_ON(dir == DMA_NONE || !prime_attach))
> +	if (WARN_ON(dir == DMA_NONE))
>  		return ERR_PTR(-EINVAL);
>  
> -	/* return the cached mapping when possible */
> -	if (prime_attach->dir == dir)
> -		return prime_attach->sgt;
> -
> -	/*
> -	 * two mappings with different directions for the same attachment are
> -	 * not allowed
> -	 */
> -	if (WARN_ON(prime_attach->dir != DMA_NONE))
> -		return ERR_PTR(-EBUSY);
> -
>  	if (obj->funcs)
>  		sgt = obj->funcs->get_sg_table(obj);
>  	else
>  		sgt = obj->dev->driver->gem_prime_get_sg_table(obj);
>  
> -	if (!IS_ERR(sgt)) {
> -		if (!dma_map_sg_attrs(attach->dev, sgt->sgl, sgt->nents, dir,
> -				      DMA_ATTR_SKIP_CPU_SYNC)) {
> -			sg_free_table(sgt);
> -			kfree(sgt);
> -			sgt = ERR_PTR(-ENOMEM);
> -		} else {
> -			prime_attach->sgt = sgt;
> -			prime_attach->dir = dir;
> -		}
> +	if (!dma_map_sg_attrs(attach->dev, sgt->sgl, sgt->nents, dir,
> +			      DMA_ATTR_SKIP_CPU_SYNC)) {
> +		sg_free_table(sgt);
> +		kfree(sgt);
> +		sgt = ERR_PTR(-ENOMEM);
>  	}
>  
>  	return sgt;
> @@ -331,14 +282,19 @@ EXPORT_SYMBOL(drm_gem_map_dma_buf);
>   * @sgt: scatterlist info of the buffer to unmap
>   * @dir: direction of DMA transfer
>   *
> - * Not implemented. The unmap is done at drm_gem_map_detach().  This can be
> - * used as the &dma_buf_ops.unmap_dma_buf callback.
> + * This can be used as the &dma_buf_ops.unmap_dma_buf callback.
>   */
>  void drm_gem_unmap_dma_buf(struct dma_buf_attachment *attach,
>  			   struct sg_table *sgt,
>  			   enum dma_data_direction dir)
>  {
> -	/* nothing to be done here */
> +	if (!sgt)
> +		return;

This copypasta isn't needed anymore, it's a caller bug if you don't supply
an sgt here. The old caching code only needed it because it only cached
on-demand in the map callback. With that:

Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>


> +
> +	dma_unmap_sg_attrs(attach->dev, sgt->sgl, sgt->nents, dir,
> +			   DMA_ATTR_SKIP_CPU_SYNC);
> +	sg_free_table(sgt);
> +	kfree(sgt);
>  }
>  EXPORT_SYMBOL(drm_gem_unmap_dma_buf);
>  
> -- 
> 2.17.1
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-05-08  9:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07  8:13 [PATCH 1/9] dma-buf: start caching of sg_table objects Christian König
2019-05-07  8:13 ` [PATCH 2/9] dma-buf: add dynamic DMA-buf handling v7 Christian König
2019-05-08  9:51   ` Daniel Vetter
2019-05-07  8:13 ` [PATCH 3/9] drm: remove prime sg_table caching Christian König
2019-05-08  9:57   ` Daniel Vetter [this message]
2019-05-08 11:19     ` Christian König
2019-05-07  8:13 ` [PATCH 4/9] drm/ttm: remove the backing store if no placement is given Christian König
2019-05-07  8:13 ` [PATCH 5/9] drm/ttm: use the parent resv for ghost objects Christian König
2019-05-07  8:13 ` [PATCH 6/9] drm/amdgpu: use allowed_domains for exported DMA-bufs Christian König
2019-05-07  8:13 ` [PATCH 7/9] drm/amdgpu: add independent DMA-buf export v3 Christian König
2019-05-07  8:13 ` [PATCH 8/9] drm/amdgpu: add independent DMA-buf import v5 Christian König
2019-05-07  8:13 ` [PATCH 9/9] drm/amdgpu: add DMA-buf invalidation callback v2 Christian König
2019-05-08  9:15 ` [PATCH 1/9] dma-buf: start caching of sg_table objects Daniel Vetter
2019-05-08 10:11   ` Daniel Vetter
2019-05-08 12:00     ` Christian König
2019-05-08 12:15       ` Daniel Vetter
2019-05-08 12:23         ` Koenig, Christian
2019-05-08 12:44           ` Daniel Vetter
2019-05-08 11:13   ` Christian König

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=20190508095749.GW17751@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=ckoenig.leichtzumerken@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox