From: Auger Eric <eric.auger@redhat.com>
To: Zenghui Yu <yuzenghui@huawei.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
peter.maydell@linaro.org, prem.mallappa@broadcom.com,
shannon.zhaosl@gmail.com
Cc: wanghaibin.wang@huawei.com
Subject: Re: [PATCH] hw/arm/virt-acpi-build: Fix GSIV values of the {GERR, Sync} interrupts
Date: Tue, 6 Apr 2021 12:10:27 +0200 [thread overview]
Message-ID: <7f42bc9f-3fb8-d24d-d9e4-9b93784504a6@redhat.com> (raw)
In-Reply-To: <20210402084731.93-1-yuzenghui@huawei.com>
Hi Zenghui,
On 4/2/21 10:47 AM, Zenghui Yu wrote:
> The GSIV values in SMMUv3 IORT node are not correct as they don't match
> the SMMUIrq enumeration, which describes the IRQ<->PIN mapping used by
> our emulated vSMMU.
>
> Fixes: a703b4f6c1ee ("hw/arm/virt-acpi-build: Add smmuv3 node in IORT table")
> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
Acked-by: Eric Auger <eric.auger@redhat.com>
Thanks!
Eric
> ---
> hw/arm/virt-acpi-build.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
> index f5a2b2d4cb..60fe2e65a7 100644
> --- a/hw/arm/virt-acpi-build.c
> +++ b/hw/arm/virt-acpi-build.c
> @@ -292,8 +292,8 @@ build_iort(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)
> smmu->flags = cpu_to_le32(ACPI_IORT_SMMU_V3_COHACC_OVERRIDE);
> smmu->event_gsiv = cpu_to_le32(irq);
> smmu->pri_gsiv = cpu_to_le32(irq + 1);
> - smmu->gerr_gsiv = cpu_to_le32(irq + 2);
> - smmu->sync_gsiv = cpu_to_le32(irq + 3);
> + smmu->sync_gsiv = cpu_to_le32(irq + 2);
> + smmu->gerr_gsiv = cpu_to_le32(irq + 3);
>
> /* Identity RID mapping covering the whole input RID range */
> idmap = &smmu->id_mapping_array[0];
>
next prev parent reply other threads:[~2021-04-06 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 8:47 [PATCH] hw/arm/virt-acpi-build: Fix GSIV values of the {GERR, Sync} interrupts Zenghui Yu
2021-04-06 10:10 ` Auger Eric [this message]
2021-04-06 10:44 ` Peter Maydell
2021-04-06 12:22 ` Auger Eric
2021-04-06 12:31 ` Peter Maydell
2021-04-06 12:37 ` Auger Eric
2021-04-08 9:34 ` Peter Maydell
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=7f42bc9f-3fb8-d24d-d9e4-9b93784504a6@redhat.com \
--to=eric.auger@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=prem.mallappa@broadcom.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhaosl@gmail.com \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@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).