[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <86v7koxk1z.wl-maz@kernel.org>
Date: Thu, 09 Oct 2025 14:48:40 +0100
From: Marc Zyngier <maz@...nel.org>
To: salil.mehta@...src.net
Cc: linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
salil.mehta@...wei.com,
jonathan.cameron@...wei.com,
will@...nel.org,
catalin.marinas@....com,
mark.rutland@....com,
james.morse@....com,
sudeep.holla@....com,
lpieralisi@...nel.org,
jean-philippe@...aro.org,
tglx@...utronix.de,
oliver.upton@...ux.dev,
peter.maydell@...aro.org,
richard.henderson@...aro.org,
andrew.jones@...ux.dev,
mst@...hat.com,
david@...hat.com,
philmd@...aro.org,
ardb@...nel.org,
borntraeger@...ux.ibm.com,
alex.bennee@...aro.org,
gustavo.romero@...aro.org,
npiggin@...il.com,
linux@...linux.org.uk,
karl.heubaum@...cle.com,
miguel.luis@...cle.com,
darren@...amperecomputing.com,
ilkka@...amperecomputing.com,
vishnu@...amperecomputing.com,
gankulkarni@...amperecomputing.com,
wangyanan55@...wei.com,
wangzhou1@...ilicon.com,
linuxarm@...wei.com
Subject: Re: [RFC PATCH] KVM: arm64: vgic-v3: Cache ICC_CTLR_EL1 and allow lockless read when ready
On Wed, 08 Oct 2025 21:19:55 +0100,
salil.mehta@...src.net wrote:
>
> From: Salil Mehta <salil.mehta@...wei.com>
>
> [A rough illustration of the problem and the probable solution]
>
> Userspace reads of ICC_CTLR_EL1 via KVM device attributes currently takes a slow
> path that may acquire all vCPU locks. Under workloads that exercise userspace
> PSCI CPU_ON flows or frequent vCPU resets, this can cause vCPU lock contention
> in KVM and, in the worst cases, -EBUSY returns to userspace.
>
> When PSCI CPU_ON and CPU_OFF calls are handled entirely in KVM, these operations
> are executed under KVM vCPU locks in the host kernel (EL1) and appear atomic to
> other vCPU threads. In this context, system register accesses are serialized
> under KVM vCPU locks, ensuring atomicity with respect to other vCPUs. After
> SMCCC filtering was introduced, PSCI CPU_ON and CPU_OFF calls can now exit to
> userspace (QEMU). During the handling of PSCI CPU_ON call in userspace, a
> cpu_reset() is exerted which reads ICC_CTLR_EL1 through KVM device attribute
> IOCTLs. To avoid transient inconsistency and -EBUSY errors, QEMU is forced to
> pause all vCPUs before issuing these IOCTLs.
I'm going to repeat in public what I already said in private.
Why does QEMU need to know this? I don't see how this is related to
PSCI, and outside of save/restore, there is no reason why QEMU should
poke at this. If QEMU needs fixing, please fix QEMU.
Honestly, I don't see why the kernel should even care about this, and
I have no intention of adopting anything of the sort for something
that has all the hallmarks of a userspace bug.
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists