KVM: arm64: Allow userspace to change the implementation ID registers

KVM's treatment of the ID registers that describe the implementation
(MIDR, REVIDR, and AIDR) is interesting, to say the least. On the
userspace-facing end of it, KVM presents the values of the boot CPU on
all vCPUs and treats them as invariant. On the guest side of things KVM
presents the hardware values of the local CPU, which can change during
CPU migration in a big-little system.

While one may call this fragile, there is at least some degree of
predictability around it. For example, if a VMM wanted to present
big-little to a guest, it could affine vCPUs accordingly to the correct
clusters.

All of this makes a giant mess out of adding support for making these
implementation ID registers writable. Avoid breaking the rather subtle
ABI around the old way of doing things by requiring opt-in from
userspace to make the registers writable.

When the cap is enabled, allow userspace to set MIDR, REVIDR, and AIDR
to any non-reserved value and present those values consistently across
all vCPUs.

Signed-off-by: Sebastian Ott <sebott@redhat.com>
[oliver: changelog, capability]
Link: https://lore.kernel.org/r/20250225005401.679536-5-oliver.upton@linux.dev
Signed-off-by: Oliver Upton <oliver.upton@linux.dev>

This commit is contained in:

Sebastian Ott

2025-02-26 01:32:16 -08:00

committed by

Oliver Upton

parent d0d81e03e6

commit 3adaee7830

6 changed files with 78 additions and 7 deletions

									
										include/uapi/linux/kvm.h
									
		+1
		
												View File
												
				@@ -929,6 +929,7 @@ struct kvm_enable_cap {

				#define KVM_CAP_PRE_FAULT_MEMORY 236

				#define KVM_CAP_X86_APIC_BUS_CYCLES_NS 237

				#define KVM_CAP_X86_GUEST_MODE 238

				#define KVM_CAP_ARM_WRITABLE_IMP_ID_REGS 239

				struct kvm_irq_routing_irqchip {

					__u32 irqchip;