From: Huan Yang <link@vivo.com>
To: "Kasireddy, Vivek" <vivek.kasireddy@intel.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "opensource.kernel@vivo.com" <opensource.kernel@vivo.com>
Subject: Re: [PATCH v5 5/7] udmabuf: introduce udmabuf init and deinit helper
Date: Fri, 6 Sep 2024 16:38:52 +0800 [thread overview]
Message-ID: <5970129f-5787-424f-ad7c-ee8568a1734b@vivo.com> (raw)
In-Reply-To: <IA0PR11MB7185D06C33DEB9E1BC05EF95F89E2@IA0PR11MB7185.namprd11.prod.outlook.com>
在 2024/9/6 16:20, Kasireddy, Vivek 写道:
> Hi Huan,
>
>> Subject: [PATCH v5 5/7] udmabuf: introduce udmabuf init and deinit helper
>>
>> After udmabuf is allocated, its resources need to be initialized,
>> including various array structures. The current array structure has
>> already been greatly expanded.
>>
>> Also, before udmabuf needs to be kfree, the occupied resources need to
>> be released.
>>
>> This part is repetitive and maybe overlooked.
>>
>> This patch give a helper function when init and deinit, by this,
>> deduce duplicate code.
> *reduce
>
> If possible, please try to improve the wording and grammatical correctness
> in the commit messages of other patches as well.
I'll fix it in next-version
>
>> Signed-off-by: Huan Yang <link@vivo.com>
>> ---
>> drivers/dma-buf/udmabuf.c | 52 +++++++++++++++++++++++----------------
>> 1 file changed, 31 insertions(+), 21 deletions(-)
>>
>> diff --git a/drivers/dma-buf/udmabuf.c b/drivers/dma-buf/udmabuf.c
>> index ca2b21c5c57f..254d9ec3d9f3 100644
>> --- a/drivers/dma-buf/udmabuf.c
>> +++ b/drivers/dma-buf/udmabuf.c
>> @@ -226,6 +226,28 @@ static int add_to_unpin_list(struct list_head
>> *unpin_list,
>> return 0;
>> }
>>
>> +static __always_inline int init_udmabuf(struct udmabuf *ubuf, pgoff_t
>> pgcnt)
>> +{
>> + INIT_LIST_HEAD(&ubuf->unpin_list);
>> +
>> + ubuf->folios = kvmalloc_array(pgcnt, sizeof(*ubuf->folios),
>> GFP_KERNEL);
>> + if (!ubuf->folios)
>> + return -ENOMEM;
>> +
>> + ubuf->offsets = kvcalloc(pgcnt, sizeof(*ubuf->offsets), GFP_KERNEL);
>> + if (!ubuf->offsets)
>> + return -ENOMEM;
>> +
>> + return 0;
>> +}
>> +
>> +static __always_inline void deinit_udmabuf(struct udmabuf *ubuf)
>> +{
>> + unpin_all_folios(&ubuf->unpin_list);
>> + kvfree(ubuf->offsets);
>> + kvfree(ubuf->folios);
>> +}
>> +
>> static void release_udmabuf(struct dma_buf *buf)
>> {
>> struct udmabuf *ubuf = buf->priv;
>> @@ -234,9 +256,7 @@ static void release_udmabuf(struct dma_buf *buf)
>> if (ubuf->sg)
>> put_sg_table(dev, ubuf->sg, DMA_BIDIRECTIONAL);
>>
>> - unpin_all_folios(&ubuf->unpin_list);
>> - kvfree(ubuf->offsets);
>> - kvfree(ubuf->folios);
>> + deinit_udmabuf(ubuf);
>> kfree(ubuf);
>> }
>>
>> @@ -396,33 +416,24 @@ static long udmabuf_create(struct miscdevice
>> *device,
>> if (!ubuf)
>> return -ENOMEM;
>>
>> - INIT_LIST_HEAD(&ubuf->unpin_list);
>> pglimit = (size_limit_mb * 1024 * 1024) >> PAGE_SHIFT;
>> for (i = 0; i < head->count; i++) {
>> if (!PAGE_ALIGNED(list[i].offset))
>> - goto err;
>> + goto err_noinit;
>> if (!PAGE_ALIGNED(list[i].size))
>> - goto err;
>> + goto err_noinit;
>>
>> pgcnt += list[i].size >> PAGE_SHIFT;
>> if (pgcnt > pglimit)
>> - goto err;
>> + goto err_noinit;
>> }
>>
>> if (!pgcnt)
>> - goto err;
>> + goto err_noinit;
>>
>> - ubuf->folios = kvmalloc_array(pgcnt, sizeof(*ubuf->folios),
>> GFP_KERNEL);
>> - if (!ubuf->folios) {
>> - ret = -ENOMEM;
>> + ret = init_udmabuf(ubuf, pgcnt);
>> + if (ret)
>> goto err;
>> - }
>> -
>> - ubuf->offsets = kvcalloc(pgcnt, sizeof(*ubuf->offsets), GFP_KERNEL);
>> - if (!ubuf->offsets) {
>> - ret = -ENOMEM;
>> - goto err;
>> - }
>>
>> for (i = 0; i < head->count; i++) {
>> struct file *memfd = fget(list[i].memfd);
>> @@ -446,9 +457,8 @@ static long udmabuf_create(struct miscdevice
>> *device,
>> return ret;
>>
>> err:
>> - unpin_all_folios(&ubuf->unpin_list);
>> - kvfree(ubuf->offsets);
>> - kvfree(ubuf->folios);
>> + deinit_udmabuf(ubuf);
>> +err_noinit:
> I don't really see the need for this new label, but I guess it makes things a
> bit clear.
If not this, each list err will need kfree, I think use this more clear.
Thank you. :)
>
> Acked-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
>
>> kfree(ubuf);
>> return ret;
>> }
>> --
>> 2.45.2
next prev parent reply other threads:[~2024-09-06 8:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 8:38 [PATCH v5 0/7] udmbuf bug fix and some improvements Huan Yang
2024-09-03 8:38 ` [PATCH v5 1/7] udmabuf: pre-fault when first page fault Huan Yang
2024-09-06 8:12 ` Kasireddy, Vivek
2024-09-06 8:37 ` Huan Yang
2024-09-03 8:38 ` [PATCH v5 2/7] udmabuf: change folios array from kmalloc to kvmalloc Huan Yang
2024-09-03 8:38 ` [PATCH v5 3/7] udmabuf: fix vmap_udmabuf error page set Huan Yang
2024-09-03 8:38 ` [PATCH v5 4/7] udmabuf: udmabuf_create pin folio codestyle cleanup Huan Yang
2024-09-06 8:17 ` Kasireddy, Vivek
2024-09-06 8:30 ` Huan Yang
2024-09-09 5:03 ` Kasireddy, Vivek
2024-09-09 6:31 ` Huan Yang
2024-09-03 8:38 ` [PATCH v5 5/7] udmabuf: introduce udmabuf init and deinit helper Huan Yang
2024-09-06 8:20 ` Kasireddy, Vivek
2024-09-06 8:38 ` Huan Yang [this message]
2024-09-03 8:38 ` [PATCH v5 6/7] udmabuf: remove udmabuf_folio Huan Yang
2024-09-06 8:22 ` Kasireddy, Vivek
2024-09-06 8:39 ` Huan Yang
2024-09-03 8:38 ` [PATCH v5 7/7] udmabuf: reuse folio array when pin folios Huan Yang
2024-09-06 8:23 ` Kasireddy, Vivek
2024-09-06 8:40 ` Huan Yang
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=5970129f-5787-424f-ad7c-ee8568a1734b@vivo.com \
--to=link@vivo.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=sumit.semwal@linaro.org \
--cc=vivek.kasireddy@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®