From: Nicolin Chen <nicolinc@nvidia.com>
To: Eric Auger <eauger@redhat.com>
Cc: <peter.maydell@linaro.org>, <wangxingang5@huawei.com>,
<shannon.zhaosl@gmail.com>, <mst@redhat.com>,
<imammedo@redhat.com>, <anisinha@redhat.com>,
<qemu-arm@nongnu.org>, <qemu-devel@nongnu.org>
Subject: Re: [PATCH v3] hw/arm/virt-acpi-build: Fix id_count in build_iort_id_mapping
Date: Wed, 19 Jun 2024 12:56:55 -0700 [thread overview]
Message-ID: <ZnM4B+ZeN73UFpeQ@Asurada-Nvidia> (raw)
In-Reply-To: <aa27c94c-099b-4383-a93f-30ffdf5cfd54@redhat.com>
On Wed, Jun 19, 2024 at 04:15:35PM +0200, Eric Auger wrote:
> > @@ -209,12 +209,20 @@ static void acpi_dsdt_add_tpm(Aml *scope, VirtMachineState *vms)
> > #define ROOT_COMPLEX_ENTRY_SIZE 36
> > #define IORT_NODE_OFFSET 48
> >
> > +/*
> > + * Input Output Remapping Table (IORT) -- Table 4 ID mapping format
> > + * Conforms to "IO Remapping Table System Software on ARM Platforms",
> > + * Document number: ARM DEN 0049E.b, Feb 2021
> I would rather explain what the function does, ie append an ID mapping
> entry as desribed in Tabble 4 ID Mapping format.
>
> Also while at it you may use a more recent revision
> There is DEN0049E_IO_Remapping_Table_E.f.pdf available
Sure. Will do a v4 with something like:
+/*
+ * Append an ID mapping entry as described in "Table 4 ID mapping format"
+ * from "IO Remapping Table System Software on ARM Platforms", Chapter 3.
+ * Document number: ARM DEN 0049E.f, Apr 2024
> Reviewed-by: Eric Auger <eric.auger@redhat.com>
Thanks for the review!
Nicolin
prev parent reply other threads:[~2024-06-19 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 21:11 [PATCH v3] hw/arm/virt-acpi-build: Fix id_count in build_iort_id_mapping Nicolin Chen
2024-06-18 21:14 ` Michael S. Tsirkin
2024-06-18 21:19 ` Nicolin Chen
2024-06-18 21:34 ` Michael S. Tsirkin
2024-06-18 21:51 ` Nicolin Chen
2024-06-18 22:05 ` Michael S. Tsirkin
2024-06-19 14:15 ` Eric Auger
2024-06-19 19:56 ` Nicolin Chen [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=ZnM4B+ZeN73UFpeQ@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=anisinha@redhat.com \
--cc=eauger@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhaosl@gmail.com \
--cc=wangxingang5@huawei.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;
as well as URLs for NNTP newsgroup(s).