dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Zhang, Jerry (Junwei)" <Jerry.Zhang@amd.com>,
	daniel@ffwll.ch, sumit.semwal@linaro.org,
	dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
	linaro-mm-sig@lists.linaro.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/4] dma-buf: add dma_buf_(un)map_attachment_locked variants v2
Date: Tue, 3 Jul 2018 13:37:00 +0200	[thread overview]
Message-ID: <0e247a50-4fae-a9d3-1e1f-d07bb076ecf7@gmail.com> (raw)
In-Reply-To: <5B34AFFC.6080805@amd.com>

Am 28.06.2018 um 11:53 schrieb Zhang, Jerry (Junwei):
> On 06/22/2018 10:11 PM, Christian König wrote:
>> Add function variants which can be called with the reservation lock
>> already held.
>>
>> v2: reordered, add lockdep asserts, fix kerneldoc
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> ---
>>   drivers/dma-buf/dma-buf.c | 57 
>> +++++++++++++++++++++++++++++++++++++++++++++++
>>   include/linux/dma-buf.h   |  5 +++++
>>   2 files changed, 62 insertions(+)
>>
>> diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
>> index 852a3928ee71..dc94e76e2e2a 100644
>> --- a/drivers/dma-buf/dma-buf.c
>> +++ b/drivers/dma-buf/dma-buf.c
>> @@ -606,6 +606,40 @@ void dma_buf_detach(struct dma_buf *dmabuf, 
>> struct dma_buf_attachment *attach)
>>   }
>>   EXPORT_SYMBOL_GPL(dma_buf_detach);
>>
>> +/**
>> + * dma_buf_map_attachment_locked - Maps the buffer into _device_ 
>> address space
>> + * with the reservation lock held. Is a wrapper for map_dma_buf() of 
>> the
>> + *
>> + * Returns the scatterlist table of the attachment;
>> + * dma_buf_ops.
>> + * @attach:    [in]    attachment whose scatterlist is to be returned
>> + * @direction:    [in]    direction of DMA transfer
>> + *
>> + * Returns sg_table containing the scatterlist to be returned; 
>> returns ERR_PTR
>> + * on error. May return -EINTR if it is interrupted by a signal.
>> + *
>> + * A mapping must be unmapped by using 
>> dma_buf_unmap_attachment_locked(). Note
>> + * that the underlying backing storage is pinned for as long as a 
>> mapping
>> + * exists, therefore users/importers should not hold onto a mapping 
>> for undue
>> + * amounts of time.
>> + */
>> +struct sg_table *
>> +dma_buf_map_attachment_locked(struct dma_buf_attachment *attach,
>> +                  enum dma_data_direction direction)
>> +{
>> +    struct sg_table *sg_table;
>> +
>
> Perhaps better to add some error check, like dma_buf_map_attachment()
>
> WARN_ON(!attach || !attach->dmabuf)

Actually I wanted to remove those from the other functions as well.

WARN_ON and BUG_ON checks for NULL pointers before using them are 
totally pointless because they have the same effect as a crash.

Regards,
Christian.

>
> Apart from that, it's
> Reviewed-by: Junwei Zhang <Jerry.Zhang@amd.com>
>
> Jerry
>
>> +    might_sleep();
>> +    reservation_object_assert_held(attach->dmabuf->resv);
>> +
>> +    sg_table = attach->dmabuf->ops->map_dma_buf(attach, direction);
>> +    if (!sg_table)
>> +        sg_table = ERR_PTR(-ENOMEM);
>> +
>> +    return sg_table;
>> +}
>> +EXPORT_SYMBOL_GPL(dma_buf_map_attachment_locked);
>> +
>>   /**
>>    * dma_buf_map_attachment - Returns the scatterlist table of the 
>> attachment;
>>    * mapped into _device_ address space. Is a wrapper for 
>> map_dma_buf() of the
>> @@ -639,6 +673,29 @@ struct sg_table *dma_buf_map_attachment(struct 
>> dma_buf_attachment *attach,
>>   }
>>   EXPORT_SYMBOL_GPL(dma_buf_map_attachment);
>>
>> +/**
>> + * dma_buf_unmap_attachment_locked - unmaps the buffer with 
>> reservation lock
>> + * held, should deallocate the associated scatterlist. Is a wrapper for
>> + * unmap_dma_buf() of dma_buf_ops.
>> + * @attach:    [in]    attachment to unmap buffer from
>> + * @sg_table:    [in]    scatterlist info of the buffer to unmap
>> + * @direction:  [in]    direction of DMA transfer
>> + *
>> + * This unmaps a DMA mapping for @attached obtained by
>> + * dma_buf_map_attachment_locked().
>> + */
>> +void dma_buf_unmap_attachment_locked(struct dma_buf_attachment *attach,
>> +                     struct sg_table *sg_table,
>> +                     enum dma_data_direction direction)
>> +{
>> +    might_sleep();
>> +    reservation_object_assert_held(attach->dmabuf->resv);
>> +
>> +    attach->dmabuf->ops->unmap_dma_buf(attach, sg_table,
>> +                        direction);
>> +}
>> +EXPORT_SYMBOL_GPL(dma_buf_unmap_attachment_locked);
>> +
>>   /**
>>    * dma_buf_unmap_attachment - unmaps and decreases usecount of the 
>> buffer;might
>>    * deallocate the scatterlist associated. Is a wrapper for 
>> unmap_dma_buf() of
>> diff --git a/include/linux/dma-buf.h b/include/linux/dma-buf.h
>> index 991787a03199..a25e754ae2f7 100644
>> --- a/include/linux/dma-buf.h
>> +++ b/include/linux/dma-buf.h
>> @@ -384,8 +384,13 @@ int dma_buf_fd(struct dma_buf *dmabuf, int flags);
>>   struct dma_buf *dma_buf_get(int fd);
>>   void dma_buf_put(struct dma_buf *dmabuf);
>>
>> +struct sg_table *dma_buf_map_attachment_locked(struct 
>> dma_buf_attachment *,
>> +                           enum dma_data_direction);
>>   struct sg_table *dma_buf_map_attachment(struct dma_buf_attachment *,
>>                       enum dma_data_direction);
>> +void dma_buf_unmap_attachment_locked(struct dma_buf_attachment *,
>> +                     struct sg_table *,
>> +                     enum dma_data_direction);
>>   void dma_buf_unmap_attachment(struct dma_buf_attachment *, struct 
>> sg_table *,
>>                   enum dma_data_direction);
>>   int dma_buf_begin_cpu_access(struct dma_buf *dma_buf,
>>

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-07-03 11:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 14:10 First step towards unpinned DMA-buf operation Christian König
2018-06-22 14:11 ` [PATCH 1/4] dma-buf: add dma_buf_(un)map_attachment_locked variants v2 Christian König
2018-06-25  8:15   ` Daniel Vetter
2018-06-28  9:44   ` Zhang, Jerry (Junwei)
2018-06-28  9:53   ` Zhang, Jerry (Junwei)
2018-07-03 11:37     ` Christian König [this message]
2018-06-22 14:11 ` [PATCH 2/4] dma-buf: lock the reservation object during (un)map_dma_buf v2 Christian König
2018-06-25  8:22   ` Daniel Vetter
2018-06-25  9:12     ` Daniel Vetter
2018-07-03 11:46       ` Christian König
2018-07-03 12:52         ` Daniel Vetter
2018-07-03 13:02           ` Christian König
2018-07-03 13:11             ` Daniel Vetter
2018-07-03 13:31               ` Christian König
2018-06-28  9:53   ` Zhang, Jerry (Junwei)
2018-06-22 14:11 ` [PATCH 3/4] drm/amdgpu: add independent DMA-buf export v3 Christian König
2018-06-28  9:58   ` Zhang, Jerry (Junwei)
2018-07-03 11:35     ` Christian König
2018-06-22 14:11 ` [PATCH 4/4] drm/amdgpu: add independent DMA-buf import v4 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=0e247a50-4fae-a9d3-1e1f-d07bb076ecf7@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=Jerry.Zhang@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sumit.semwal@linaro.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;
as well as URLs for NNTP newsgroup(s).