[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z030AVd1_uURWsgL@J2N7QTR9R3>
Date: Mon, 2 Dec 2024 17:53:05 +0000
From: Mark Rutland <mark.rutland@....com>
To: Marc Zyngier <maz@...nel.org>
Cc: Vitaly Chikunov <vt@...linux.org>, Will Deacon <will@...nel.org>,
james.morse@....com, linux-arm-kernel@...ts.infradead.org,
Catalin Marinas <catalin.marinas@....com>,
linux-kernel@...r.kernel.org, oliver.upton@...ux.dev
Subject: Re: v6.13-rc1: Internal error: Oops - Undefined instruction:
0000000002000000 [#1] SMP
On Mon, Dec 02, 2024 at 04:07:03PM +0000, Marc Zyngier wrote:
> On Mon, 02 Dec 2024 15:59:40 +0000,
> Vitaly Chikunov <vt@...linux.org> wrote:
> >
> > Marc,
> >
> > On Mon, Dec 02, 2024 at 03:53:59PM +0000, Marc Zyngier wrote:
> > >
> > > What the log doesn't say is what the host is. Is it 6.13-rc1 as well?
> >
> > No, host is 6.6.60.
>
> Right. I wouldn't be surprised if:
>
> - this v6.6 kernel doesn't hide the MPAM feature as it should (and
> that's proably something we should backport)
Looks like v6.6.60 is missing:
6685f5d572c22e10 ("KVM: arm64: Disable MPAM visibility by default and ignore VMM writes")
... which is a fix for:
011e5f5bf529f8ec (" arm64/cpufeature: Add remaining feature bits in ID_AA64PFR0 register")
... which unintentionally exposed ID_AA64PFR0.MPAM to guests, and *is*
in v6.6.60.
Mark.
> - you get a nastygram in the host log telling you that the guest has
> executed something it shouldn't (you'll get the encoding of the
> instruction)
>
> Can you confirm these two things?
>
> M.
>
> --
> Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists