From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH] ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge
Date: Thu, 15 Nov 2018 04:37:06 -0800 [thread overview]
Message-ID: <CAKv+Gu_YUO7QqCXqJAJcbEAp=6z2mggeQ=UqKy9=LNDrUodjsA@mail.gmail.com> (raw)
In-Reply-To: <ab5e8adb-a518-5ef1-29a3-89081f4307ab@redhat.com>
On Wed, 14 Nov 2018 at 14:11, Laszlo Ersek <lersek@redhat.com> wrote:
>
> On 11/14/18 21:00, Leif Lindholm wrote:
> > On Wed, Nov 14, 2018 at 11:27:24AM -0800, Ard Biesheuvel wrote:
> >> Fix a typo in the 32-bit ARM version of the GICv3 driver, which uses
> >> the wrong system register encoding to access ICC_IAR1, and attempted
> >> to access ICC_IAR0 instead. This results in boot time hangs both
> >> under QEMU emulation and on real hardware.
> >>
> >> Contributed-under: TianoCore Contribution Agreement 1.1
> >> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >
> > Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
> >
> > I would say given how long we've gone without finding this,
>
> Right, that makes me curious -- what has changed now? What exposed this bug?
>
I was regression testing a EFI workaround I put in the kernel for
GICv3, which was apparently the first time anyone tried running
EDK2/ARM on a GICv3 system (which is one of the reasons I wanted to
get you one of the Socionext SynQuacer boards: it has a GICv3 with
GICv2 compatibility and support for 32-bit guests, but sadly, we still
don't have any with fixed silicon)
next prev parent reply other threads:[~2018-11-15 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 19:27 [PATCH] ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge Ard Biesheuvel
2018-11-14 20:00 ` Leif Lindholm
2018-11-14 22:11 ` Laszlo Ersek
2018-11-15 12:37 ` Ard Biesheuvel [this message]
2018-11-15 12:44 ` Laszlo Ersek
2018-11-15 13:09 ` Ard Biesheuvel
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-list 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='CAKv+Gu_YUO7QqCXqJAJcbEAp=6z2mggeQ=UqKy9=LNDrUodjsA@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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