From: Auger Eric <eric.auger@redhat.com>
To: Graeme Gregory <graeme@nuviainc.com>, qemu-arm@nongnu.org
Cc: peter.maydell@linaro.org, jamie@nuviainc.com, rad@semihalf.com,
qemu-devel@nongnu.org, leif@nuviainc.com, philmd@redhat.com
Subject: Re: [PATCH] hw/arm/sbsa-ref : Fix SMMUv3 Initialisation
Date: Fri, 25 Sep 2020 16:00:48 +0200 [thread overview]
Message-ID: <f67b75fe-c5ce-8b95-e19b-fc4ce2217b31@redhat.com> (raw)
In-Reply-To: <20200925133902.28349-1-graeme@nuviainc.com>
Hi Gregory,
On 9/25/20 3:39 PM, Graeme Gregory wrote:
> SMMUv3 has an error in previous patch where a i was transposed to a 1
> meaning interrupts would not have been correctly assigned to the SMMUv3
> instance.
>
> The code also contained an error in that the IRQs were never allocated
> in the irqmap.
>
> Fixes: 48ba18e6d3f3 ("hw/arm/sbsa-ref: Simplify by moving the gic in the machine state")
> Signed-off-by: Graeme Gregory <graeme@nuviainc.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Thanks
Eric
> ---
> hw/arm/sbsa-ref.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/hw/arm/sbsa-ref.c b/hw/arm/sbsa-ref.c
> index 257ada9425..9109fb58be 100644
> --- a/hw/arm/sbsa-ref.c
> +++ b/hw/arm/sbsa-ref.c
> @@ -138,6 +138,7 @@ static const int sbsa_ref_irqmap[] = {
> [SBSA_SECURE_UART_MM] = 9,
> [SBSA_AHCI] = 10,
> [SBSA_EHCI] = 11,
> + [SBSA_SMMU] = 12, /* ... to 15 */
> };
>
> static uint64_t sbsa_ref_cpu_mp_affinity(SBSAMachineState *sms, int idx)
> @@ -530,7 +531,7 @@ static void create_smmu(const SBSAMachineState *sms, PCIBus *bus)
> sysbus_mmio_map(SYS_BUS_DEVICE(dev), 0, base);
> for (i = 0; i < NUM_SMMU_IRQS; i++) {
> sysbus_connect_irq(SYS_BUS_DEVICE(dev), i,
> - qdev_get_gpio_in(sms->gic, irq + 1));
> + qdev_get_gpio_in(sms->gic, irq + i));
> }
> }
>
>
next prev parent reply other threads:[~2020-09-25 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 13:39 [PATCH] hw/arm/sbsa-ref : Fix SMMUv3 Initialisation Graeme Gregory
2020-09-25 14:00 ` Auger Eric [this message]
2020-09-26 7:45 ` Philippe Mathieu-Daudé
2020-09-28 9:35 ` Graeme Gregory
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=f67b75fe-c5ce-8b95-e19b-fc4ce2217b31@redhat.com \
--to=eric.auger@redhat.com \
--cc=graeme@nuviainc.com \
--cc=jamie@nuviainc.com \
--cc=leif@nuviainc.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rad@semihalf.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).