From: Qinxin Xia <xiaqinxin@huawei.com>
To: Barry Song <21cnbao@gmail.com>
Cc: <m.szyprowski@samsung.com>, <robin.murphy@arm.com>,
<prime.zeng@huawei.com>, <fanghao11@huawei.com>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
<wangzhou1@hisilicon.com>
Subject: Re: [PATCH v4] tools/dma: move dma_map_benchmark from selftests to tools/dma
Date: Wed, 22 Oct 2025 16:16:27 +0800 [thread overview]
Message-ID: <04ac708f-922e-4aca-80ea-e1217da89ce2@huawei.com> (raw)
In-Reply-To: <CAGsJ_4wMtWZUTWRePK9_90LrbANUo7RcVkBRbQJ4aBEypWwtLQ@mail.gmail.com>
On 2025/10/22 12:23:04, Barry Song <21cnbao@gmail.com> wrote:
>>
>> #define DMA_MAP_BENCHMARK _IOWR('d', 1, struct map_benchmark)
>> #define DMA_MAP_MAX_THREADS 1024
>> @@ -27,5 +29,7 @@ struct map_benchmark {
>> __u32 dma_dir; /* DMA data direction */
>> __u32 dma_trans_ns; /* time for DMA transmission in ns */
>> __u32 granule; /* how many PAGE_SIZE will do map/unmap once a time */
>> + __u8 expansion[76]; /* For future use */
>> };
>
> I didn’t realize you were hiding a bugfix within the code cleanup.
>
> We agreed this is a hotfix that should be merged promptly[1]. Before sending
> v5, please submit the hotfix first using the existing folder (without moving
> the code from selftest to tools). Once it is merged, resend v5 based on it.
>
> [1] https://lore.kernel.org/lkml/f8c0cbdc-9c68-46bb-8dad-1d7c80f3f741@samsung.com/
>
> Thanks
> Barry
Hello Barry:
For the previous patch has not merged, I have carefully considered this.
(I didn't include this in v1. You can see it in the 'Changes')
Previously, struct map_benchmark is defined in map_benchmark.h. The
header file in include/linux/ generally does not guarantee stable uABI.
(Although it does get used in userspace, I thought that's because we
include the kernel header in userspace.Referencing kernel headers in
userspace programs is inherently risky)
This patch moves map_benchmark.h from include/linux to include/uapi
/linux. I think maybe it's reasonable to restore that here...
I'm sure you have more experience in this area, and if you still insist
on separation, I will prepare v5 based on merged version.
Thanks,
Qinxin
next prev parent reply other threads:[~2025-10-22 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 3:55 [PATCH v4] tools/dma: move dma_map_benchmark from selftests to tools/dma Qinxin Xia
2025-10-22 4:23 ` Barry Song
2025-10-22 8:16 ` Qinxin Xia [this message]
2025-10-22 8:21 ` Barry Song
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=04ac708f-922e-4aca-80ea-e1217da89ce2@huawei.com \
--to=xiaqinxin@huawei.com \
--cc=21cnbao@gmail.com \
--cc=fanghao11@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=m.szyprowski@samsung.com \
--cc=prime.zeng@huawei.com \
--cc=robin.murphy@arm.com \
--cc=wangzhou1@hisilicon.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 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.