On Wed, 08 May 2024 15:25:01 +0200, Julian Stecklina wrote:
> When a vCPU is interrupted by a signal while running a nested guest,
> KVM will exit to userspace with L2 state. However, userspace has no
> way to know whether it sees L1 or L2 state (besides calling
> KVM_GET_STATS_FD, which does not have a stable ABI).
>
> This causes multiple problems:
>
> [...]
Applied to kvm-x86 misc. Note, the capability got number 237, as 236 was
claimed by KVM_CAP_X86_APIC_BUS_CYCLES_NS. The number might also change again,
e.g. if a different arch adds a capability and x86 loses the race.
Thanks!
[1/1] KVM: x86: add KVM_RUN_X86_GUEST_MODE kvm_run flag
https://github.com/kvm-x86/linux/commit/85542adb65ec
--
https://github.com/kvm-x86/linux/tree/next
