From: Keqian Zhu <zhukeqian1@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<iommu@lists.linux-foundation.org>
Cc: Marc Zyngier <maz@kernel.org>,
Alex Williamson <alex.williamson@redhat.com>,
<jiangkunkun@huawei.com>, Will Deacon <will@kernel.org>,
<wanghaibin.wang@huawei.com>
Subject: Re: [PATCH] iommu: Update the document of IOMMU_DOMAIN_UNMANAGED
Date: Tue, 2 Feb 2021 21:14:29 +0800 [thread overview]
Message-ID: <c8aebb44-a5ff-9532-facf-b33e0402e660@huawei.com> (raw)
In-Reply-To: <8eac9259-66e5-9b83-39a9-46a86097d450@arm.com>
On 2021/2/2 20:58, Robin Murphy wrote:
> On 2021-02-02 08:53, Keqian Zhu wrote:
>> Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com>
>> ---
>> include/linux/iommu.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/linux/iommu.h b/include/linux/iommu.h
>> index 77e561ed57fd..e8f2efae212b 100644
>> --- a/include/linux/iommu.h
>> +++ b/include/linux/iommu.h
>> @@ -68,7 +68,7 @@ struct iommu_domain_geometry {
>> * devices
>> * IOMMU_DOMAIN_IDENTITY - DMA addresses are system physical addresses
>> * IOMMU_DOMAIN_UNMANAGED - DMA mappings managed by IOMMU-API user, used
>> - * for VMs
>> + * for VMs or userspace driver frameworks
>
> Given that "VMs" effectively has to mean VFIO, doesn't it effectively already imply other uses of VFIO anyway? Unmanaged domains are also used in other subsystems/drivers inside the kernel and we're not naming those, so I don't see that it's particularly helpful to specifically call out one more VFIO use-case.
>
> Perhaps the current wording could be generalised a little more, but we certainly don't want to start trying to maintain an exhaustive list of users here...
Yep, a more generalised description is better. After I have a look at all the use cases...
Thanks,
Keqian
>
> Robin.
>
>> * IOMMU_DOMAIN_DMA - Internally used for DMA-API implementations.
>> * This flag allows IOMMU drivers to implement
>> * certain optimizations for these domains
>>
> .
>
prev parent reply other threads:[~2021-02-02 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 8:53 Keqian Zhu
2021-02-02 12:58 ` Robin Murphy
2021-02-02 13:14 ` Keqian Zhu [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=c8aebb44-a5ff-9532-facf-b33e0402e660@huawei.com \
--to=zhukeqian1@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jiangkunkun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robin.murphy@arm.com \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®