[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-arm] Kernel boot regression with PAuth and aarch64-softmmu -cp

From: Mark Rutland
Subject: Re: [Qemu-arm] Kernel boot regression with PAuth and aarch64-softmmu -cpu max and el2 enabled
Date: Tue, 29 Jan 2019 12:51:02 +0000
User-agent: Mutt/1.11.1+11 (2f07cb52) (2018-12-01)

On Tue, Jan 29, 2019 at 11:54:13AM +0000, Peter Maydell wrote:
> On Tue, 29 Jan 2019 at 11:46, Mark Rutland <address@hidden> 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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]