From: Henry Wang <xin.wang2@amd.com>
To: Julien Grall <julien@xen.org>, <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Michal Orzel <michal.orzel@amd.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH v2 3/8] xen/arm, doc: Add a DT property to specify IOMMU for Dom0less domUs
Date: Mon, 20 May 2024 09:40:36 +0800 [thread overview]
Message-ID: <e6c9c37f-1ecd-4b76-ab97-b3649503f0ae@amd.com> (raw)
In-Reply-To: <d208a4d6-8d3c-4bee-a77c-a3f4758ac9ae@amd.com>
Hi Julien,
On 5/20/2024 8:41 AM, Henry Wang wrote:
> Hi Julien,
>
> Thanks for spending time on the review!
>
> On 5/19/2024 6:17 PM, Julien Grall wrote:
>> Hi Henry,
>>
>> On 16/05/2024 11:03, Henry Wang wrote:
>>> diff --git a/docs/misc/arm/device-tree/booting.txt
>>> b/docs/misc/arm/device-tree/booting.txt
>>> index bbd955e9c2..61f9082553 100644
>>> --- a/docs/misc/arm/device-tree/booting.txt
>>> +++ b/docs/misc/arm/device-tree/booting.txt
>>> @@ -260,6 +260,19 @@ with the following properties:
>>> value specified by Xen command line parameter
>>> gnttab_max_maptrack_frames
>>> (or its default value if unspecified, i.e. 1024) is used.
>>> +- passthrough
>>> +
>>> + A string property specifying whether IOMMU mappings are enabled
>>> for the
>>> + domain and hence whether it will be enabled for passthrough
>>> hardware.
>>> + Possible property values are:
>>> +
>>> + - "enabled"
>>> + IOMMU mappings are enabled for the domain.
>>> +
>>> + - "disabled"
>>> + IOMMU mappings are disabled for the domain and so hardware may
>>> not be
>>> + passed through. This option is the default if this property is
>>> missing.
>>
>> Looking at the code below, it seems like the default will depend on
>> whether the partial device-tree is present. Did I misunderstand?
>
> I am not sure if I understand the "partial device tree" in above
> comment correctly. The "passthrough" property is supposed to be placed
> in the dom0less domU domain node exactly the same way as the other
> dom0less domU properties (such as "direct-map" etc.). This way we can
> control the XEN_DOMCTL_CDF_iommu is set or not for each dom0less domU
> separately.
Oh I think I get your points, you meant the XEN_DOMCTL_CDF_iommu will
still be set if the passthrough dt property is "disabled", but user
provides a partial device tree. Yes you are correct. I will update the
doc to explain a bit more details as below. Thanks for pointing it out.
- "enabled"
IOMMU mappings are enabled for the domain. Note that this option is
the
default if the user provides the device partial passthrough device
tree
for the domain.
- "disabled"
IOMMU mappings are disabled for the domain and so hardware may not be
passed through. This option is the default if this property is missing
and the user does not provide the device partial device tree for
the domain.
Kind regards,
Henry
next prev parent reply other threads:[~2024-05-20 1:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 10:03 [PATCH v2 0/8] Remaining patches for dynamic node programming using overlay dtbo Henry Wang
2024-05-16 10:03 ` [PATCH v2 1/8] xen/common/dt-overlay: Fix lock issue when add/remove the device Henry Wang
2024-05-19 10:04 ` Julien Grall
2024-05-16 10:03 ` [PATCH v2 2/8] tools/xl: Correct the help information and exit code of the dt-overlay command Henry Wang
2024-05-20 18:48 ` Jason Andryuk
2024-05-16 10:03 ` [PATCH v2 3/8] xen/arm, doc: Add a DT property to specify IOMMU for Dom0less domUs Henry Wang
2024-05-19 10:17 ` Julien Grall
2024-05-20 0:41 ` Henry Wang
2024-05-20 1:38 ` Henry Wang
2024-05-20 1:40 ` Henry Wang [this message]
2024-05-16 10:03 ` [PATCH v2 4/8] tools/arm: Introduce the "nr_spis" xl config entry Henry Wang
2024-05-20 19:13 ` Jason Andryuk
2024-05-20 23:19 ` Henry Wang
2024-05-16 10:03 ` [PATCH v2 5/8] xen/arm/gic: Allow routing/removing interrupt to running VMs Henry Wang
2024-05-17 6:03 ` Henry Wang
2024-05-19 11:08 ` Julien Grall
2024-05-20 1:01 ` Henry Wang
2024-05-20 9:50 ` Julien Grall
2024-05-21 2:29 ` Stefano Stabellini
2024-05-16 10:03 ` [PATCH v2 6/8] xen/arm: Add XEN_DOMCTL_dt_overlay DOMCTL and related operations Henry Wang
2024-05-16 12:31 ` Jan Beulich
2024-05-17 1:36 ` Henry Wang
2024-05-17 7:11 ` Jan Beulich
2024-05-16 10:03 ` [PATCH v2 7/8] tools: Introduce the "xl dt-overlay {attach,detach}" commands Henry Wang
2024-05-20 19:41 ` Jason Andryuk
2024-05-20 23:21 ` Henry Wang
2024-05-16 10:03 ` [PATCH v2 8/8] docs: Add device tree overlay documentation Henry Wang
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=e6c9c37f-1ecd-4b76-ab97-b3649503f0ae@amd.com \
--to=xin.wang2@amd.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 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.