From: Eric Auger <eric.auger@redhat.com>
To: Gustavo Romero <gustavo.romero@linaro.org>,
qemu-devel@nongnu.org, philmd@linaro.org, mst@redhat.com
Cc: qemu-arm@nongnu.org, alex.bennee@linaro.org, udo@hypervisor.org,
ajones@ventanamicro.com, peter.maydell@linaro.org,
imammedo@redhat.com, anisinha@redhat.com
Subject: Re: [PATCH v5 4/9] hw/arm/virt-acpi-build: Improve comment in build_iort
Date: Fri, 27 Jun 2025 15:57:35 +0200 [thread overview]
Message-ID: <adf5e6e5-e0e3-44f9-949c-620aea3edfa0@redhat.com> (raw)
In-Reply-To: <20250623135749.691137-5-gustavo.romero@linaro.org>
Hi Gustavo,
On 6/23/25 3:57 PM, Gustavo Romero wrote:
> When building the Root Complex table, the comment about the code that
s/table/node? or do you refer to the IORT table?
> maps the RC node to SMMU node is misleading because it reads
> "RC -> SMMUv3 -> ITS", but the code is only mapping the RCs IDs to the
> SMMUv3 node. The step of mapping from the SMMUv3 IDs to the ITS Group
> node is actually defined in another table (in the SMMUv3 node). So
> change the comment to read "RC -> SMMUv3" instead.
>
> Signed-off-by Gustavo Romero <gustavo.romero@linaro.org>
> ---
> hw/arm/virt-acpi-build.c | 25 +++++++++++++++++++------
> 1 file changed, 19 insertions(+), 6 deletions(-)
>
> diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
> index 9eee284c80..e9cd3fb351 100644
> --- a/hw/arm/virt-acpi-build.c
> +++ b/hw/arm/virt-acpi-build.c
> @@ -370,7 +370,7 @@ build_iort(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)
> /* DeviceID mapping index (ignored since interrupts are GSIV based) */
> build_append_int_noprefix(table_data, 0, 4);
>
> - /* output IORT node is the ITS group node (the first node) */
> + /* Output IORT node is the ITS Group node (the first node) */
> build_iort_id_mapping(table_data, 0, 0x10000, IORT_NODE_OFFSET);
> }
>
> @@ -407,23 +407,36 @@ build_iort(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)
> if (vms->iommu == VIRT_IOMMU_SMMUV3) {
> AcpiIortIdMapping *range;
>
> - /* translated RIDs connect to SMMUv3 node: RC -> SMMUv3 -> ITS */
> + /*
> + * Map RIDs (input) from RC to SMMUv3 nodes: RC -> SMMUv3.
> + *
> + * N.B.: The mapping from SMMUv3 to ITS Group node (SMMUv3 -> ITS) is
> + * defined in the SMMUv3 table, where all SMMUv3 IDs are mapped to the
s/table/node
> + * ITS Group node.
> + */
> for (i = 0; i < smmu_idmaps->len; i++) {
> range = &g_array_index(smmu_idmaps, AcpiIortIdMapping, i);
> - /* output IORT node is the smmuv3 node */
> + /* Output IORT node is the SMMUv3 node. */
> build_iort_id_mapping(table_data, range->input_base,
> range->id_count, smmu_offset);
> }
>
> - /* bypassed RIDs connect to ITS group node directly: RC -> ITS */
> + /*
> + * Map bypassed (don't go throught the SMMU) RIDs (input) to ITS Group
> + * node directly: RC -> ITS.
> + */
> for (i = 0; i < its_idmaps->len; i++) {
> range = &g_array_index(its_idmaps, AcpiIortIdMapping, i);
> - /* output IORT node is the ITS group node (the first node) */
> + /* Output IORT node is the ITS Group node (the first node). */
> build_iort_id_mapping(table_data, range->input_base,
> range->id_count, IORT_NODE_OFFSET);
> }
> } else {
> - /* output IORT node is the ITS group node (the first node) */
> + /*
> + * Map all RIDs (input) to ITS Group node directly, since there is no
> + * SMMU: RC -> ITS.
> + * Output IORT node is the ITS Group node (the first node).
> + */
> build_iort_id_mapping(table_data, 0, 0x10000, IORT_NODE_OFFSET);
> }
>
Besides:
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Eric
next prev parent reply other threads:[~2025-06-27 13:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:57 [PATCH-for-10.1 v5 0/9] hw/arm: GIC 'its=off' ACPI table fixes Gustavo Romero
2025-06-23 13:57 ` [PATCH v5 1/9] hw/intc/gicv3_its: Do not check its_class_name() Gustavo Romero
2025-06-23 13:57 ` [PATCH v5 2/9] hw/arm/virt: Simplify logic for setting instance's 'tcg_its' variable Gustavo Romero
2025-06-23 13:57 ` [PATCH v5 3/9] hw/arm/virt: Simplify create_its() Gustavo Romero
2025-06-23 13:57 ` [PATCH v5 4/9] hw/arm/virt-acpi-build: Improve comment in build_iort Gustavo Romero
2025-06-27 13:57 ` Eric Auger [this message]
2025-06-27 14:05 ` Eric Auger via
2025-06-23 13:57 ` [PATCH v5 5/9] hw/arm/virt-acpi-build: Factor out create_its_idmaps Gustavo Romero
2025-06-27 15:28 ` Eric Auger
2025-06-28 19:43 ` Gustavo Romero
2025-06-23 13:57 ` [PATCH v5 6/9] qtest/bios-tables-test: Add test for when ITS is off on aarch64 Gustavo Romero
2025-06-27 15:30 ` Eric Auger
2025-06-23 13:57 ` [PATCH v5 7/9] qtest/bios-tables-test: Add blobs for its=off test " Gustavo Romero
2025-06-27 15:32 ` Eric Auger
2025-06-23 13:57 ` [PATCH v5 8/9] hw/arm/virt-acpi-build: Fix ACPI IORT and MADT tables when its=off Gustavo Romero
2025-06-27 15:44 ` Eric Auger
2025-06-28 19:44 ` Gustavo Romero
2025-06-27 15:45 ` Eric Auger
2025-06-27 15:46 ` Eric Auger via
2025-06-23 13:57 ` [PATCH v5 9/9] qtest/bios-tables-test: Update blobs for its=off test on aarch64 Gustavo Romero
2025-06-27 15:49 ` Eric Auger
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=adf5e6e5-e0e3-44f9-949c-620aea3edfa0@redhat.com \
--to=eric.auger@redhat.com \
--cc=ajones@ventanamicro.com \
--cc=alex.bennee@linaro.org \
--cc=anisinha@redhat.com \
--cc=gustavo.romero@linaro.org \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=udo@hypervisor.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).