From: Mark Rutland <mark.rutland@arm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Marc Zyngier" <marc.zyngier@arm.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Kristina Martsenko" <kristina.martsenko@arm.com>,
"open list:ARM" <qemu-arm@nongnu.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Qemu-devel] Kernel boot regression with PAuth and aarch64-softmmu -cpu max and el2 enabled
Date: Tue, 29 Jan 2019 12:51:02 +0000 [thread overview]
Message-ID: <20190129125101.GC25983@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <CAFEAcA-_ShbUthqPSPgEPmV0EeRUO85n=sC-+76gRAH830co_g@mail.gmail.com>
On Tue, Jan 29, 2019 at 11:54:13AM +0000, Peter Maydell wrote:
> On Tue, 29 Jan 2019 at 11:46, Mark Rutland <mark.rutland@arm.com> wrote:
> > On Tue, Jan 29, 2019 at 11:08:19AM +0000, Alex Bennée wrote:
> > > The -cpu max enabled a cortex-a57 + whatever extra features we've
> > > enabled in QEMU so far. It won't match any "real" CPU but it should be
> > > architecturally correct in so far we implement prerequisite features for
> > > any given feature. The cpuid feature bits should also be correct as we
> > > test them internally in QEMU to enable features.
> >
> > Just to check, does this enable VHE?
>
> It does not. (We have no implementation of VHE yet -- as and when
> we do implement that "-cpu max" will turn it on, but today it doesn't.)
Ok. In that case, the kernel should drop to EL1N and stay there after it
configures EL2.
There are no pointer authentication traps taken to EL1N, so if something
is going wrong, I suspect either:
* a trap is taken to EL2, and we hyp_panic()
* an UNDEF is being taken to EL1N
Thanks,
Mark.
prev parent reply other threads:[~2019-01-29 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 11:08 [Qemu-devel] Kernel boot regression with PAuth and aarch64-softmmu -cpu max and el2 enabled Alex Bennée
2019-01-29 11:46 ` Mark Rutland
2019-01-29 11:54 ` Peter Maydell
2019-01-29 12:51 ` Mark Rutland [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=20190129125101.GC25983@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=alex.bennee@linaro.org \
--cc=kristina.martsenko@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/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).