[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <24d06740-f8da-43d0-9e40-81323f6a9237@sirena.org.uk>
Date: Tue, 13 Jan 2026 19:08:29 +0000
From: Mark Brown <broonie@...nel.org>
To: Fuad Tabba <tabba@...gle.com>
Cc: Marc Zyngier <maz@...nel.org>, Joey Gouly <joey.gouly@....com>,
Catalin Marinas <catalin.marinas@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Will Deacon <will@...nel.org>, Paolo Bonzini <pbonzini@...hat.com>,
Jonathan Corbet <corbet@....net>, Shuah Khan <shuah@...nel.org>,
Oliver Upton <oupton@...nel.org>, Dave Martin <Dave.Martin@....com>,
Mark Rutland <mark.rutland@....com>,
Ben Horgan <ben.horgan@....com>,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.linux.dev,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kselftest@...r.kernel.org,
Peter Maydell <peter.maydell@...aro.org>,
Eric Auger <eric.auger@...hat.com>
Subject: Re: [PATCH v9 18/30] KVM: arm64: Support SME priority registers
On Mon, Jan 12, 2026 at 11:59:22AM +0000, Fuad Tabba wrote:
> On Tue, 23 Dec 2025 at 01:22, Mark Brown <broonie@...nel.org> wrote:
> > + /*
> > + * We block SME priorities so SMPRIMAP_EL2 is RES0, however we
> > + * do not have traps to block access so the guest might have
> > + * updated the state, overwrite anything there.
>
> nit: overwrite -> overwriting
> > + */
> > + __vcpu_assign_sys_reg(vcpu, SMPRIMAP_EL2, 0);
> > }
My original is correct here - the action we are taking is that we will
overwrite the value. To use overwriting we'd need something more like
"handle this by overwriting anything there".
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists