From: "Ard Biesheuvel" <ardb@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Oliver Steffen <osteffen@redhat.com>,
devel@edk2.groups.io, dann.frazier@canonical.com,
kraxel@redhat.com
Subject: Re: [edk2-devel] [PATCH v2 2/2] ArmVirtPkg/ArmVirtQemu: Avoid early ID map on ThunderX
Date: Thu, 19 Jan 2023 13:21:39 +0100 [thread overview]
Message-ID: <CAMj1kXHwtnkR0W76ugugYbWj2=u7xZycSZ80izU0d+KPiUjmGA@mail.gmail.com> (raw)
In-Reply-To: <86y1pyn3g4.wl-maz@kernel.org>
On Thu, 19 Jan 2023 at 12:56, Marc Zyngier <maz@kernel.org> wrote:
>
> On Thu, 19 Jan 2023 11:11:34 +0000,
> Ard Biesheuvel <ardb@kernel.org> wrote:
> >
> > (cc Marc)
> >
> > Context:
> > - on my TX2 (with the S1PTW r/o memslot fix applied), the new version
> > of ArmVirtQemu that uses an initial ID map in emulated NOR flash works
> > fine.
> > - in Oliver's case (which is a slightly different flavor of TX2), it
> > crashes extremely early, presumably at the point where this ID map is
> > activated.
>
> Oliver seems to have a vintage ThunderX (aka the worst arm64
> implementation in history!), so it is indeed a very different beat
> from TX2.
>
No, it's a TX2 alright - we disabled this ID map for TX1 already
because it tickles the I-cache corruption erratum (EDK2 runs at EL1
and the initial ID map is ASID scoped with non-global mappings, so
that we can switch to the actual ID map seamlessly)
> Without the kernel patch[1], I can trigger the issue pretty reliably,
> specially in the absence of THP. It all depends on the layout of the
> EDK2 object and the order in which pages get mapped.
>
> The first course of action would be to make sure that the patch is
> applied to the host kernel. If this still fails to boot, I'm happy to
> help investigating it.
>
indeed.
next prev parent reply other threads:[~2023-01-19 12:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 16:25 [PATCH v2 1/2] ArmVirtPkg/ArmPlatformLibQemu: Ensure that VFP is on before running C code Ard Biesheuvel
2023-01-05 16:25 ` [PATCH v2 2/2] ArmVirtPkg/ArmVirtQemu: Avoid early ID map on ThunderX Ard Biesheuvel
2023-01-10 0:08 ` dann frazier
2023-01-17 12:47 ` [edk2-devel] " Oliver Steffen
2023-01-17 14:53 ` Ard Biesheuvel
2023-01-18 6:36 ` Oliver Steffen
2023-01-18 7:34 ` Ard Biesheuvel
2023-01-18 8:27 ` Oliver Steffen
2023-01-18 8:48 ` Ard Biesheuvel
2023-01-18 9:22 ` Ard Biesheuvel
2023-01-19 11:03 ` Oliver Steffen
2023-01-19 11:11 ` Ard Biesheuvel
2023-01-19 11:25 ` Oliver Steffen
2023-01-19 11:55 ` Marc Zyngier
2023-01-19 12:21 ` Ard Biesheuvel [this message]
2023-01-19 12:00 ` Gerd Hoffmann
2023-01-19 12:55 ` Oliver Steffen
2023-01-19 13:21 ` Ard Biesheuvel
2023-01-26 12:01 ` Gerd Hoffmann
2023-01-26 13:48 ` Marc Zyngier
2023-01-26 14:46 ` Gerd Hoffmann
2023-01-26 15:08 ` Marc Zyngier
2023-02-01 9:13 ` Oliver Steffen
2023-02-01 11:51 ` Ard Biesheuvel
2023-02-01 12:58 ` Oliver Steffen
2023-02-01 13:29 ` Ard Biesheuvel
2023-02-02 11:09 ` Oliver Steffen
[not found] ` <173FFD60429C89C3.3213@groups.io>
2023-02-07 10:51 ` Oliver Steffen
2023-02-07 11:56 ` Ard Biesheuvel
2023-02-07 12:58 ` Oliver Steffen
2023-02-09 15:15 ` Ard Biesheuvel
2023-03-02 10:50 ` Ard Biesheuvel
2023-03-02 13:29 ` Oliver Steffen
[not found] ` <17489D498A098DB9.9697@groups.io>
2023-05-19 16:32 ` Oliver Steffen
2023-05-19 21:36 ` Ard Biesheuvel
2023-05-20 8:37 ` Oliver Steffen
2023-05-20 9:20 ` 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='CAMj1kXHwtnkR0W76ugugYbWj2=u7xZycSZ80izU0d+KPiUjmGA@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