KVM: selftests: Stress save+restore and #PF (ft. nested)
v3 cover KVM: selftests: Stress save+restore and #PF (ft. nested)
Add a stress test for save+restore while the guest is triggering and handling #PFs, in both L1 and L2. The goal was to create a generic selftest that would catch bugs like the one fixed by commit 5c247d08bc81 ("KVM: nSVM: Use vcpu->arch.cr2 when updating vmcb12 on nested #VMEXIT"), instead of relying on high-level testing (e.g. building GCC in L2) to catch it.
The test tries to be as generic as possible by triggering #PFs in a guest and installing a proper #PF handler, while the host is continuously doing save+restore cycles. Exiting to userspace is randomly triggered by a second thread that constantly signals the vCPU thread.
Patches (1-6) are prep patches, fixing GPR switching for nSVM and generalizing it to cover nVMX, which is needed for the test to run properly with nVMX. Patch 4 removes HORRIFIC_L2_UCALL_CLOBBER_HACK, as it is no longer needed. While this series does not have the "complete" fix added by commit 6783ca4105a7 ("KVM: selftests: Add a shameful hack to preserve/clobber GPRs across ucall"), it's a good step in the right direction.
Patches (7-10) add the actual test. The test is first introduced as a simple (read: dummy) stress test that just explicitly syncs to userspace after each #PF handling to do save+restore, then gradually evolves to add the random signaling and nested support. After the last patch, the test reliably reproduces the CR2 bug.
v2 -> v3:
- Rebased on top of L2 stack rework in selftests.
- Fix GPR array size (i.e. NR_GUEST_REGS) [Sashiko].
- Handle evmcs_vmlaunch() and evmcs_vmresume() [Sashiko].
- Fix off-by-one assertion error in intermediate patches.
- Increase inter-signal delay from 100us to 1msec.
v1 -> v2:
- Switch guest_regs to an array, which simplifies the offsets calculation and forgoes the dependency on using OFFSET() or defining the struct offsets for assembly otherwise.
- Move page table mapping to the test (instead of a generic helper), as the helper mistakenly tried to map the entire memslot, not just page tables.
- Do not use identity mappings for page tables as it collisions with GVAs used for ELF in some cases.
- Simplify page table walking by using loops.
- Make sure the signals are ignored before creating the signaling thread [Sashiko]
- Assert that the guest actually ran and had page faults [Sashiko]
- Add a patch to fix RAX and RFLAGS offsets in run_guest() [Sashiko]
- Initialize exception_has_payload when injecting a #UD [Sashiko]
- Only check KVM_STATE_NESTED_GUEST_MODE when running in nested mode [Sashiko]
v1: https://lore.kernel.org/all/[email protected]/
v2: https://lore.kernel.org/kvm/[email protected]/
Yosry Ahmed (10):
KVM: selftests: Move STR() and XSTR() definitions to test_util.h
KVM: selftests: Fix RAX and RFLAGS VMCB offsets when running L2
KVM: selftests: Use an array for guest_regs (and fix offsets)
KVM: selftests: Move GPR load/save definitions outside of nSVM code
KVM: selftests: Reuse GPR switching logic for nVMX
KVM: selftests: Drop HORRIFIC_L2_UCALL_CLOBBER_HACK
KVM: selftests: Add basic stress test for save+restore and #PF
handling
KVM: selftests: Trigger save+restore randomly in the #PF stress test
KVM: selftests: Support running stress save+restore and #PF test in L2
KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test
tools/testing/selftests/kvm/Makefile.kvm | 1 + .../testing/selftests/kvm/include/test_util.h | 3 + .../testing/selftests/kvm/include/x86/evmcs.h | 40 +-- .../selftests/kvm/include/x86/processor.h | 55 ++- tools/testing/selftests/kvm/include/x86/vmx.h | 63 ++-- .../testing/selftests/kvm/lib/x86/processor.c | 2 + tools/testing/selftests/kvm/lib/x86/svm.c | 60 ++-- tools/testing/selftests/kvm/lib/x86/ucall.c | 32 +- .../kvm/x86/evmcs_smm_controls_test.c | 3 - tools/testing/selftests/kvm/x86/smm_test.c | 3 - .../kvm/x86/stress_save_restore_pf_test.c | 326 ++++++++++++++++++ 11 files changed, 441 insertions(+), 147 deletions(-) create mode 100644 tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c
base-commit: 50406d35f5635e1cc523e61409d57e851b5f5df8
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
PATCH v3 1/10 KVM: selftests: Move STR() and XSTR() definitions to test_util.h
The macros are defined in two tests, and future changes will use them elsewhere. Move their definition into test_util.h to deduplicate them.
No functional change intended.
--- tools/testing/selftests/kvm/include/test_util.h | 3 +++ tools/testing/selftests/kvm/x86/evmcs_smm_controls_test.c | 3 --- tools/testing/selftests/kvm/x86/smm_test.c | 3 --- 3 files changed, 3 insertions(+), 6 deletions(-)
tools/testing/selftests/kvm/include/test_util.h +3 -0
@@ -240,4 +240,7 @@ char *strdup_printf(const char *fmt, ...) __attribute__((format(printf, 1, 2), nchar *sys_get_cur_clocksource (void ); +#define STR (x) #x +#define XSTR (x) STR(x) +#endif /* SELFTEST_KVM_TEST_UTIL_H */
tools/testing/selftests/kvm/x86/evmcs_smm_controls_test.c +0 -3
@@ -22,9 +22,6 @@#define SYNC_PORT 0xe -#define STR (x) #x -#define XSTR (s) STR(s) -/* * SMI handler: runs in real-address mode. * Reports SMRAM_STAGE via port IO, then does RSM.
tools/testing/selftests/kvm/x86/smm_test.c +0 -3
@@ -22,9 +22,6 @@#define SMRAM_GPA 0x1000000#define SMRAM_STAGE 0xfe -#define STR (x) #x -#define XSTR (s) STR(s) -#define SYNC_PORT 0xe#define DONE 0xff
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
Sean Christopherson
maintainerRe: [PATCH v3 01/10] KVM: selftests: Move STR() and XSTR() definitions to test_util.h
Quoted 2 lines · Yosry Ahmed
The macros are defined in two tests, and future changes will use them elsewhere. Move their definition into
test_util.hto deduplicate them.
Even better, just include tools/include/linux/stringify.h and use __stringify().
PATCH v3 2/10 KVM: selftests: Fix RAX and RFLAGS VMCB offsets when running L2
In reply to Yosry AhmedThe offsets used (0x170 and 0x1f8) are offsets within vmcb_save_area, not vmcb. The correct offsets should include the base of vmcb_save_area within vmcb (which is 0x400 -- so 0x570 and 0x5f8).
Instead of just correcting the offsets, use vmcb->save.rax and vmcb->save.rflags as parameters to the asm block and avoid hardcoding offsets completely. While at it, also use guest_regs.rax directly instead of assuming it's at offset 0 of guest_regs.
Note: "+m" must be used for vmcb_rax and vmcb_rflags, as caching those fields in registers would be wrong as the underlying KVM will update them in memory.
The same problem was recently fixed (differently) for kvm-unit-tests [1].
[1]https://lore.kernel.org/all/[email protected]/
--- tools/testing/selftests/kvm/lib/x86/svm.c | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-)
tools/testing/selftests/kvm/lib/x86/svm.c +11 -8
@@ -164,19 +164,22 @@ void run_guest(struct vmcb *vmcb, u64 vmcb_gpa) { asmvolatile ("vmload %[vmcb_gpa]\n\t" -"mov rflags, %%r15\n\t" // rflags -"mov %%r15, 0x170(%[vmcb])\n\t" -"mov guest_regs, %%r15\n\t" // rax -"mov %%r15, 0x1f8(%[vmcb])\n\t" +"mov rflags, %%r15\n\t" +"mov %%r15, %[vmcb_rflags]\n\t" +"mov %[guest_regs_rax], %%r15\n\t" +"mov %%r15, %[vmcb_rax]\n\t" LOAD_GPR_C "vmrun %[vmcb_gpa]\n\t" SAVE_GPR_C -"mov 0x170(%[vmcb]), %%r15\n\t" // rflags +"mov %[vmcb_rflags], %%r15\n\t" "mov %%r15, rflags\n\t" -"mov 0x1f8(%[vmcb]), %%r15\n\t" // rax -"mov %%r15, guest_regs\n\t" +"mov %[vmcb_rax], %%r15\n\t" // rax +"mov %%r15, %[guest_regs_rax]\n\t" "vmsave %[vmcb_gpa]\n\t" - : : [vmcb]"r" (vmcb), [vmcb_gpa]"a" (vmcb_gpa) + : [vmcb_rflags]"+m" (vmcb->save.rflags), + [vmcb_rax]"+m" (vmcb->save.rax), + [guest_regs_rax]"+rm" (guest_regs.rax) + : [vmcb_gpa]"a" (vmcb_gpa) :"r15" ,"memory" ); }
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
PATCH v3 3/10 KVM: selftests: Use an array for guest_regs (and fix offsets)
In reply to Yosry AhmedThe assembly code defined by SAVE_GPR_C uses the wrong offsets for some registers in guest_regs. For example, the offset of RCX should 0x08 not 0x10. Also, the last offset in the struct (R15) is 0x78, not 0x80, so the code actually saves and restore beyond the end of gpr64_regs.
Eliminate hardcoded offsets by using an array instead of a struct (similar to KVM's per-vCPU regs), and use the array index to generate the offset. While at it, rename SAVE_GPR_C and LOAD_GPR_C to a single macro, SVM_SWITCH_GPRS_ASM.
--- .../selftests/kvm/include/x86/processor.h | 36 +++++++------- tools/testing/selftests/kvm/lib/x86/svm.c | 47 ++++++++++--------- 2 files changed, 41 insertions(+), 42 deletions(-)
tools/testing/selftests/kvm/include/x86/processor.h +17 -19
@@ -396,25 +396,23 @@ static inline unsigned int x86_model(unsigned int eax)#define PTE_GET_PA (pte) ((pte) & PHYSICAL_PAGE_MASK)#define PTE_GET_PFN (pte) (PTE_GET_PA(pte) >> PAGE_SHIFT) -/* General Registers in 64-Bit Mode */ -struct gpr64_regs { -u64 rax; -u64 rcx; -u64 rdx; -u64 rbx; -u64 rsp; -u64 rbp; -u64 rsi; -u64 rdi; -u64 r8; -u64 r9; -u64 r10; -u64 r11; -u64 r12; -u64 r13; -u64 r14; -u64 r15; -}; +#define GUEST_REGS_RAX 0 +#define GUEST_REGS_RCX 1 +#define GUEST_REGS_RDX 2 +#define GUEST_REGS_RBX 3 +#define GUEST_REGS_RSP 4 +#define GUEST_REGS_RBP 5 +#define GUEST_REGS_RSI 6 +#define GUEST_REGS_RDI 7 +#define GUEST_REGS_R8 8 +#define GUEST_REGS_R9 9 +#define GUEST_REGS_R10 10 +#define GUEST_REGS_R11 11 +#define GUEST_REGS_R12 12 +#define GUEST_REGS_R13 13 +#define GUEST_REGS_R14 14 +#define GUEST_REGS_R15 15 +#define NR_GUEST_REGS (GUEST_REGS_R15 + 1)struct desc64 {u16 limit0;
tools/testing/selftests/kvm/lib/x86/svm.c +24 -23
85 lines not on this page · raw message
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
Sean Christopherson
maintainerRe: [PATCH v3 03/10] KVM: selftests: Use an array for guest_regs (and fix offsets)
Quoted 50 lines · Yosry Ahmed
The assembly code defined by
SAVE_GPR_Cuses the wrong offsets for some registers inguest_regs. For example, the offset of RCX should0x08not0x10. Also, the last offset in the struct (R15) is0x78, not0x80, so the code actually saves and restore beyond the end ofgpr64_regs.Eliminate hardcoded offsets by using an array instead of a struct (similar to KVM's per-vCPU regs), and use the array index to generate the offset. While at it, rename
SAVE_GPR_CandLOAD_GPR_Cto a single macro,SVM_SWITCH_GPRS_ASM.Signed-off-by Yosry Ahmed <[email protected]>--- .../selftests/kvm/include/x86/processor.h | 36 +++++++------- tools/testing/selftests/kvm/lib/x86/svm.c | 47 ++++++++++--------- 2 files changed, 41 insertions(+), 42 deletions(-)tools/testing/selftests/kvm/include/x86/processor.h +7
-19@@ -396,25 +396,23 @@ static inline unsigned int x86_model(unsigned int eax)#define PTE_GET_PA (pte) ((pte) & PHYSICAL_PAGE_MASK)#define PTE_GET_PFN (pte) (PTE_GET_PA(pte) >> PAGE_SHIFT) -/* General Registers in 64-Bit Mode */ -struct gpr64_regs { -u64 rax; -u64 rcx; -u64 rdx; -u64 rbx; -u64 rsp; -u64 rbp; -u64 rsi; -u64 rdi; -u64 r8; -u64 r9; -u64 r10; -u64 r11; -u64 r12; -u64 r13; -u64 r14; -u64 r15; -}; +#define GUEST_REGS_RAX 0 +#define GUEST_REGS_RCX 1 +#define GUEST_REGS_RDX 2 +#define GUEST_REGS_RBX 3 +#define GUEST_REGS_RSP 4 +#define GUEST_REGS_RBP 5 +#define GUEST_REGS_RSI 6
tools/testing/selftests/kvm/include/x86/processor.h static inline unsigned int x86_model(unsigned int eax) · line 415
Quoted 10 lines
tools/testing/selftests/kvm/include/x86/processor.h +10
-0+#define GUEST_REGS_RDI 7 +#define GUEST_REGS_R8 8 +#define GUEST_REGS_R9 9 +#define GUEST_REGS_R10 10 +#define GUEST_REGS_R11 11 +#define GUEST_REGS_R12 12 +#define GUEST_REGS_R13 13 +#define GUEST_REGS_R14 14 +#define GUEST_REGS_R15 15 +#define NR_GUEST_REGS (GUEST_REGS_R15 + 1)
Eh, these aren't guest specific, they're architectural x86 values. Ideally, KVM's own VCPU_REGS_xxx would be X86_REGS_xxx, which is possible now that KVM doesn't do pretend RIP is a GPR.
I also prefer arch/x86/include/asm/kvm_host.h's approach of using an enum, e.g.
enum x86_general_purpose_reg {
X86_REGS_RAX,
X86_REGS_RCX,
X86_REGS_RDX,
X86_REGS_RBX,
X86_REGS_RSP,
X86_REGS_RBP,
X86_REGS_RSI,
X86_REGS_RDI,
X86_REGS_R8,
X86_REGS_R9,
X86_REGS_R10,
X86_REGS_R11,
X86_REGS_R12,
X86_REGS_R13,
X86_REGS_R14,
X86_REGS_R15,
NR_X86_GENERAL_PURPOSE_REGS,
};And I think it makes sense to squeeze this in with the other architectural definitions, e.g.
testing/selftests/kvm/include/x86/processor.h +20 -0
@@ -57,6 +57,26 @@ const char *ex_str(int vector);#define X86_EFLAGS_VIP BIT(20)/* Virtual Interrupt Pending */ #define X86_EFLAGS_ID BIT(21)/* CPUID detection */ +enum x86_general_purpose_reg { +X86_REGS_RAX , +VCPU_REGS_RCX , +VCPU_REGS_RDX , +VCPU_REGS_RBX , +VCPU_REGS_RSP , +VCPU_REGS_RBP , +VCPU_REGS_RSI , +VCPU_REGS_RDI , +VCPU_REGS_R8 , +VCPU_REGS_R9 , +VCPU_REGS_R10 , +VCPU_REGS_R11 , +VCPU_REGS_R12 , +VCPU_REGS_R13 , +VCPU_REGS_R14 , +VCPU_REGS_R15 , +NR_X86_GENERAL_PURPOSE_REGS , +}; +#define X86_CR4_VME (1ul << 0)#define X86_CR4_PVI (1ul << 1)#define X86_CR4_TSD (1ul << 2)
Re: [PATCH v3 03/10] KVM: selftests: Use an array for guest_regs (and fix offsets)
Quoted 58 lines · Sean Christopherson
Quoted 56 lines · Yosry Ahmed
The assembly code defined by
SAVE_GPR_Cuses the wrong offsets for some registers inguest_regs. For example, the offset of RCX should0x08not0x10. Also, the last offset in the struct (R15) is0x78, not0x80, so the code actually saves and restore beyond the end ofgpr64_regs.Eliminate hardcoded offsets by using an array instead of a struct (similar to KVM's per-vCPU regs), and use the array index to generate the offset. While at it, rename
SAVE_GPR_CandLOAD_GPR_Cto a single macro,SVM_SWITCH_GPRS_ASM.Signed-off-by Yosry Ahmed <[email protected]>--- .../selftests/kvm/include/x86/processor.h | 36 +++++++------- tools/testing/selftests/kvm/lib/x86/svm.c | 47 ++++++++++--------- 2 files changed, 41 insertions(+), 42 deletions(-)tools/testing/selftests/kvm/include/x86/processor.h +13
-19@@ -396,25 +396,23 @@ static inline unsigned int x86_model(unsigned int eax)#define PTE_GET_PA (pte) ((pte) & PHYSICAL_PAGE_MASK)#define PTE_GET_PFN (pte) (PTE_GET_PA(pte) >> PAGE_SHIFT) -/* General Registers in 64-Bit Mode */ -struct gpr64_regs { -u64 rax; -u64 rcx; -u64 rdx; -u64 rbx; -u64 rsp; -u64 rbp; -u64 rsi; -u64 rdi; -u64 r8; -u64 r9; -u64 r10; -u64 r11; -u64 r12; -u64 r13; -u64 r14; -u64 r15; -}; +#define GUEST_REGS_RAX 0 +#define GUEST_REGS_RCX 1 +#define GUEST_REGS_RDX 2 +#define GUEST_REGS_RBX 3 +#define GUEST_REGS_RSP 4 +#define GUEST_REGS_RBP 5 +#define GUEST_REGS_RSI 6 +#define GUEST_REGS_RDI 7 +#define GUEST_REGS_R8 8 +#define GUEST_REGS_R9 9 +#define GUEST_REGS_R10 10 +#define GUEST_REGS_R11 11 +#define GUEST_REGS_R12 12
Quoted 8 lines
tools/testing/selftests/kvm/include/x86/processor.h static inline unsigned int x86_model(unsigned int eax) · line 415
Quoted 4 lines
tools/testing/selftests/kvm/include/x86/processor.h +4
-0+#define GUEST_REGS_R13 13 +#define GUEST_REGS_R14 14 +#define GUEST_REGS_R15 15 +#define NR_GUEST_REGS (GUEST_REGS_R15 + 1)Eh, these aren't guest specific, they're architectural x86 values. Ideally, KVM's own
VCPU_REGS_xxxwould beX86_REGS_xxx, which is possible now that KVM doesn't do pretend RIP is a GPR.
I just called these GUEST_REGS_* because they are used to index guest_regs, but yeah I can name them X86_REGS_*.
Quoted 14 lines
I also prefer arch/x86/include/asm/kvm_host.h's approach of using an enum, e.g.
enum x86_general_purpose_reg { X86_REGS_RAX, X86_REGS_RCX, X86_REGS_RDX, X86_REGS_RBX, X86_REGS_RSP, X86_REGS_RBP, X86_REGS_RSI, X86_REGS_RDI, X86_REGS_R8, X86_REGS_R9,
Quoted 8 lines
X86_REGS_R10,
X86_REGS_R11,
X86_REGS_R12,
X86_REGS_R13,
X86_REGS_R14,
X86_REGS_R15,
NR_X86_GENERAL_PURPOSE_REGS,
};Oh I wanted to, but the compiler wouldn't let me use enum values directly in the preprocessor, see:
https://lore.kernel.org/kvm/CAO9r8zPz8WbijVN6mgLb8OaU6=tNSSz1NgNBjZCsC36D4+TO+w@mail.gmail.com/.
I can do an enum *and* macros using enum values if you prefer so, like:
#define __GUEST_REGS_RAX 0
...
enum guest_regs {
GUEST_REGS_RAX = __GUEST_REGS_RAX,
...
NR_GUEST_REGS,
};
Sean Christopherson
maintainerRe: [PATCH v3 03/10] KVM: selftests: Use an array for guest_regs (and fix offsets)
Quoted 7 lines · Yosry Ahmed
On Fri, Jul 24, 2026 at 8:33 AM Sean Christopherson <[email protected]> wrote:
Oh I wanted to, but the compiler wouldn't let me use enum values directly in the preprocessor, see:
https://lore.kernel.org/kvm/CAO9r8zPz8WbijVN6mgLb8OaU6=tNSSz1NgNBjZCsC36D4+TO+w@mail.gmail.com/.I can do an enum *and* macros using enum values if you prefer so, like:
Quoted 8 lines
#define
__GUEST_REGS_RAX0
...enum
guest_regs{
GUEST_REGS_RAX=__GUEST_REGS_RAX,
...
NR_GUEST_REGS,
};
I would much rather follow KUT's lib/x86/virt.h, and provide asm constraints for the offsets. Actually, my vote is to copy+paste KUT's entire approach, and provide:
struct guest_regs {
u64 rax;
u64 rcx;
u64 rdx;
u64 rbx;
/*
* Use RSP's index to hold CR2, as RSP isn't manually context switched
* by software in any relevant flows.
*
* FIXME: Actually context switch CR2 on Intel.
*/
u64 cr2;
u64 rbp;
u64 rsi;
u64 rdi;
u64 r8;
u64 r9;
u64 r10;
u64 r11;
u64 r12;
u64 r13;
u64 r14;
u64 r15;
u64 rflags;};
Using an array for the GPRs is only valuable when the code *needs* to index the GPRs based on their index, e.g. like KVM needs to do when emulating instructions. But for "normal" software, using an array just makes the code kludgy.
E.g. this
vmcb->save.rip = (u64)guest_rip; vmcb->save.rsp = (u64)svm->stack; guest_regs.rdi = (u64)svm;
versus
vmcb->save.rip = (u64)guest_rip; vmcb->save.rsp = (u64)svm->stack; guest_regs[X86_REGS_RDI] = (u64)svm;
Re: [PATCH v3 03/10] KVM: selftests: Use an array for guest_regs (and fix offsets)
Quoted 12 lines · Sean Christopherson
Quoted 10 lines · Yosry Ahmed
On Fri, Jul 24, 2026 at 8:33 AM Sean Christopherson <[email protected]> wrote:
Oh I wanted to, but the compiler wouldn't let me use enum values directly in the preprocessor, see:
https://lore.kernel.org/kvm/CAO9r8zPz8WbijVN6mgLb8OaU6=tNSSz1NgNBjZCsC36D4+TO+w@mail.gmail.com/.I can do an enum *and* macros using enum values if you prefer so, like:
#define
__GUEST_REGS_RAX0
...
Quoted 8 lines
Quoted 5 lines
enum
guest_regs{
GUEST_REGS_RAX=__GUEST_REGS_RAX,
...
NR_GUEST_REGS,
};I would much rather follow KUT's
lib/x86/virt.h, and provide asm constraints for the offsets.
I actually did this initially (without knowing it's what KUT does), I did not like the asm constraint, and I think I may have run into a limit on the number of operands. But yeah if we are already doing this for KUT let me try it again and see if I can make it work.
Quoted 43 lines
Actually, my vote is to copy+paste KUT's entire approach, and provide:
struct guest_regs { u64 rax; u64 rcx; u64 rdx; u64 rbx; /* * Use RSP's index to hold CR2, as RSP isn't manually context switched * by software in any relevant flows. * * FIXME: Actually context switch CR2 on Intel. */ u64 cr2; u64 rbp; u64 rsi; u64 rdi; u64 r8; u64 r9; u64 r10; u64 r11; u64 r12; u64 r13; u64 r14; u64 r15; u64 rflags;};
Using an array for the GPRs is only valuable when the code *needs* to index the GPRs based on their index, e.g. like KVM needs to do when emulating instructions. But for "normal" software, using an array just makes the code kludgy.
E.g. this
vmcb->save.rip = (u64)guest_rip; vmcb->save.rsp = (u64)svm->stack; guest_regs.rdi = (u64)svm;versus
vmcb->save.rip = (u64)guest_rip; vmcb->save.rsp = (u64)svm->stack; guest_regs[X86_REGS_RDI] = (u64)svm;
PATCH v3 4/10 KVM: selftests: Move GPR load/save definitions outside of nSVM code
In reply to Yosry AhmedIn preparation for reusing the code for nVMX tests, move the guest_regs array declaration as well as GPR switching macro to processor.h.
No functional change intended.
--- tools/testing/selftests/kvm/include/x86/processor.h | 5 +++++ tools/testing/selftests/kvm/lib/x86/processor.c | 2 ++ tools/testing/selftests/kvm/lib/x86/svm.c | 4 ---- 3 files changed, 7 insertions(+), 4 deletions(-)
tools/testing/selftests/kvm/include/x86/processor.h +5 -0
@@ -414,6 +414,11 @@ static inline unsigned int x86_model(unsigned int eax)#define GUEST_REGS_R15 15#define NR_GUEST_REGS (GUEST_REGS_R15 + 1) +extern u64 guest_regs[NR_GUEST_REGS ]; + +#define GUEST_SWITCH_GPR_ASM (reg, idx) \ + "xchg %%" #reg ", guest_regs + 8 *" XSTR(idx) "\n\t" +struct desc64 {u16 limit0;u16 base0;
tools/testing/selftests/kvm/lib/x86/processor.c +2 -0
@@ -29,6 +29,8 @@ bool host_cpu_is_amd_compatible;bool is_forced_emulation_enabled;u64 guest_tsc_khz; +u64 guest_regs[NR_GUEST_REGS ]; +const char *ex_str (int vector) {switch (vector) {
tools/testing/selftests/kvm/lib/x86/svm.c +0 -4
@@ -13,7 +13,6 @@#define SEV_DEV_PATH "/dev/sev" -u64 guest_regs[NR_GUEST_REGS ];u64 rflags;/* Allocate memory regions for nested SVM tests.
@@ -133,9 +132,6 @@ void generic_svm_setup(struct svm_test_data *svm, void *guest_rip) } } -#define GUEST_SWITCH_GPR_ASM (reg, idx) \ - "xchg %%" #reg ", guest_regs + 8 *" XSTR(idx) "\n\t" -/* * save/restore 64-bit general registers except rax, rip, rsp * which are directly handed through the VMCB guest processor state
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
PATCH v3 5/10 KVM: selftests: Reuse GPR switching logic for nVMX
In reply to Yosry AhmedReuse the GPR switching logic for nVMX by defining VMX_SWITCH_GPRS_ASM, which is essentially the same as SVM_SWITCH_GPRS_ASM but also switches RAX, replacing the push/pop of a subset of the registers.
The long clobber list of registers is no longer needed as registers are saved and restored appropriately (and not clobbered by L2).
Define VMX_SWITCH_GPRS_ASM before including evmcs.h, such that it can be used by evmcs_vmlaunch() and evmcs_vmresume().
--- .../testing/selftests/kvm/include/x86/evmcs.h | 40 ++++-------- tools/testing/selftests/kvm/include/x86/vmx.h | 63 +++++++++---------- 2 files changed, 41 insertions(+), 62 deletions(-)
tools/testing/selftests/kvm/include/x86/evmcs.h +12 -28
@@ -1207,30 +1207,22 @@ static inline int evmcs_vmlaunch(void) current_evmcs->hv_clean_fields =0 ; - __asm__ __volatile__("push %%rbp;" -"push %%rcx;" -"push %%rdx;" -"push %%rsi;" -"push %%rdi;" -"push $0;" + __asm__ __volatile__("push $0;" "mov %%rsp, (%[host_rsp]);" "lea 1f(%%rip), %%rax;" "mov %%rax, (%[host_rip]);" +VMX_SWITCH_GPRS_ASM "vmlaunch;" "incq (%%rsp);" -"1: pop %%rax;" -"pop %%rdi;" -"pop %%rsi;" -"pop %%rdx;" -"pop %%rcx;" -"pop %%rbp;" +"1: ;" +VMX_SWITCH_GPRS_ASM +"pop %%rax;" : [ret]"=&a" (ret) : [host_rsp]"r" ((u64)¤t_evmcs->host_rsp), [host_rip]"r" ((u64)¤t_evmcs->host_rip) - :"memory" ,"cc" ,"rbx" ,"r8" ,"r9" ,"r10" , -"r11" ,"r12" ,"r13" ,"r14" ,"r15" ); + :"memory" ,"cc" );return ret; }
@@ -1246,30 +1238,22 @@ static inline int evmcs_vmresume(void)/* HOST_RSP */ current_evmcs->hv_clean_fields &= ~HV_VMX_ENLIGHTENED_CLEAN_FIELD_HOST_POINTER ; - __asm__ __volatile__("push %%rbp;" -"push %%rcx;" -"push %%rdx;" -"push %%rsi;" -"push %%rdi;" -"push $0;" + __asm__ __volatile__("push $0;" "mov %%rsp, (%[host_rsp]);" "lea 1f(%%rip), %%rax;" "mov %%rax, (%[host_rip]);" +VMX_SWITCH_GPRS_ASM "vmresume;" "incq (%%rsp);" -"1: pop %%rax;" -"pop %%rdi;" -"pop %%rsi;" -"pop %%rdx;" -"pop %%rcx;" -"pop %%rbp;" +"1: ;" +VMX_SWITCH_GPRS_ASM +"pop %%rax;" : [ret]"=&a" (ret) : [host_rsp]"r" ((u64)¤t_evmcs->host_rsp), [host_rip]"r" ((u64)¤t_evmcs->host_rip) - :"memory" ,"cc" ,"rbx" ,"r8" ,"r9" ,"r10" , -"r11" ,"r12" ,"r13" ,"r14" ,"r15" ); + :"memory" ,"cc" );return ret; }
tools/testing/selftests/kvm/include/x86/vmx.h +29 -34
106 lines not on this page · raw message
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
[email protected]
AI reviewRe: [PATCH v3 05/10] KVM: selftests: Reuse GPR switching logic for nVMX
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Medium] The newly introduced VMX_SWITCH_GPRS_ASM logic makes vmlaunch and vmresume thread-unsafe…
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly introduced VMX_SWITCH_GPRS_ASM logic makes vmlaunch and vmresume thread-unsafe, corrupting L1 host and L2 guest register state in multi-vCPU nested tests. --
commit f53344a36faa652dd7b5c7d1e749a4bffbc5242b
Author: Yosry Ahmed <[email protected]>
KVM: selftests: Reuse GPR switching logic for nVMX
This commit introduces VMX_SWITCH_GPRS_ASM to reuse the GPR switching logic from SVM for nVMX. It replaces the push/pop of registers with VMX_SWITCH_GPRS_ASM during vmlaunch and vmresume operations for both standard and enlightened VMCS.
Quoted 4 lines
tools/testing/selftests/kvm/include/x86/vmx.h +0
-0
[ ... ]
Quoted 6 lines
tools/testing/selftests/kvm/include/x86/vmx.h +0
-2@@ -373,34 +387,23 @@ static inline int vmlaunch(void)if (enable_evmcs)return evmcs_vmlaunch (); - __asm__ __volatile__("push %%rbp;" - "push %%rcx;"
tools/testing/selftests/kvm/include/x86/vmx.h static inline int vmlaunch(void) · line 395
Quoted 10 lines
tools/testing/selftests/kvm/include/x86/vmx.h +2
-4-"push %%rdx;" -"push %%rsi;" -"push %%rdi;" -"push $0;" + __asm__ __volatile__("push $0;" "vmwrite %%rsp, %[host_rsp];" "lea 1f(%%rip), %%rax;" "vmwrite %%rax, %[host_rip];" +VMX_SWITCH_GPRS_ASM "vmlaunch;"
[Severity: Medium]
Will this replacement make vmlaunch() thread-unsafe in multi-vCPU nested tests?
Since VMX_SWITCH_GPRS_ASM uses GUEST_SWITCH_GPR_ASM which operates on a single shared guest_regs array in L1 memory, concurrent executions by multiple vCPUs (e.g., via memstress_l2_guest_entry) could clobber the saved host state and L2 initial state for all but one vCPU.
The previous push/pop sequence was thread-safe since it used the stack. Does this same thread-safety issue apply to vmresume() and the evmcs variants that also adopted this macro?
Quoted 18 lines
tools/testing/selftests/kvm/include/x86/vmx.h +4
-8"incq (%%rsp);" -"1: pop %%rax;" -"pop %%rdi;" -"pop %%rsi;" -"pop %%rdx;" -"pop %%rcx;" -"pop %%rbp;" +"1: ;" +VMX_SWITCH_GPRS_ASM +"pop %%rax;" : [ret]"=&a"(ret) : [host_rsp]"r"((u64)HOST_RSP), [host_rip]"r"((u64)HOST_RIP) - : "memory", "cc", "rbx", "r8", "r9", "r10", - "r11", "r12", "r13", "r14", "r15"); + : "memory", "cc"); return ret; }
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=5
Re: [PATCH v3 05/10] KVM: selftests: Reuse GPR switching logic for nVMX
Quoted 40 lines · On Mon, Jun 29, 2026 at 06:49:31PM +0000, [email protected] wrote:
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly introducedVMX_SWITCH_GPRS_ASMlogic makes vmlaunch and vmresume thread-unsafe, corrupting L1 host and L2 guest register state in multi-vCPU nested tests. --commit
f53344a36faa652dd7b5c7d1e749a4bffbc5242b
Author: Yosry Ahmed <[email protected]>KVM: selftests: Reuse GPR switching logic for nVMX
This commit introduces
VMX_SWITCH_GPRS_ASMto reuse the GPR switching logic from SVM for nVMX. It replaces the push/pop of registers withVMX_SWITCH_GPRS_ASMduring vmlaunch and vmresume operations for both standard and enlightened VMCS.Quoted 4 lines
tools/testing/selftests/kvm/include/x86/vmx.h +0
-0[ ... ]
Quoted 6 lines
tools/testing/selftests/kvm/include/x86/vmx.h +0
-2@@ -373,34 +387,23 @@ static inline int vmlaunch(void)if (enable_evmcs)return evmcs_vmlaunch (); - __asm__ __volatile__("push %%rbp;" - "push %%rcx;"tools/testing/selftests/kvm/include/x86/vmx.h static inline int vmlaunch(void) · line 395
Quoted 10 lines
tools/testing/selftests/kvm/include/x86/vmx.h +2
-4-"push %%rdx;" -"push %%rsi;" -"push %%rdi;" -"push $0;" + __asm__ __volatile__("push $0;" "vmwrite %%rsp, %[host_rsp];" "lea 1f(%%rip), %%rax;" "vmwrite %%rax, %[host_rip];" +VMX_SWITCH_GPRS_ASM "vmlaunch;"[Severity: Medium]
Will this replacement makevmlaunch()thread-unsafe in multi-vCPU nested tests?
Quoted 8 lines
Since
VMX_SWITCH_GPRS_ASMusesGUEST_SWITCH_GPR_ASMwhich operates on a single sharedguest_regsarray in L1 memory, concurrent executions by multiple vCPUs (e.g., viamemstress_l2_guest_entry) could clobber the saved host state and L2 initial state for all but one vCPU.The previous push/pop sequence was thread-safe since it used the stack. Does this same thread-safety issue apply to
vmresume()and the evmcs variants that also adopted this macro?
Yes, I should have explicitly called this out. This replaces the apparently thread-safe push/pop sequence with reusing the GPR switching logic in SVM, which isn't thread-safe at all (uses a global array).
However this is still an improvement imo because:
- The logic here is half-baked and prompts the UCALL clobber hack as it doesn't properly save/restore everything. Reusing the GPR switching logic used by SVM allows us to drop that hack.
- It's more likely (imo) that we hit a problem due to the half-baked GPR save/restore logic than thread-safety. This is evidently true by the fact that the stress test added in this series fails on VMX with the existing push/pop sequence. OTOH, no tests are failing on SVM due to lack of thread-safety. There is only one test that uses more than one vCPU with nested anyway (the memstress test).
I think the logical next step is to move the GPR array to be per-vCPU, making it thread-safe for both VMX and SVM in a proper way, but this is outside the scope of this series.
Quoted 22 lines
Quoted 19 lines
tools/testing/selftests/kvm/include/x86/vmx.h +4
-8"incq (%%rsp);" -"1: pop %%rax;" -"pop %%rdi;" -"pop %%rsi;" -"pop %%rdx;" -"pop %%rcx;" -"pop %%rbp;" +"1: ;" +VMX_SWITCH_GPRS_ASM +"pop %%rax;" : [ret]"=&a"(ret) : [host_rsp]"r"((u64)HOST_RSP), [host_rip]"r"((u64)HOST_RIP) - : "memory", "cc", "rbx", "r8", "r9", "r10", - "r11", "r12", "r13", "r14", "r15"); + : "memory", "cc"); return ret; }Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=5
PATCH v3 6/10 KVM: selftests: Drop HORRIFIC_L2_UCALL_CLOBBER_HACK
In reply to Yosry AhmedNow that nVMX test codes preserves GPRs across nested VM-Exits (specifically RBP, RDX, and RDI among others), drop the ucall-specific hack to avoid clobbering these registers.
--- tools/testing/selftests/kvm/lib/x86/ucall.c | 32 ++------------------- 1 file changed, 2 insertions(+), 30 deletions(-)
tools/testing/selftests/kvm/lib/x86/ucall.c +2 -30
@@ -10,36 +10,8 @@void ucall_arch_do_ucall (gva_t uc) { -/* -* FIXME: Revert this hack (the entire commit that added it) once nVMX -* preserves L2 GPRs across a nested VM-Exit. If a ucall from L2, e.g. -* to do a GUEST_SYNC(), lands the vCPU in L1, any and all GPRs can be -* clobbered by L1. Save and restore non-volatile GPRs (clobbering RBP -* in particular is problematic) along with RDX and RDI (which are -* inputs), and clobber volatile GPRs. *sigh* -*/ -#define HORRIFIC_L2_UCALL_CLOBBER_HACK \ - "rcx", "rsi", "r8", "r9", "r10", "r11" - - asmvolatile ("push %%rbp\n\t" -"push %%r15\n\t" -"push %%r14\n\t" -"push %%r13\n\t" -"push %%r12\n\t" -"push %%rbx\n\t" -"push %%rdx\n\t" -"push %%rdi\n\t" -"in %[port], %%al\n\t" -"pop %%rdi\n\t" -"pop %%rdx\n\t" -"pop %%rbx\n\t" -"pop %%r12\n\t" -"pop %%r13\n\t" -"pop %%r14\n\t" -"pop %%r15\n\t" -"pop %%rbp\n\t" - : : [port] "d" (UCALL_PIO_PORT), "D" (uc) : "rax", "memory", - HORRIFIC_L2_UCALL_CLOBBER_HACK); + asmvolatile ("in %[port], %%al" + : : [port]"d" (UCALL_PIO_PORT ),"D" (uc) :"rax" ,"memory" ); }void *ucall_arch_get_ucall (struct kvm_vcpu *vcpu)
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
Sean Christopherson
maintainerRe: [PATCH v3 06/10] KVM: selftests: Drop HORRIFIC_L2_UCALL_CLOBBER_HACK
Quoted 5 lines · Yosry Ahmed
Now that nVMX test codes preserves GPRs across nested VM-Exits (specifically RBP, RDX, and RDI among others), drop the ucall-specific hack to avoid clobbering these registers.
Assisted-by Gemini:gemini-3.1-pro
Did Gemini really help you write this patch? It's ok if it did, I just want to be precise with documenting how AI was used so that when I get a patch that was indeed heavily helped by AI, I can actually key off the "AI was used" information for context when reviewing.
Quoted 51 lines
Signed-off-by Yosry Ahmed <[email protected]>--- tools/testing/selftests/kvm/lib/x86/ucall.c | 32 ++------------------- 1 file changed, 2 insertions(+), 30 deletions(-)tools/testing/selftests/kvm/lib/x86/ucall.c +2
-30@@ -10,36 +10,8 @@void ucall_arch_do_ucall (gva_t uc) { -/* -* FIXME: Revert this hack (the entire commit that added it) once nVMX -* preserves L2 GPRs across a nested VM-Exit. If a ucall from L2, e.g. -* to do a GUEST_SYNC(), lands the vCPU in L1, any and all GPRs can be -* clobbered by L1. Save and restore non-volatile GPRs (clobbering RBP -* in particular is problematic) along with RDX and RDI (which are -* inputs), and clobber volatile GPRs. *sigh* -*/ -#define HORRIFIC_L2_UCALL_CLOBBER_HACK \ - "rcx", "rsi", "r8", "r9", "r10", "r11" - - asmvolatile ("push %%rbp\n\t" -"push %%r15\n\t" -"push %%r14\n\t" -"push %%r13\n\t" -"push %%r12\n\t" -"push %%rbx\n\t" -"push %%rdx\n\t" -"push %%rdi\n\t" -"in %[port], %%al\n\t" -"pop %%rdi\n\t" -"pop %%rdx\n\t" -"pop %%rbx\n\t" -"pop %%r12\n\t" -"pop %%r13\n\t" -"pop %%r14\n\t" -"pop %%r15\n\t" -"pop %%rbp\n\t" - : : [port] "d" (UCALL_PIO_PORT), "D" (uc) : "rax", "memory", - HORRIFIC_L2_UCALL_CLOBBER_HACK); + asmvolatile ("in %[port], %%al" + : : [port]"d" (UCALL_PIO_PORT ),"D" (uc) :"rax" ,"memory" ); }void *ucall_arch_get_ucall (struct kvm_vcpu *vcpu)Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
Re: [PATCH v3 06/10] KVM: selftests: Drop HORRIFIC_L2_UCALL_CLOBBER_HACK
Quoted 6 lines · Sean Christopherson
Quoted 4 lines · Yosry Ahmed
Now that nVMX test codes preserves GPRs across nested VM-Exits (specifically RBP, RDX, and RDI among others), drop the ucall-specific hack to avoid clobbering these registers.
Quoted 6 lines
Quoted 1 line
Assisted-by Gemini:gemini-3.1-proDid Gemini really help you write this patch? It's ok if it did, I just want to be precise with documenting how AI was used so that when I get a patch that was indeed heavily helped by AI, I can actually key off the "AI was used" information for context when reviewing.
I am pretty sure I was just too lazy and prompted it to write it, even though it's effectively a git revert.
Quoted 2 lines
Quoted 2 lines
Signed-off-by Yosry Ahmed <[email protected]>
PATCH v3 7/10 KVM: selftests: Add basic stress test for save+restore and #PF handling
In reply to Yosry AhmedAdd a basic stress test for handling #PFs in a guest while the host is doing save+restore cycles. The guest periodically accesses non-present memory causing a #PF, and the #PF handler walks the page tables and updates the PTE to be present, like a proper #PF handler.
After every access (and #PF), the guest triggers a sync and the test performs save+restore of the VM. This is not very meaningful as save+restore are performed after the access and #PF handling complete, but following changes will change that.
--- tools/testing/selftests/kvm/Makefile.kvm | 1 + .../selftests/kvm/include/x86/processor.h | 14 ++ .../kvm/x86/stress_save_restore_pf_test.c | 182 ++++++++++++++++++ 3 files changed, 197 insertions(+) create mode 100644 tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c
tools/testing/selftests/kvm/Makefile.kvm +1 -0
@@ -111,6 +111,7 @@ TEST_GEN_PROGS_x86 += x86/set_sregs_test TEST_GEN_PROGS_x86 += x86/smaller_maxphyaddr_emulation_test TEST_GEN_PROGS_x86 += x86/smm_test TEST_GEN_PROGS_x86 += x86/state_test +TEST_GEN_PROGS_x86 += x86/stress_save_restore_pf_test TEST_GEN_PROGS_x86 += x86/vmx_preemption_timer_test TEST_GEN_PROGS_x86 += x86/svm_vmcall_test TEST_GEN_PROGS_x86 += x86/svm_int_ctl_test
tools/testing/selftests/kvm/include/x86/processor.h +14 -0
@@ -585,6 +585,15 @@ static inline void set_cr0(u64 val) __asm__ __volatile__("mov %0, %%cr0" : :"r" (val) :"memory" ); } +static inline u64 get_cr2 (void ) +{ +u64 cr2; + + __asm__ __volatile__("mov %%cr2, %[cr2]" + :/* output */ [cr2]"=r" (cr2)); +return cr2; +} +static inline u64 get_cr3 (void ) {u64 cr3;
@@ -880,6 +889,11 @@ static inline void write_sse_reg(int reg, const sse128_t *data) } } +static inline void invlpg (u64 addr) +{ + __asm__ __volatile__("invlpg (%0)" : :"r" (addr) :"memory" ); +} +static inline void cpu_relax (void ) { asmvolatile ("rep; nop" :::"memory" );
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +182 -0
182 lines not on this page · raw message
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
Sean Christopherson
maintainerRe: [PATCH v3 07/10] KVM: selftests: Add basic stress test for save+restore and #PF handling
Quoted 24 lines · Yosry Ahmed
Add a basic stress test for handling #PFs in a guest while the host is doing save+restore cycles. The guest periodically accesses non-present memory causing a #PF, and the #PF handler walks the page tables and updates the PTE to be present, like a proper #PF handler.
After every access (and #PF), the guest triggers a sync and the test performs save+restore of the VM. This is not very meaningful as save+restore are performed after the access and #PF handling complete, but following changes will change that.
Assisted-by Gemini:gemini-3.1-proSigned-off-by Yosry Ahmed <[email protected]>--- tools/testing/selftests/kvm/Makefile.kvm | 1 + .../selftests/kvm/include/x86/processor.h | 14 ++ .../kvm/x86/stress_save_restore_pf_test.c | 182 ++++++++++++++++++ 3 files changed, 197 insertions(+) create mode 100644 tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.ctools/testing/selftests/kvm/Makefile.kvm +0
-0
tools/testing/selftests/kvm/Makefile.kvm TEST_GEN_PROGS_x86 += x86/set_sregs_test · line 114
Quoted 4 lines
tools/testing/selftests/kvm/Makefile.kvm +1
-0@@ -111,6 +111,7 @@ TEST_GEN_PROGS_x86 += x86/set_sregs_test TEST_GEN_PROGS_x86 += x86/smaller_maxphyaddr_emulation_test TEST_GEN_PROGS_x86 += x86/smm_test TEST_GEN_PROGS_x86 += x86/state_test +TEST_GEN_PROGS_x86 += x86/stress_save_restore_pf_test
I'd rather go with just save_restore_pf_test, so that the focus of the test is at the beginning of the file name. E.g. I don't want to end up with a pile of stress_xyz tests, because that makes tab completion a pain in the ass.
I'd also be ok with save_restore_pf_stress_test, but I highly doubt we'll end up with another save_restore_pf_test, i.e. I don't think the clarification is needed.
Side topic, it probably makes sense to rename state_test to save_restore_state_test?
Quoted 15 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +12
-0@@ -0,0 +1,182 @@ +// SPDX-License-Identifier: GPL-2.0-only +#include <stdio.h> +#include <stdlib.h> +#include <string.h> +#include <errno.h> +#include <sys/types.h> +#include <time.h> +#include <unistd.h> + +#include "test_util.h" +#include "kvm_util.h" +#include "processor.h"
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 22
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+ +#define NR_ITERATIONS 500 + +#define GOTO_PREV_LINE "\033[A\r" +#define PRINT_ITER (s, x) \ +do { \ + if (x == 1) \ + printf(s "%d\n", x); \ + else \ + printf(GOTO_PREV_LINE s "%d\n", x); \
Oh c'mon. I had to Google the escape sequence you're (heh, "you"), using to understand this. Use a little creativity, and then the only magic escape sequence is the much more familiar carriage return.
pr_info("\rSave+restore iterations: %d", count);
}
pr_info("\n");tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 31
Quoted 9 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +9
-0+fflush (stdout); \ +} while (0) + +#define PTRS_PER_PTE 512 +#define PXD_INDEX (vaddr, level) (((vaddr) >> PG_LEVEL_SHIFT(level)) & (PTRS_PER_PTE - 1)) + +#define TEST_MEM_BASE_GVA 0xc0000000ULL +#define TEST_PGTABLE_GVA_OFFSET 0xd0000000ULL +#define NR_TEST_ADDRS PTRS_PER_PTE
IMO, this macro does waaaaay more harm than good. I'm looking at the usage and going "WTF is this is actually doing?". Knowing that the test is mucking with a page table's worth of PTEs is super useful information.
Quoted 6 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +6
-0+#define PATTERN 0xabcdefabcdefabcdULL + +static u64 pte_present_mask; +static u64 pte_huge_mask; + +static u64 expected_vaddr;
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 47
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+static u64 guest_faults; + +static u64 *guest_get_pte (u64 vaddr) +{ +u64 pgtable_pa, pte; +u64 *pgtable; +int level; +bool la57; + + la57 = !!(get_cr4 () &X86_CR4_LA57 );
Superfluous use of !!, and of the local bool itself. Just do
level = (get_cr4() & X86_CR4_LA57) ? PG_LEVEL_256T : PG_LEVEL_512G;
Quoted 4 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +4
-0+ level = la57 ?PG_LEVEL_256T :PG_LEVEL_512G ; + + pgtable_pa =get_cr3 () &PHYSICAL_PAGE_MASK ; +for (; level >PG_LEVEL_4K ; level--) {
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 61
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+ pgtable = (u64 *)(pgtable_pa +TEST_PGTABLE_GVA_OFFSET ); + pte = pgtable[PXD_INDEX (vaddr, level)]; +GUEST_ASSERT (pte & pte_present_mask); +GUEST_ASSERT (!(pte & pte_huge_mask)); + pgtable_pa =PTE_GET_PA (pte); + } + + pgtable = (u64 *)(pgtable_pa +TEST_PGTABLE_GVA_OFFSET ); +return &pgtable[PXD_INDEX (vaddr,PG_LEVEL_4K )]; +}
Hmm, I think we should put this helper in tools/testing/selftests/kvm/lib/x86/processor.c, and then provide a "struct kvm_mmu *guest_mmu;" that is automatically synchronized to the guest during kvm_arch_vm_post_create(). I think vm->mmu is fully populated at that point?
Then this test should be able to use the PTE macros from x86/processor.h, and future tests don't need to reinvent the wheel.
Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +5
-0+ +static void guest_pf_handler (struct ex_regs *regs) +{ +u64 fault_addr; +u64 *ptep;
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 76
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+ + fault_addr =get_cr2 (); +GUEST_ASSERT_EQ (fault_addr,READ_ONCE (expected_vaddr)); + + ptep =guest_get_pte (fault_addr); +GUEST_ASSERT (ptep); +GUEST_ASSERT (!(*ptep & pte_present_mask)); + + *ptep |= pte_present_mask; +invlpg (fault_addr);
invlpg() should be unnecessary. #PF is architecturally required to flush TLB entries for the faulting address. And since the PTEP is guaranteed to be !PRESENT, the CPU can't have speculatively added a new TLB entry after the fault.
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 86
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+ + guest_faults++; +} + +static void guest_access_memory (void *arg) +{ +u64 vaddr, val; +int i =0 ; + +for (;; i++) {
Dude.
for (i = 0; ; i++)
Quoted 26 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +26
-0+ vaddr =TEST_MEM_BASE_GVA + (i %NR_TEST_ADDRS ) *PAGE_SIZE ; +WRITE_ONCE (expected_vaddr, vaddr); + +/* Read to trigger #PF */ + val =READ_ONCE (*(u64 *)vaddr); +GUEST_ASSERT_EQ (val,PATTERN ); + +/* Clear the present bit again so it faults next time */ + *guest_get_pte (vaddr) &= ~pte_present_mask; +invlpg (vaddr); + +GUEST_SYNC (guest_faults); + } +} + +int main (int argc,char *argv[]) +{ +struct kvm_x86_state *state; +int r, i, level, count =0 ; +gpa_t gpa, pgtable_gpa; +struct kvm_vcpu *vcpu; +struct kvm_vm *vm; +struct ucall uc; +u64 *pgtable; +gva_t gva; +u64 pte;
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 122
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+ + vm =vm_create_with_one_vcpu (&vcpu, guest_access_memory); +vm_install_exception_handler (vm,PF_VECTOR , guest_pf_handler); + + pte_present_mask =PTE_PRESENT_MASK (&vm->mmu); + pte_huge_mask =PTE_HUGE_MASK (&vm->mmu); +sync_global_to_guest (vm, pte_present_mask); +sync_global_to_guest (vm, pte_huge_mask); + +/* Allocate a page and write the pattern to it */
Oh, is that was this code is doing? /s
I love comments. I hate useless comments.
Quoted 22 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +22
-0+ gva =vm_alloc_page (vm); + *(u64 *)addr_gva2hva (vm, gva) =PATTERN ; + gpa =addr_gva2gpa (vm, gva); + +/* +* Map all virtual addresses to the pattern page and clear the present +* bit such that guest accesses will cause a #PF. +*/ +for (i =0 ; i <NR_TEST_ADDRS ; i++) { + gva =TEST_MEM_BASE_GVA + i *getpagesize (); +virt_pg_map (vm, gva, gpa); + *vm_get_pte (vm, gva) &= ~pte_present_mask; + } + +/* +* Now create mappings for the page tables created above so that the +* guest #PF handler can walk them. All PTEs for test virtual addresses +* should lie on the same PTE page, so one page is mapped for each page +* table level. +* +* Use an offset for the GVA instead of creating identity mappings to +* avoid collision with existing mappings at low GVAs (e.g. ELF).
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 154
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+*/ + pgtable_gpa = vm->mmu.pgd; +for (level = vm->mmu.pgtable_levels; level >=PG_LEVEL_4K ; level--) { +virt_map (vm, pgtable_gpa +TEST_PGTABLE_GVA_OFFSET , pgtable_gpa,1 ); + pgtable =addr_gpa2hva (vm, pgtable_gpa); + pte = pgtable[PXD_INDEX (TEST_MEM_BASE_GVA , level)]; + pgtable_gpa =PTE_GET_PA (pte); + } + +while (count++ <NR_ITERATIONS ) {
Seriously.
for (i = 0; i < NR_ITERATIONS; i++)
I'm a-ok with people using AI to help with development, but I still absolutely expect the result to follow kernel style and generally not be the stupidest way to write code.
Re: [PATCH v3 07/10] KVM: selftests: Add basic stress test for save+restore and #PF handling
Quoted 35 lines · Sean Christopherson
Quoted 24 lines · Yosry Ahmed
Add a basic stress test for handling #PFs in a guest while the host is doing save+restore cycles. The guest periodically accesses non-present memory causing a #PF, and the #PF handler walks the page tables and updates the PTE to be present, like a proper #PF handler.
After every access (and #PF), the guest triggers a sync and the test performs save+restore of the VM. This is not very meaningful as save+restore are performed after the access and #PF handling complete, but following changes will change that.
Assisted-by Gemini:gemini-3.1-proSigned-off-by Yosry Ahmed <[email protected]>--- tools/testing/selftests/kvm/Makefile.kvm | 1 + .../selftests/kvm/include/x86/processor.h | 14 ++ .../kvm/x86/stress_save_restore_pf_test.c | 182 ++++++++++++++++++ 3 files changed, 197 insertions(+) create mode 100644 tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.ctools/testing/selftests/kvm/Makefile.kvm +0
-0tools/testing/selftests/kvm/Makefile.kvm TEST_GEN_PROGS_x86 += x86/set_sregs_test · line 114
Quoted 4 lines
tools/testing/selftests/kvm/Makefile.kvm +1
-0@@ -111,6 +111,7 @@ TEST_GEN_PROGS_x86 += x86/set_sregs_test TEST_GEN_PROGS_x86 += x86/smaller_maxphyaddr_emulation_test TEST_GEN_PROGS_x86 += x86/smm_test TEST_GEN_PROGS_x86 += x86/state_test +TEST_GEN_PROGS_x86 += x86/stress_save_restore_pf_testI'd rather go with just
save_restore_pf_test, so that the focus of the test is at the beginning of the file name. E.g. I don't want to end up with a pile ofstress_xyztests, because that makes tab completion a pain in the ass.
Quoted 2 lines
I'd also be ok with
save_restore_pf_stress_test, but I highly doubt we'll end up with anothersave_restore_pf_test, i.e. I don't think the clarification is needed.
I like having 'stress' in the name as I often find myself looking for stress tests. We also have other stress tests, so I think save_restore_pf_stress_test is good.
Quoted 2 lines
Side topic, it probably makes sense to rename
state_testtosave_restore_state_test?
*opens state_test.c*
*sees comments at the top saying "Tests for vCPU state save/restore"* *closes state_test.c*
Yes.
Quoted 21 lines
Quoted 21 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +17
-0@@ -0,0 +1,182 @@ +// SPDX-License-Identifier: GPL-2.0-only +#include <stdio.h> +#include <stdlib.h> +#include <string.h> +#include <errno.h> +#include <sys/types.h> +#include <time.h> +#include <unistd.h> + +#include "test_util.h" +#include "kvm_util.h" +#include "processor.h" + +#define NR_ITERATIONS 500 + +#define GOTO_PREV_LINE "\033[A\r" +#define PRINT_ITER (s, x) \
Quoted 8 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 22
Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +5
-0+do { \ + if (x == 1) \ + printf(s "%d\n", x); \ + else \ + printf(GOTO_PREV_LINE s "%d\n", x); \Oh c'mon. I had to Google the escape sequence you're (heh, "you"), using to understand this.
I named it GOTO_PREV_LINE specifically so that people don't have to Google it. AI wanted to call it something like ESC_SEQ, this is a big improvement :P
Quoted 7 lines
Use a little creativity, and then the only magic escape sequence is the much more familiar carriage return.
pr_info("\rSave+restore iterations: %d", count); } pr_info("\n");
I had something like this initially and I changed it, but I can't remember exactly why. I *think* when there is a test failure the log is messed up because we didn't print a line break after the last "Save+restore.." message.
Quoted 14 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 31
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +9
-0+fflush (stdout); \ +} while (0) + +#define PTRS_PER_PTE 512 +#define PXD_INDEX (vaddr, level) (((vaddr) >> PG_LEVEL_SHIFT(level)) & (PTRS_PER_PTE - 1)) + +#define TEST_MEM_BASE_GVA 0xc0000000ULL +#define TEST_PGTABLE_GVA_OFFSET 0xd0000000ULL +#define NR_TEST_ADDRS PTRS_PER_PTEIMO, this macro does waaaaay more harm than good. I'm looking at the usage and going "WTF is this is actually doing?". Knowing that the test is mucking with a page table's worth of PTEs is super useful information.
I initially thought that using PTRS_PER_PTE in guest_access_memory() reads a bit weird, but looking at it now I agree.
Quoted 21 lines
Quoted 8 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +6
-0+#define PATTERN 0xabcdefabcdefabcdULL + +static u64 pte_present_mask; +static u64 pte_huge_mask; + +static u64 expected_vaddr;tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 47
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+static u64 guest_faults; + +static u64 *guest_get_pte (u64 vaddr) +{ +u64 pgtable_pa, pte; +u64 *pgtable; +int level; +bool la57; + + la57 = !!(get_cr4 () &X86_CR4_LA57 );Superfluous use of !!, and of the local bool itself. Just do
Quoted 1 line
level = (get_cr4() & X86_CR4_LA57) ? PG_LEVEL_256T : PG_LEVEL_512G;
Ack.
Quoted 12 lines
Quoted 12 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +11
-0+ level = la57 ?PG_LEVEL_256T :PG_LEVEL_512G ; + + pgtable_pa =get_cr3 () &PHYSICAL_PAGE_MASK ; +for (; level >PG_LEVEL_4K ; level--) { + pgtable = (u64 *)(pgtable_pa +TEST_PGTABLE_GVA_OFFSET ); + pte = pgtable[PXD_INDEX (vaddr, level)]; +GUEST_ASSERT (pte & pte_present_mask); +GUEST_ASSERT (!(pte & pte_huge_mask)); + pgtable_pa =PTE_GET_PA (pte); + } +
Quoted 8 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 61
Quoted 3 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +3
-0+ pgtable = (u64 *)(pgtable_pa +TEST_PGTABLE_GVA_OFFSET ); +return &pgtable[PXD_INDEX (vaddr,PG_LEVEL_4K )]; +}Hmm, I think we should put this helper in
tools/testing/selftests/kvm/lib/x86/processor.c, and then provide a "structkvm_mmu*guest_mmu;" that is automatically synchronized to the guest duringkvm_arch_vm_post_create(). I thinkvm->mmuis fully populated at that point?
Hmm yes, It is initialized in virt_pgd_alloc(), which is called in ____vm_alloc() on the first allocation, which I think will be in kvm_vm_elf_load(). We can probably add an assertion to make sure that holds true.
However, I think we can't really provide a full kvm_mmu. We can synchronize the PTE masks, which I assume is what you mean here, but then provide a 'pgd' which isn't really usable because guest PTEs created by virt_map() (and friends) are not automatically sync'd to the guest. I thought about doing that, but it isn't straightforward because we cannot use direct mappings (see
https://lore.kernel.org/all/CAO9r8zNqYA6CACeGTVLcyj4bJ2XPAzEXL+y9tLuCU5Y-F=D-WA@mail.gmail.com/).
Quoted 3 lines
Then this test should be able to use the PTE macros from
x86/processor.h, and future tests don't need to reinvent the wheel.
Maybe provide a kvm_mmu with pgd=NULL just a placeholder to use the PTE masks?
Quoted 12 lines
Quoted 12 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +11
-0+ +static void guest_pf_handler (struct ex_regs *regs) +{ +u64 fault_addr; +u64 *ptep; + + fault_addr =get_cr2 (); +GUEST_ASSERT_EQ (fault_addr,READ_ONCE (expected_vaddr)); + + ptep =guest_get_pte (fault_addr); +GUEST_ASSERT (ptep);
Quoted 8 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 76
Quoted 4 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +4
-0+GUEST_ASSERT (!(*ptep & pte_present_mask)); + + *ptep |= pte_present_mask; +invlpg (fault_addr);
invlpg()should be unnecessary. #PF is architecturally required to flush TLB entries for the faulting address. And since the PTEP is guaranteed to be !PRESENT, the CPU can't have speculatively added a new TLB entry after the fault.
Yes, good catch.
Quoted 92 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 86
Quoted 11 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+ + guest_faults++; +} + +static void guest_access_memory (void *arg) +{ +u64 vaddr, val; +int i =0 ; + +for (;; i++) {Dude.
for (i = 0; ; i++)Quoted 26 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +26
-0+ vaddr =TEST_MEM_BASE_GVA + (i %NR_TEST_ADDRS ) *PAGE_SIZE ; +WRITE_ONCE (expected_vaddr, vaddr); + +/* Read to trigger #PF */ + val =READ_ONCE (*(u64 *)vaddr); +GUEST_ASSERT_EQ (val,PATTERN ); + +/* Clear the present bit again so it faults next time */ + *guest_get_pte (vaddr) &= ~pte_present_mask; +invlpg (vaddr); + +GUEST_SYNC (guest_faults); + } +} + +int main (int argc,char *argv[]) +{ +struct kvm_x86_state *state; +int r, i, level, count =0 ; +gpa_t gpa, pgtable_gpa; +struct kvm_vcpu *vcpu; +struct kvm_vm *vm; +struct ucall uc; +u64 *pgtable; +gva_t gva; +u64 pte;tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 122
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+ + vm =vm_create_with_one_vcpu (&vcpu, guest_access_memory); +vm_install_exception_handler (vm,PF_VECTOR , guest_pf_handler); + + pte_present_mask =PTE_PRESENT_MASK (&vm->mmu); + pte_huge_mask =PTE_HUGE_MASK (&vm->mmu); +sync_global_to_guest (vm, pte_present_mask); +sync_global_to_guest (vm, pte_huge_mask); + +/* Allocate a page and write the pattern to it */ Oh, is that was this code is doing? /s
I love comments. I hate useless comments.
Quoted 22 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +22
-0+ gva =vm_alloc_page (vm); + *(u64 *)addr_gva2hva (vm, gva) =PATTERN ; + gpa =addr_gva2gpa (vm, gva); + +/* +* Map all virtual addresses to the pattern page and clear the present +* bit such that guest accesses will cause a #PF. +*/ +for (i =0 ; i <NR_TEST_ADDRS ; i++) { + gva =TEST_MEM_BASE_GVA + i *getpagesize (); +virt_pg_map (vm, gva, gpa); + *vm_get_pte (vm, gva) &= ~pte_present_mask; + } + +/* +* Now create mappings for the page tables created above so that the +* guest #PF handler can walk them. All PTEs for test virtual addresses +* should lie on the same PTE page, so one page is mapped for each page +* table level. +* +* Use an offset for the GVA instead of creating identity mappings to +* avoid collision with existing mappings at low GVAs (e.g. ELF). tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 154
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +10
-0+*/ + pgtable_gpa = vm->mmu.pgd; +for (level = vm->mmu.pgtable_levels; level >=PG_LEVEL_4K ; level--) { +virt_map (vm, pgtable_gpa +TEST_PGTABLE_GVA_OFFSET , pgtable_gpa,1 ); + pgtable =addr_gpa2hva (vm, pgtable_gpa); + pte = pgtable[PXD_INDEX (TEST_MEM_BASE_GVA , level)]; + pgtable_gpa =PTE_GET_PA (pte); + } + +while (count++ <NR_ITERATIONS ) {Seriously.
Quoted 5 lines
for (i = 0; i < NR_ITERATIONS; i++)I'm a-ok with people using AI to help with development, but I still absolutely expect the result to follow kernel style and generally not be the stupidest way to write code.
To be honest I focused on iterating on the juicy bits (e.g. page table walker) to make sure the code there is clean and readable, I probably missed the "simple" things like loops :)
Sean Christopherson
maintainerRe: [PATCH v3 07/10] KVM: selftests: Add basic stress test for save+restore and #PF handling
Quoted 38 lines · Yosry Ahmed
Quoted 20 lines · Sean Christopherson
Quoted 20 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +17
-0@@ -0,0 +1,182 @@ +// SPDX-License-Identifier: GPL-2.0-only +#include <stdio.h> +#include <stdlib.h> +#include <string.h> +#include <errno.h> +#include <sys/types.h> +#include <time.h> +#include <unistd.h> + +#include "test_util.h" +#include "kvm_util.h" +#include "processor.h" + +#define NR_ITERATIONS 500 + +#define GOTO_PREV_LINE "\033[A\r" +#define PRINT_ITER (s, x) \Quoted 8 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 22
Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +5
-0+do { \ + if (x == 1) \ + printf(s "%d\n", x); \ + else \ + printf(GOTO_PREV_LINE s "%d\n", x); \Oh c'mon. I had to Google the escape sequence you're (heh, "you"), using to understand this.
I named it
GOTO_PREV_LINEspecifically so that people don't have to Google it. AI wanted to call it something likeESC_SEQ, this is a big improvement :PQuoted 4 lines
Use a little creativity, and then the only magic escape sequence is the much more familiar carriage return.
Quoted 8 lines
Quoted 3 lines
pr_info("\rSave+restore iterations: %d", count); } pr_info("\n");I had something like this initially and I changed it, but I can't remember exactly why. I *think* when there is a test failure the log is messed up because we didn't print a line break after the last "Save+restore.." message.
Ah, if an assert fires before the loop terminates. Hrm. This feels like something that should be a generic utility, but using any helper like this would require extreme care (the caller needs to know that *nothing* got printed between iterations).
What if we simply add a newline before printing an assertion?
testing/selftests/kvm/lib/assert.c +1 -1
@@ -74,7 +74,7 @@ test_assert(bool exp, const char *exp_str,if (!(exp)) {va_start (ap, fmt); - fprintf(stderr, "==== Test Assertion Failure ====\n" + fprintf(stderr, "\n==== Test Assertion Failure ====\n" " %s:%u: %s\n" " pid=%d tid=%d errno=%d - %s\n", file, line, exp_str, getpid(), kvm_gettid(),
IMO, that's desirable even when there's a preceding newline, e.g. I find this ever so slightly easier to parse:
$ ./x86/stress_save_restore_pf_test Random seed: 0x65f90564 Save+restore iterations: 500
==== Test Assertion Failure ====
x86/stress_save_restore_pf_test.c:310: guest_faults == 0 pid=4077 tid=4077 errno=25 - Inappropriate ioctl for device
1 0x0000000000403de6: main at stress_save_restore_pf_test.c:310
2 0x00007f8ead829d8f: ?? ??:0
3 0x00007f8ead829e3f: ?? ??:0
4 0x0000000000403fd4: _start at ??:?No guest page faults triggered
versus:
$ ./x86/stress_save_restore_pf_test
Random seed: 0xbc3c1a3
Save+restore iterations: 500
==== Test Assertion Failure ====
x86/stress_save_restore_pf_test.c:310: guest_faults == 0
pid=6077 tid=6077 errno=25 - Inappropriate ioctl for device
1 0x0000000000403de6: main at stress_save_restore_pf_test.c:310
2 0x00007f4750829d8f: ?? ??:0
3 0x00007f4750829e3f: ?? ??:0
4 0x0000000000403fd4: _start at ??:?
No guest page faults triggeredQuoted 10 lines
Quoted 4 lines
Hmm, I think we should put this helper in
tools/testing/selftests/kvm/lib/x86/processor.c, and then provide a "structkvm_mmu*guest_mmu;" that is automatically synchronized to the guest duringkvm_arch_vm_post_create(). I thinkvm->mmuis fully populated at that point?Hmm yes, It is initialized in
virt_pgd_alloc(), which is called in____vm_alloc()on the first allocation, which I think will be inkvm_vm_elf_load(). We can probably add an assertion to make sure that holds true.
Quoted 6 lines
However, I think we can't really provide a full
kvm_mmu. We can synchronize the PTE masks, which I assume is what you mean here, but then provide a 'pgd' which isn't really usable because guest PTEs created byvirt_map()(and friends) are not automatically sync'd to the guest. I thought about doing that, but it isn't straightforward because we cannot use direct mappings (see
Nit, s/direct/identity. That's a fairly important distinction for this code.
Quoted 1 line
https://lore.kernel.org/all/CAO9r8zNqYA6CACeGTVLcyj4bJ2XPAzEXL+y9tLuCU5Y-F=D-WA@mail.gmail.com/).
Wait, what? Me confused. The PTEs themselves must be "sync'd" to the guest, otherwise installing a new mapping would be useless.
IIUC, the problem is that the guest isn't guaranteed to have valid *mappings* to its own PTEs, which is not the same as the actual PTEs being stale.
IMO, that's totally fine, we just need to document the caveats. The guest can get at its PGD via MOV CR3 anyways. I.e. all we'd be doing is loading the gun for the guest to make it easier to put a hole in its foot.
Quoted 4 lines
Quoted 2 lines
Then this test should be able to use the PTE macros from
x86/processor.h, and future tests don't need to reinvent the wheel.Maybe provide a
kvm_mmuwith pgd=NULL just a placeholder to use the PTE masks?
pgd is a GPA.
Oooh, and this test relies on the page tables being identity mapped. In that case, it's probably best to keep guest_get_pte() in this test until we can broadly guarantee gPTEs are reachable. But I still think it makes sense to sync the MMU to the guest.
Re: [PATCH v3 07/10] KVM: selftests: Add basic stress test for save+restore and #PF handling
Quoted 49 lines · Sean Christopherson
Quoted 38 lines · Yosry Ahmed
Quoted 20 lines · Sean Christopherson
Quoted 20 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +17
-0@@ -0,0 +1,182 @@ +// SPDX-License-Identifier: GPL-2.0-only +#include <stdio.h> +#include <stdlib.h> +#include <string.h> +#include <errno.h> +#include <sys/types.h> +#include <time.h> +#include <unistd.h> + +#include "test_util.h" +#include "kvm_util.h" +#include "processor.h" + +#define NR_ITERATIONS 500 + +#define GOTO_PREV_LINE "\033[A\r" +#define PRINT_ITER (s, x) \Quoted 8 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c line 22
Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c new file +5
-0+do { \ + if (x == 1) \ + printf(s "%d\n", x); \ + else \ + printf(GOTO_PREV_LINE s "%d\n", x); \Oh c'mon. I had to Google the escape sequence you're (heh, "you"), using to understand this.
I named it
GOTO_PREV_LINEspecifically so that people don't have to Google it. AI wanted to call it something likeESC_SEQ, this is a big improvement :PQuoted 4 lines
Use a little creativity, and then the only magic escape sequence is the much more familiar carriage return.
Quoted 8 lines
Quoted 3 lines
pr_info("\rSave+restore iterations: %d", count); } pr_info("\n");I had something like this initially and I changed it, but I can't remember exactly why. I *think* when there is a test failure the log is messed up because we didn't print a line break after the last "Save+restore.." message.
Quoted 6 lines
Ah, if an assert fires before the loop terminates. Hrm. This feels like something that should be a generic utility, but using any helper like this would require extreme care (the caller needs to know that *nothing* got printed between iterations).
What if we simply add a newline before printing an assertion?
I like that. I will add a separate patch to do this (which will help other tests using carriage returns), then just use a carriage return here. Although..
Quoted 16 lines
testing/selftests/kvm/lib/assert.c +1
-1@@ -74,7 +74,7 @@ test_assert(bool exp, const char *exp_str,if (!(exp)) {va_start (ap, fmt); - fprintf(stderr, "==== Test Assertion Failure ====\n" + fprintf(stderr, "\n==== Test Assertion Failure ====\n" " %s:%u: %s\n" " pid=%d tid=%d errno=%d - %s\n", file, line, exp_str, getpid(), kvm_gettid(),
Quoted 2 lines
IMO, that's desirable even when there's a preceding newline, e.g. I find this ever so slightly easier to parse:
..in this very specific case, you still won't get the extra newline because of the carriage return :P
Quoted 50 lines
$ ./x86/stress_save_restore_pf_test Random seed: 0x65f90564 Save+restore iterations: 500==== Test Assertion Failure ====
x86/stress_save_restore_pf_test.c:310:guest_faults== 0 pid=4077 tid=4077 errno=25 - Inappropriate ioctl for device1 0x0000000000403de6: main at stress_save_restore_pf_test.c:310 2 0x00007f8ead829d8f: ?? ??:0 3 0x00007f8ead829e3f: ?? ??:0 4 0x0000000000403fd4: _start at ??:?No guest page faults triggered
versus:
$ ./x86/stress_save_restore_pf_test Random seed: 0xbc3c1a3 Save+restore iterations: 500 ==== Test Assertion Failure ==== x86/stress_save_restore_pf_test.c:310: guest_faults == 0 pid=6077 tid=6077 errno=25 - Inappropriate ioctl for device 1 0x0000000000403de6: main at stress_save_restore_pf_test.c:310 2 0x00007f4750829d8f: ?? ??:0 3 0x00007f4750829e3f: ?? ??:0 4 0x0000000000403fd4: _start at ??:? No guest page faults triggeredQuoted 10 lines
Quoted 4 lines
Hmm, I think we should put this helper in
tools/testing/selftests/kvm/lib/x86/processor.c, and then provide a "structkvm_mmu*guest_mmu;" that is automatically synchronized to the guest duringkvm_arch_vm_post_create(). I thinkvm->mmuis fully populated at that point?Hmm yes, It is initialized in
virt_pgd_alloc(), which is called in____vm_alloc()on the first allocation, which I think will be inkvm_vm_elf_load(). We can probably add an assertion to make sure that holds true.Quoted 6 lines
However, I think we can't really provide a full
kvm_mmu. We can synchronize the PTE masks, which I assume is what you mean here, but then provide a 'pgd' which isn't really usable because guest PTEs created byvirt_map()(and friends) are not automatically sync'd to the guest. I thought about doing that, but it isn't straightforward because we cannot use direct mappings (seeNit, s/direct/identity. That's a fairly important distinction for this code.
Quoted 7 lines
Quoted 1 line
https://lore.kernel.org/all/CAO9r8zNqYA6CACeGTVLcyj4bJ2XPAzEXL+y9tLuCU5Y-F=D-WA@mail.gmail.com/).
Wait, what? Me confused. The PTEs themselves must be "sync'd" to the guest, otherwise installing a new mapping would be useless.
IIUC, the problem is that the guest isn't guaranteed to have valid *mappings* to its own PTEs, which is not the same as the actual PTEs being stale.
Yes, sorry, bad wording.
Quoted 3 lines
IMO, that's totally fine, we just need to document the caveats. The guest can get at its PGD via MOV CR3 anyways. I.e. all we'd be doing is loading the gun for the guest to make it easier to put a hole in its foot.
Right, which is why I think writing pgd=NULL (or pgd=0 because it's a GPA) makes it easier (I think) to see the gun?
Quoted 9 lines
Quoted 5 lines
Quoted 3 lines
Then this test should be able to use the PTE macros from
x86/processor.h, and future tests don't need to reinvent the wheel.Maybe provide a
kvm_mmuwith pgd=NULL just a placeholder to use the PTE masks?pgd is a GPA.
Oooh, and this test relies on the page tables being identity mapped.
They are actually *not* identity mapped, they couldn't (see above). They are mapped at a magic VA (i.e. TEST_PGTABLE_GVA_OFFSET).
Quoted 4 lines
In that
case, it's probably best to keepguest_get_pte()in this test until we can broadly guarantee gPTEs are reachable. But I still think it makes sense to sync the MMU to the guest.
We can make the PTEs GVA offset a parameter to guest_get_pte(), but I think that's not a good API. At least we shouldn't proactively expose it before we have other users. So yes, I think we should keep guest_get_pte() in the test, and just expose the placeholder MMU for the pte masks.
PATCH v3 8/10 KVM: selftests: Trigger save+restore randomly in the #PF stress test
In reply to Yosry AhmedInstead of an explicit GUEST_SYNC() after each access+#PF, run another thread that keeps sending SIGUSR to the vCPU thread, essentially triggering exits to userspace and save+restore on random points in guest execution. This makes the test a lot more meaningful as it opens the door to exercising race conditions between #PF handling in the guest and save+restore in the host.
The signals are ignored using SIG_IGN outside of __vcpu_run() to avoid interrupting other ioctls/sysctls performed by the test.
--- .../kvm/x86/stress_save_restore_pf_test.c | 59 ++++++++++++++++--- 1 file changed, 51 insertions(+), 8 deletions(-)
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +51 -8
@@ -5,6 +5,8 @@#include <errno.h> #include <sys/types.h> #include <time.h> +#include <pthread.h> +#include <signal.h> #include <unistd.h> #include "test_util.h"
@@ -94,15 +96,41 @@ static void guest_access_memory(void *arg)/* Clear the present bit again so it faults next time */ *guest_get_pte (vaddr) &= ~pte_present_mask;invlpg (vaddr); + } +} + +static void *sigusr_thread_fn (void *arg) +{ +pthread_t vcpu_thread = (pthread_t )arg; -GUEST_SYNC (guest_faults); +for (;;) { +pthread_testcancel (); +pthread_kill (vcpu_thread,SIGUSR1 ); +usleep (msecs_to_usecs (1 )); } +return NULL ; +} + +static void dummy_signal_handler (int signo) {} +static struct sigaction sa; + +static void vcpu_sigusr_listen (void ) +{ + sa.sa_handler = dummy_signal_handler; +sigaction (SIGUSR1 , &sa,NULL ); +} + +static void vcpu_sigusr_ignore (void ) +{ + sa.sa_handler =SIG_IGN ; +sigaction (SIGUSR1 , &sa,NULL ); }int main (int argc,char *argv[]) {struct kvm_x86_state *state;int r, i, level, count =0 ; +pthread_t sigusr_thread;gpa_t gpa, pgtable_gpa;struct kvm_vcpu *vcpu;struct kvm_vm *vm;
@@ -151,18 +179,30 @@ int main(int argc, char *argv[]) pgtable_gpa =PTE_GET_PA (pte); } +/* Initialize the thread sending SIGUSR and install the handler */ +vcpu_sigusr_ignore (); + r =pthread_create (&sigusr_thread,NULL , sigusr_thread_fn, + (void *)pthread_self ()); +TEST_ASSERT (!r,"pthread_create() failed: %d" , r); +while (count++ <NR_ITERATIONS ) { +/* +* Only handle SIGUSR while the vCPU is running, otherwise +* ignore it to avoid interrupting other ioctls/syscalls. +*/ +vcpu_sigusr_listen (); r =__vcpu_run (vcpu); -TEST_ASSERT (!r,"vcpu_run failed" ); -TEST_ASSERT_KVM_EXIT_REASON (vcpu,KVM_EXIT_IO ); - -get_ucall (vcpu, &uc); -if (uc.cmd ==UCALL_ABORT ) { +if (r ==-1 ) +TEST_ASSERT_EQ (errno,EINTR ); +vcpu_sigusr_ignore (); + +/* The guest only exits due to a signal or failed assertion */ +if (!r) { +TEST_ASSERT_KVM_EXIT_REASON (vcpu,KVM_EXIT_IO ); +TEST_ASSERT_EQ (get_ucall (vcpu, &uc),UCALL_ABORT );REPORT_GUEST_ASSERT (uc);break ; } -TEST_ASSERT_EQ (uc.cmd,UCALL_SYNC ); -TEST_ASSERT_EQ (uc.args[1 ], count); state =vcpu_save_state (vcpu);
@@ -175,8 +215,11 @@ int main(int argc, char *argv[]) }sync_global_from_guest (vm, guest_faults); +TEST_ASSERT (guest_faults >0 ,"No guest page faults triggered" );pr_info ("Guest page faults: %lu\n" , guest_faults); +pthread_cancel (sigusr_thread); +pthread_join (sigusr_thread,NULL );kvm_vm_free (vm);return 0 ; }
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
[email protected]
AI reviewRe: [PATCH v3 08/10] KVM: selftests: Trigger save+restore randomly in the #PF stress test
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Medium] The aggressive 1ms signal interval can starve the guest and cause the test to deterministically…
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The aggressive 1ms signal interval can starve the guest and cause the test to deterministically fail on slower or nested environments. --
commit 4750524a9d34a97e2957bdf96a22b57c5404cb65
Author: Yosry Ahmed <[email protected]>
KVM: selftests: Trigger save+restore randomly in the #PF stress test
This patch introduces a background thread in the page fault stress test that sends SIGUSR1 to the vCPU thread to trigger exits to userspace. This allows exercising race conditions between page fault handling in the guest and save/restore paths in the host.
Quoted 4 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +0
-0
[ ... ]
Quoted 12 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +11
-0@@ -94,15 +96,41 @@ static void guest_access_memory(void *arg) +static void *sigusr_thread_fn (void *arg) +{ +pthread_t vcpu_thread = (pthread_t )arg; + +for (;;) { +pthread_testcancel (); +pthread_kill (vcpu_thread,SIGUSR1 ); +usleep (msecs_to_usecs (1 )); + } +return NULL ; +}
[ ... ]
Quoted 6 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +4
-0@@ -151,18 +179,30 @@ int main(int argc, char *argv[])while (count++ <NR_ITERATIONS ) { +/* +* Only handle SIGUSR while the vCPU is running, otherwise +* ignore it to avoid interrupting other ioctls/syscalls. +*/
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 188
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +4
-5+vcpu_sigusr_listen (); r =__vcpu_run (vcpu); -TEST_ASSERT (!r,"vcpu_run failed" ); -TEST_ASSERT_KVM_EXIT_REASON (vcpu,KVM_EXIT_IO ); - -get_ucall (vcpu, &uc); -if (uc.cmd ==UCALL_ABORT ) { +if (r ==-1 ) +TEST_ASSERT_EQ (errno,EINTR ); +vcpu_sigusr_ignore ();
[Severity: Medium]
Can the aggressive 1ms signal interval from sigusr_thread_fn starve the guest and cause deterministic test failures in slower environments?
The first time __vcpu_run executes for a newly created VM, it performs expensive kernel-side initializations like setting up the shadow MMU. If this setup takes longer than 1ms (which is probable in nested or heavily loaded CI environments), the background thread will send SIGUSR1 before the guest actually executes.
When KVM detects the pending signal, it will abort the entry and return -EINTR. Because main catches -EINTR and immediately proceeds to save the unchanged state and recreate the VM for the next iteration, the test can get stuck in a cycle where the guest never makes forward progress.
After exhausting all iterations doing nothing but VM recreations, the test would then fail the guest_faults > 0 assertion at the end. Could we verify that the guest actually ran and made forward progress before destroying the VM, or perhaps increase the signal interval?
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=8
Re: [PATCH v3 08/10] KVM: selftests: Trigger save+restore randomly in the #PF stress test
Quoted 68 lines · On Mon, Jun 29, 2026 at 06:48:37PM +0000, [email protected] wrote:
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The aggressive 1ms signal interval can starve the guest and cause the test to deterministically fail on slower or nested environments. --commit
4750524a9d34a97e2957bdf96a22b57c5404cb65
Author: Yosry Ahmed <[email protected]>KVM: selftests: Trigger save+restore randomly in the #PF stress test
This patch introduces a background thread in the page fault stress test that sends SIGUSR1 to the vCPU thread to trigger exits to userspace. This allows exercising race conditions between page fault handling in the guest and save/restore paths in the host.
Quoted 4 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +0
-0[ ... ]
Quoted 12 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +11
-0@@ -94,15 +96,41 @@ static void guest_access_memory(void *arg) +static void *sigusr_thread_fn (void *arg) +{ +pthread_t vcpu_thread = (pthread_t )arg; + +for (;;) { +pthread_testcancel (); +pthread_kill (vcpu_thread,SIGUSR1 ); +usleep (msecs_to_usecs (1 )); + } +return NULL ; +}[ ... ]
Quoted 6 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +4
-0@@ -151,18 +179,30 @@ int main(int argc, char *argv[])while (count++ <NR_ITERATIONS ) { +/* +* Only handle SIGUSR while the vCPU is running, otherwise +* ignore it to avoid interrupting other ioctls/syscalls. +*/ tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 188
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +4
-5+vcpu_sigusr_listen (); r =__vcpu_run (vcpu); -TEST_ASSERT (!r,"vcpu_run failed" ); -TEST_ASSERT_KVM_EXIT_REASON (vcpu,KVM_EXIT_IO ); - -get_ucall (vcpu, &uc); -if (uc.cmd ==UCALL_ABORT ) { +if (r ==-1 ) +TEST_ASSERT_EQ (errno,EINTR ); +vcpu_sigusr_ignore ();[Severity: Medium]
Can the aggressive 1ms signal interval fromsigusr_thread_fnstarve the guest and cause deterministic test failures in slower environments?The first time
__vcpu_runexecutes for a newly created VM, it performs expensive kernel-side initializations like setting up the shadow MMU. If this setup takes longer than 1ms (which is probable in nested or heavily loaded CI environments), the background thread will send SIGUSR1 before the guest actually executes.When KVM detects the pending signal, it will abort the entry and return
-EINTR. Because main catches-EINTRand immediately proceeds to save the unchanged state and recreate the VM for the next iteration, the test can get stuck in a cycle where the guest never makes forward progress.
Quoted 4 lines
After exhausting all iterations doing nothing but VM recreations, the test would then fail the
guest_faults> 0 assertion at the end. Could we verify that the guest actually ran and made forward progress before destroying the VM, or perhaps increase the signal interval?
The signal interval was initially 100us and that did cause problems on slower kernels (with DEBUG options or ASAN). With 1 msec, we don't observe any problems internally with DEBUG or ASAN builds on a variety of platforms. So I think we are good with 1 msec.
Increasing the interval too much will probably make the test less effective, as the signal is less likely to hit in interesting race windows.
PATCH v3 9/10 KVM: selftests: Support running stress save+restore and #PF test in L2
In reply to Yosry AhmedExtend the stress test to allow running the access+#PF code in L2 instead of L1 by adding proper L1 guest code to bootstrap L2. The test runs in nested mode if a '-n' flag is added.
--- .../kvm/x86/stress_save_restore_pf_test.c | 68 ++++++++++++++++++- 1 file changed, 66 insertions(+), 2 deletions(-)
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +66 -2
@@ -8,10 +8,13 @@#include <pthread.h> #include <signal.h> #include <unistd.h> +#include <getopt.h> #include "test_util.h" #include "kvm_util.h" #include "processor.h" +#include "svm_util.h" +#include "vmx.h" #define NR_ITERATIONS 500
@@ -99,6 +102,36 @@ static void guest_access_memory(void *arg) } } +static void l1_svm_code (struct svm_test_data *svm) +{ +generic_svm_setup (svm, guest_access_memory); +run_guest (svm->vmcb, svm->vmcb_gpa); +GUEST_ASSERT (false); +} + +static void l1_vmx_code (struct vmx_pages *vmx) +{ +GUEST_ASSERT (prepare_for_vmx_operation (vmx)); +GUEST_ASSERT (load_vmcs (vmx)); +prepare_vmcs (vmx, guest_access_memory); + +/* Ignore any #PF */ +GUEST_ASSERT (!vmwrite (EXCEPTION_BITMAP ,BIT (PF_VECTOR ))); +GUEST_ASSERT (!vmwrite (PAGE_FAULT_ERROR_CODE_MASK ,0 )); +GUEST_ASSERT (!vmwrite (PAGE_FAULT_ERROR_CODE_MATCH ,-1 )); + +GUEST_ASSERT (!vmlaunch ()); +GUEST_ASSERT (false); +} + +static void l1_guest_code (void *test_data) +{ +if (this_cpu_has (X86_FEATURE_SVM )) +l1_svm_code (test_data); +else +l1_vmx_code (test_data); +} +static void *sigusr_thread_fn (void *arg) {pthread_t vcpu_thread = (pthread_t )arg;
@@ -126,6 +159,25 @@ static void vcpu_sigusr_ignore(void)sigaction (SIGUSR1 , &sa,NULL ); } +static bool parse_args_nested (int argc,char *argv[]) +{ +bool nested = false; +int opt; + +while ((opt =getopt (argc, argv,"n" )) !=-1 ) { +switch (opt) { +case 'n' : + nested = true; +break ; +default : +printf ("Usage: %s [-n]\n" , argv[0 ]); +exit (1 ); + } + } + +return nested; +} +int main (int argc,char *argv[]) {struct kvm_x86_state *state;
@@ -136,12 +188,24 @@ int main(int argc, char *argv[])struct kvm_vm *vm;struct ucall uc;u64 *pgtable; +bool nested;gva_t gva;u64 pte; - vm =vm_create_with_one_vcpu (&vcpu, guest_access_memory); + nested =parse_args_nested (argc, argv); + + vm =vm_create_with_one_vcpu (&vcpu, nested ? l1_guest_code : guest_access_memory);vm_install_exception_handler (vm,PF_VECTOR , guest_pf_handler); +if (nested) { +TEST_REQUIRE (kvm_cpu_has (X86_FEATURE_SVM ) ||kvm_cpu_has (X86_FEATURE_VMX )); +if (kvm_cpu_has (X86_FEATURE_SVM )) +vcpu_alloc_svm (vm, &gva); +else +vcpu_alloc_vmx (vm, &gva); +vcpu_args_set (vcpu,1 , gva); + } + pte_present_mask =PTE_PRESENT_MASK (&vm->mmu); pte_huge_mask =PTE_HUGE_MASK (&vm->mmu);sync_global_to_guest (vm, pte_present_mask);
@@ -216,7 +280,7 @@ int main(int argc, char *argv[])sync_global_from_guest (vm, guest_faults);TEST_ASSERT (guest_faults >0 ,"No guest page faults triggered" ); -pr_info ("Guest page faults: %lu\n" , guest_faults); +pr_info ("Guest page faults%s: %lu\n" , nested ?" (in L2)" :"" , guest_faults);pthread_cancel (sigusr_thread);pthread_join (sigusr_thread,NULL );
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
Sean Christopherson
maintainerRe: [PATCH v3 09/10] KVM: selftests: Support running stress save+restore and #PF test in L2
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c static void vcpu_sigusr_ignore(void) · line 167
Quoted 6 lines · Yosry Ahmed
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +6
-0+static bool parse_args_nested (int argc,char *argv[]) +{ +bool nested = false; +int opt; + +while ((opt =getopt (argc, argv,"n" )) !=-1 ) {
Since the test ends up taking args anyways, might as well have it take the number of iterations too.
But, why make it an either-or? If nested is supported, run the test non-nested and then run it nested. While I am sloooooowly working towards utilizing Vipin's selftest runner, IMO this is still basic functionality that should be tested by default, i.e. shouldn't require fancy opt-in.
Quoted 54 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +27
-2+switch (opt) { +case 'n' : + nested = true; +break ; +default : +printf ("Usage: %s [-n]\n" , argv[0 ]); +exit (1 ); + } + } + +return nested; +} +int main (int argc,char *argv[]) {struct kvm_x86_state *state;@@ -136,12 +188,24 @@ int main(int argc, char *argv[])struct kvm_vm *vm;struct ucall uc;u64 *pgtable; +bool nested;gva_t gva;u64 pte; - vm =vm_create_with_one_vcpu (&vcpu, guest_access_memory); + nested =parse_args_nested (argc, argv); + + vm =vm_create_with_one_vcpu (&vcpu, nested ? l1_guest_code : guest_access_memory);vm_install_exception_handler (vm,PF_VECTOR , guest_pf_handler); +if (nested) { +TEST_REQUIRE (kvm_cpu_has (X86_FEATURE_SVM ) ||kvm_cpu_has (X86_FEATURE_VMX )); +if (kvm_cpu_has (X86_FEATURE_SVM )) +vcpu_alloc_svm (vm, &gva); +else +vcpu_alloc_vmx (vm, &gva); +vcpu_args_set (vcpu,1 , gva); + } + pte_present_mask =PTE_PRESENT_MASK (&vm->mmu); pte_huge_mask =PTE_HUGE_MASK (&vm->mmu);sync_global_to_guest (vm, pte_present_mask);@@ -216,7 +280,7 @@ int main(int argc, char *argv[])sync_global_from_guest (vm, guest_faults);TEST_ASSERT (guest_faults >0 ,"No guest page faults triggered" ); -pr_info ("Guest page faults: %lu\n" , guest_faults); +pr_info ("Guest page faults%s: %lu\n" , nested ?" (in L2)" :"" , guest_faults);pthread_cancel (sigusr_thread);pthread_join (sigusr_thread,NULL );Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
Re: [PATCH v3 09/10] KVM: selftests: Support running stress save+restore and #PF test in L2
Quoted 12 lines · Sean Christopherson
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c static void vcpu_sigusr_ignore(void) · line 167
Quoted 6 lines · Yosry Ahmed
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +6
-0+static bool parse_args_nested (int argc,char *argv[]) +{ +bool nested = false; +int opt; + +while ((opt =getopt (argc, argv,"n" )) !=-1 ) {Since the test ends up taking args anyways, might as well have it take the number of iterations too.
Quoted 4 lines
But, why make it an either-or? If nested is supported, run the test non-nested and then run it nested. While I am sloooooowly working towards utilizing Vipin's selftest runner, IMO this is still basic functionality that should be tested by default, i.e. shouldn't require fancy opt-in.
Good point, I will refactor all the logic in main() into run_test(nested), then run the test by default for both nested and non-nested.
PATCH v3 10/10 KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test
In reply to Yosry AhmedExtend the testing coverage in L2 by injecting a #UD into the vCPU every other iteration during restore, and intercepting #UD from L1, essentially forcing an L2 -> L1 VM-Exit directly after save+restore.
With this change, the test reliably reproduces the CR2 bug fixed by commit 5c247d08bc81 ("KVM: nSVM: Use vcpu->arch.cr2 when updating vmcb12 on nested #VMEXIT") -- at least on Milan, Genoa, and Turin CPUs.
--- .../kvm/x86/stress_save_restore_pf_test.c | 47 +++++++++++++++++-- 1 file changed, 42 insertions(+), 5 deletions(-)
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +42 -5
@@ -105,8 +105,12 @@ static void guest_access_memory(void *arg)static void l1_svm_code (struct svm_test_data *svm) {generic_svm_setup (svm, guest_access_memory); -run_guest (svm->vmcb, svm->vmcb_gpa); -GUEST_ASSERT (false); + svm->vmcb->control.intercept_exceptions |=BIT (UD_VECTOR ); + +while (1 ) { +run_guest (svm->vmcb, svm->vmcb_gpa); +GUEST_ASSERT_EQ (svm->vmcb->control.exit_code, (SVM_EXIT_EXCP_BASE +UD_VECTOR )); + } }static void l1_vmx_code (struct vmx_pages *vmx)
@@ -115,13 +119,17 @@ static void l1_vmx_code(struct vmx_pages *vmx)GUEST_ASSERT (load_vmcs (vmx));prepare_vmcs (vmx, guest_access_memory); -/* Ignore any #PF */ -GUEST_ASSERT (!vmwrite (EXCEPTION_BITMAP ,BIT (PF_VECTOR ))); +/* Intercept UD, ignore any #PF */ +GUEST_ASSERT (!vmwrite (EXCEPTION_BITMAP ,BIT (UD_VECTOR ) |BIT (PF_VECTOR )));GUEST_ASSERT (!vmwrite (PAGE_FAULT_ERROR_CODE_MASK ,0 ));GUEST_ASSERT (!vmwrite (PAGE_FAULT_ERROR_CODE_MATCH ,-1 ));GUEST_ASSERT (!vmlaunch ()); -GUEST_ASSERT (false); +while (1 ) { +GUEST_ASSERT_EQ (vmreadz (VM_EXIT_REASON ),EXIT_REASON_EXCEPTION_NMI ); +GUEST_ASSERT_EQ (vmreadz (VM_EXIT_INTR_INFO ) &0xff ,UD_VECTOR ); +GUEST_ASSERT (!vmresume ()); + } }static void l1_guest_code (void *test_data)
@@ -159,6 +167,24 @@ static void vcpu_sigusr_ignore(void)sigaction (SIGUSR1 , &sa,NULL ); } +static bool vcpu_state_is_guest_mode (struct kvm_x86_state *state) +{ +return !!(state->nested.flags &KVM_STATE_NESTED_GUEST_MODE ); +} + +static void vcpu_state_inject_ud (struct kvm_x86_state *state) +{ +if (state->events.exception.pending || state->events.exception.injected) +return ; + + state->events.flags |=KVM_VCPUEVENT_VALID_PAYLOAD ; + state->events.exception.pending = true; + state->events.exception.injected = false; + state->events.exception.nr =UD_VECTOR ; + state->events.exception.has_error_code = false; + state->events.exception_has_payload = false; +} +static bool parse_args_nested (int argc,char *argv[]) {bool nested = false;
@@ -192,10 +218,13 @@ int main(int argc, char *argv[])gva_t gva;u64 pte; +TEST_REQUIRE (kvm_has_cap (KVM_CAP_EXCEPTION_PAYLOAD )); + nested =parse_args_nested (argc, argv); vm =vm_create_with_one_vcpu (&vcpu, nested ? l1_guest_code : guest_access_memory);vm_install_exception_handler (vm,PF_VECTOR , guest_pf_handler); +vm_enable_cap (vm,KVM_CAP_EXCEPTION_PAYLOAD ,-2ul );if (nested) {TEST_REQUIRE (kvm_cpu_has (X86_FEATURE_SVM ) ||kvm_cpu_has (X86_FEATURE_VMX ));
@@ -270,8 +299,16 @@ int main(int argc, char *argv[]) state =vcpu_save_state (vcpu); +/* +* If the vCPU is in guest mode, inject a #UD to trigger an +* L2->L1 VM-Exit every other iteration. +*/ +if (nested &&vcpu_state_is_guest_mode (state) && count %2 ==0 ) +vcpu_state_inject_ud (state); +kvm_vm_release (vm); vcpu =vm_recreate_with_one_vcpu (vm); +vm_enable_cap (vm,KVM_CAP_EXCEPTION_PAYLOAD ,-2ul );vcpu_load_state (vcpu, state);kvm_x86_state_cleanup (state);
Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
Sean Christopherson
maintainerRe: [PATCH v3 10/10] KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test
Quoted 3 lines · Yosry Ahmed
Extend the testing coverage in L2 by injecting a #UD into the vCPU every other iteration during restore, and intercepting #UD from L1, essentially forcing an L2 -> L1 VM-Exit directly after save+restore.
Assuming the #UD is a means to an end, make that the focus of the intro blurb. I read this changelog without looking at the shortlog, and was about to ask why injecting a #UD is interesting, and then I saw the comment. It'd be helpful to add a bit more context too, as it took me a few seconds to piece together that the goal is to force the exit while L0 has control, i.e. a more obvious hypercall from L2 wouldn't suffice.
Quoted 15 lines
With this change, the test reliably reproduces the CR2 bug fixed by commit
5c247d08bc81("KVM: nSVM: Usevcpu->arch.cr2when updating vmcb12 on nested #VMEXIT") -- at least on Milan, Genoa, and Turin CPUs.Assisted-by Gemini:gemini-3.1-proSigned-off-by Yosry Ahmed <[email protected]>--- .../kvm/x86/stress_save_restore_pf_test.c | 47 +++++++++++++++++-- 1 file changed, 42 insertions(+), 5 deletions(-)tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +0
-0
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c static void guest_access_memory(void *arg) · line 112
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +5
-2@@ -105,8 +105,12 @@ static void guest_access_memory(void *arg)static void l1_svm_code (struct svm_test_data *svm) {generic_svm_setup (svm, guest_access_memory); -run_guest (svm->vmcb, svm->vmcb_gpa); -GUEST_ASSERT (false); + svm->vmcb->control.intercept_exceptions |=BIT (UD_VECTOR ); + +while (1 ) { +run_guest (svm->vmcb, svm->vmcb_gpa); +GUEST_ASSERT_EQ (svm->vmcb->control.exit_code, (SVM_EXIT_EXCP_BASE +UD_VECTOR ));
Please wrap this one, it's so long that I find it genuinely difficult to parse.
GUEST_ASSERT_EQ(svm->vmcb->control.exit_code, (SVM_EXIT_EXCP_BASE + UD_VECTOR));
Quoted 51 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +26
-3+ } }static void l1_vmx_code (struct vmx_pages *vmx)@@ -115,13 +119,17 @@ static void l1_vmx_code(struct vmx_pages *vmx)GUEST_ASSERT (load_vmcs (vmx));prepare_vmcs (vmx, guest_access_memory); -/* Ignore any #PF */ -GUEST_ASSERT (!vmwrite (EXCEPTION_BITMAP ,BIT (PF_VECTOR ))); +/* Intercept UD, ignore any #PF */ +GUEST_ASSERT (!vmwrite (EXCEPTION_BITMAP ,BIT (UD_VECTOR ) |BIT (PF_VECTOR )));GUEST_ASSERT (!vmwrite (PAGE_FAULT_ERROR_CODE_MASK ,0 ));GUEST_ASSERT (!vmwrite (PAGE_FAULT_ERROR_CODE_MATCH ,-1 ));GUEST_ASSERT (!vmlaunch ()); -GUEST_ASSERT (false); +while (1 ) { +GUEST_ASSERT_EQ (vmreadz (VM_EXIT_REASON ),EXIT_REASON_EXCEPTION_NMI ); +GUEST_ASSERT_EQ (vmreadz (VM_EXIT_INTR_INFO ) &0xff ,UD_VECTOR ); +GUEST_ASSERT (!vmresume ()); + } }static void l1_guest_code (void *test_data)@@ -159,6 +167,24 @@ static void vcpu_sigusr_ignore(void)sigaction (SIGUSR1 , &sa,NULL ); } +static bool vcpu_state_is_guest_mode (struct kvm_x86_state *state) +{ +return !!(state->nested.flags &KVM_STATE_NESTED_GUEST_MODE ); +} + +static void vcpu_state_inject_ud (struct kvm_x86_state *state) +{ +if (state->events.exception.pending || state->events.exception.injected) +return ; + + state->events.flags |=KVM_VCPUEVENT_VALID_PAYLOAD ; + state->events.exception.pending = true; + state->events.exception.injected = false; + state->events.exception.nr =UD_VECTOR ; + state->events.exception.has_error_code = false; + state->events.exception_has_payload = false; +} +static bool parse_args_nested (int argc,char *argv[]) {bool nested = false;
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 221
Quoted 4 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +1
-0@@ -192,10 +218,13 @@ int main(int argc, char *argv[])gva_t gva;u64 pte; +TEST_REQUIRE (kvm_has_cap (KVM_CAP_EXCEPTION_PAYLOAD ));
But KVM_CAP_EXCEPTION_PAYLOAD _isn't_ required, it's an optional feature. Actually, this is ridiculous. The test is injecting a #UD, it doesn't have a payload. Bad AI, bad.
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 227
Quoted 6 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +2
-0+ nested =parse_args_nested (argc, argv); vm =vm_create_with_one_vcpu (&vcpu, nested ? l1_guest_code : guest_access_memory);vm_install_exception_handler (vm,PF_VECTOR , guest_pf_handler); +vm_enable_cap (vm,KVM_CAP_EXCEPTION_PAYLOAD ,-2ul );
-2ul?
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 306
Quoted 11 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +5
-0if (nested) {TEST_REQUIRE (kvm_cpu_has (X86_FEATURE_SVM ) ||kvm_cpu_has (X86_FEATURE_VMX ));@@ -270,8 +299,16 @@ int main(int argc, char *argv[]) state =vcpu_save_state (vcpu); +/* +* If the vCPU is in guest mode, inject a #UD to trigger an +* L2->L1 VM-Exit every other iteration. +*/ +if (nested &&vcpu_state_is_guest_mode (state) && count %2 ==0 )
Checking "nested" here is unnecessary.
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 307
Quoted 1 line
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +1
-0+vcpu_state_inject_ud (state);
Honestly, I'd rather open code this whole thing, because this doesn't actually inject a #UD. It _prepares_ state, but doesn't send that into KVM. E.g.
/*
* If the vCPU is in guest mode, inject a #UD to trigger an
* L2->L1 VM-Exit every other iteration, unless the vCPU has. Take care not to
* clobber any exceptions
*/
if ((i & 1) && (state.nested.flags & KVM_STATE_NESTED_GUEST_MODE) &&
!state.events.exception.pending && !state.events.exception.injected) {
state->events.exception.pending = true;
state->events.exception.injected = false;
state->events.exception.nr = UD_VECTOR;
state->events.exception.has_error_code = false;
} Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +2
-0+kvm_vm_release (vm); vcpu =vm_recreate_with_one_vcpu (vm); +vm_enable_cap (vm,KVM_CAP_EXCEPTION_PAYLOAD ,-2ul );vcpu_load_state (vcpu, state);kvm_x86_state_cleanup (state);Signature · 1 line
2.55.0.rc0.799.gd6f94ed593-goog
Re: [PATCH v3 10/10] KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test
Quoted 6 lines · Sean Christopherson
Quoted 3 lines · Yosry Ahmed
Extend the testing coverage in L2 by injecting a #UD into the vCPU every other iteration during restore, and intercepting #UD from L1, essentially forcing an L2 -> L1 VM-Exit directly after save+restore.
Quoted 6 lines
Assuming the #UD is a means to an end, make that the focus of the intro blurb. I read this changelog without looking at the shortlog, and was about to ask why injecting a #UD is interesting, and then I saw the comment. It'd be helpful to add a bit more context too, as it took me a few seconds to piece together that the goal is to force the exit while L0 has control, i.e. a more obvious hypercall from L2 wouldn't suffice.
Yes, #UD is the easiest way (I think) to force an exit to L1 without running L2 first. Will reword.
Quoted 29 lines
Quoted 16 lines
With this change, the test reliably reproduces the CR2 bug fixed by commit
5c247d08bc81("KVM: nSVM: Usevcpu->arch.cr2when updating vmcb12 on nested #VMEXIT") -- at least on Milan, Genoa, and Turin CPUs.Assisted-by Gemini:gemini-3.1-proSigned-off-by Yosry Ahmed <[email protected]>--- .../kvm/x86/stress_save_restore_pf_test.c | 47 +++++++++++++++++-- 1 file changed, 42 insertions(+), 5 deletions(-)tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +0
-0tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c static void guest_access_memory(void *arg) · line 112
Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +5
-2@@ -105,8 +105,12 @@ static void guest_access_memory(void *arg)static void l1_svm_code (struct svm_test_data *svm) {generic_svm_setup (svm, guest_access_memory); -run_guest (svm->vmcb, svm->vmcb_gpa); -GUEST_ASSERT (false); + svm->vmcb->control.intercept_exceptions |=BIT (UD_VECTOR ); + +while (1 ) { +run_guest (svm->vmcb, svm->vmcb_gpa); +GUEST_ASSERT_EQ (svm->vmcb->control.exit_code, (SVM_EXIT_EXCP_BASE +UD_VECTOR ));Please wrap this one, it's so long that I find it genuinely difficult to parse.
Quoted 2 lines
GUEST_ASSERT_EQ(svm->vmcb->control.exit_code,
(SVM_EXIT_EXCP_BASE + UD_VECTOR));Will do.
Quoted 30 lines
Quoted 30 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +18
-0static void l1_guest_code (void *test_data)@@ -159,6 +167,24 @@ static void vcpu_sigusr_ignore(void)sigaction (SIGUSR1 , &sa,NULL ); } +static bool vcpu_state_is_guest_mode (struct kvm_x86_state *state) +{ +return !!(state->nested.flags &KVM_STATE_NESTED_GUEST_MODE ); +} + +static void vcpu_state_inject_ud (struct kvm_x86_state *state) +{ +if (state->events.exception.pending || state->events.exception.injected) +return ; + + state->events.flags |=KVM_VCPUEVENT_VALID_PAYLOAD ; + state->events.exception.pending = true; + state->events.exception.injected = false; + state->events.exception.nr =UD_VECTOR ; + state->events.exception.has_error_code = false; + state->events.exception_has_payload = false; +} +static bool parse_args_nested (int argc,char *argv[]) {bool nested = false;@@ -192,10 +218,13 @@ int main(int argc, char *argv[])gva_t gva;u64 pte;
Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 221
Quoted 1 line
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +1
-0+TEST_REQUIRE (kvm_has_cap (KVM_CAP_EXCEPTION_PAYLOAD ));But
KVM_CAP_EXCEPTION_PAYLOAD_isn't_ required, it's an optional feature. Actually, this is ridiculous. The test is injecting a #UD, it doesn't have a payload. Bad AI, bad.
KVM_CAP_EXCEPTION_PAYLOAD is required to inject a *pending* exception, which is needed as KVM won't check for interception on already injected exceptions. I will add a comment.
Quoted 8 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 227
Quoted 6 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +2
-0+ nested =parse_args_nested (argc, argv); vm =vm_create_with_one_vcpu (&vcpu, nested ? l1_guest_code : guest_access_memory);vm_install_exception_handler (vm,PF_VECTOR , guest_pf_handler); +vm_enable_cap (vm,KVM_CAP_EXCEPTION_PAYLOAD ,-2ul );-2ul?
That was actually me, not the AI. Apparently the other selftests also write -2ul for some reason. I was too lazy to go change them and/or figure out why -2ul, it didn't make any sense to me. I chose the lazy option and just used the same thing here.
Someone named Sean Christopherson wrote the other two, maybe we can ask him? :P
Quoted 7 lines
Quoted 7 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +0
-0if (nested) {TEST_REQUIRE (kvm_cpu_has (X86_FEATURE_SVM ) ||kvm_cpu_has (X86_FEATURE_VMX ));@@ -270,8 +299,16 @@ int main(int argc, char *argv[]) state =vcpu_save_state (vcpu);
Quoted 7 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 306
Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +5
-0+/* +* If the vCPU is in guest mode, inject a #UD to trigger an +* L2->L1 VM-Exit every other iteration. +*/ +if (nested &&vcpu_state_is_guest_mode (state) && count %2 ==0 )Checking "nested" here is unnecessary.
It is, actually. Sashiko pointed out [1] that vcpu_state_is_guest_mode() will read uninitialized memory otherwise.
[1]https://sashiko.dev/#/patchset/20260518202514.2037078-1-yosry%40kernel.org?part=8
Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 307
Quoted 2 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +1
-0+vcpu_state_inject_ud (state);Honestly, I'd rather open code this whole thing, because this doesn't actually inject a #UD. It _prepares_ state, but doesn't send that into KVM. E.g.
It injects a #UD into the state. The function name and parameter should make it clear. I prefer the helper, but I won't die on this hill.
Quoted 24 lines
/* * If the vCPU is in guest mode, inject a #UD to trigger an * L2->L1 VM-Exit every other iteration, unless the vCPU has. Take care not to * clobber any exceptions */ if ((i & 1) && (state.nested.flags & KVM_STATE_NESTED_GUEST_MODE) && !state.events.exception.pending && !state.events.exception.injected) { state->events.exception.pending = true; state->events.exception.injected = false; state->events.exception.nr = UD_VECTOR; state->events.exception.has_error_code = false; }Quoted 10 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +2
-1+kvm_vm_release (vm); vcpu =vm_recreate_with_one_vcpu (vm); +vm_enable_cap (vm,KVM_CAP_EXCEPTION_PAYLOAD ,-2ul );vcpu_load_state (vcpu, state);kvm_x86_state_cleanup (state); --2.55.0.rc0.799.gd6f94ed593-goog
Sean Christopherson
maintainerRe: [PATCH v3 10/10] KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test
Quoted 14 lines · Yosry Ahmed
Quoted 7 lines · Sean Christopherson
Quoted 7 lines
static bool
parse_args_nested(int argc, char *argv[]){ bool nested = false;tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +0
-0@@ -192,10 +218,13 @@ int main(int argc, char *argv[])gva_t gva;u64 pte;Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 221
Quoted 1 line
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +1
-0+TEST_REQUIRE (kvm_has_cap (KVM_CAP_EXCEPTION_PAYLOAD ));But
KVM_CAP_EXCEPTION_PAYLOAD_isn't_ required, it's an optional feature. Actually, this is ridiculous. The test is injecting a #UD, it doesn't have a payload. Bad AI, bad.
Quoted 3 lines
KVM_CAP_EXCEPTION_PAYLOADis required to inject a *pending* exception, which is needed as KVM won't check for interception on already injected exceptions. I will add a comment.
Drop the TEST_REQUIRE(), and instead only inject the pending #UD if the CAP is supported.
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +2
-0+ nested =parse_args_nested (argc, argv); vm =vm_create_with_one_vcpu (&vcpu, nested ? l1_guest_code : guest_access_memory);vm_install_exception_handler (vm,PF_VECTOR , guest_pf_handler); +vm_enable_cap (vm,KVM_CAP_EXCEPTION_PAYLOAD ,-2ul );
Quoted 8 lines
Quoted 1 line
-2ul?
That was actually me, not the AI. Apparently the other selftests also write -2ul for some reason. I was too lazy to go change them and/or figure out why -2ul, it didn't make any sense to me. I chose the lazy option and just used the same thing here.
Someone named Sean Christopherson wrote the other two, maybe we can ask him? :P
Nah, that guy's an asshole, not worth your time.
Quoted 14 lines
Quoted 6 lines
Quoted 6 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +0
-0if (nested) {TEST_REQUIRE (kvm_cpu_has (X86_FEATURE_SVM ) ||kvm_cpu_has (X86_FEATURE_VMX ));@@ -270,8 +299,16 @@ int main(int argc, char *argv[]) state =vcpu_save_state (vcpu);Quoted 7 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 306
Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +5
-0+/* +* If the vCPU is in guest mode, inject a #UD to trigger an +* L2->L1 VM-Exit every other iteration. +*/ +if (nested &&vcpu_state_is_guest_mode (state) && count %2 ==0 )Checking "nested" here is unnecessary.
Quoted 4 lines
It is, actually. Sashiko pointed out [1] that
vcpu_state_is_guest_mode()will read uninitialized memory otherwise.[1]https://sashiko.dev/#/patchset/20260518202514.2037078-1-yosry%40kernel.org?part=8
Oof. That's subtle. At the risk of true evil, what if we did:
int inject_ud; /* * Big comment here, explaining both the CAP dependency and the need to * check for nested before querying guest state. */ inject_ud = nested && kvm_has_cap(KVM_CAP_EXCEPTION_PAYLOAD); ... if ((i & inject_ud) && kvm_x86_state_is_guest_mode(&state) kvm_x86_state_inject_ud(&state);
Quoted 8 lines
Quoted 4 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 307
Quoted 1 line
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +1
-0+vcpu_state_inject_ud (state);Honestly, I'd rather open code this whole thing, because this doesn't actually inject a #UD. It _prepares_ state, but doesn't send that into KVM. E.g.
It injects a #UD into the state. The function name and parameter should make it clear. I prefer the helper, but I won't die on this hill.
I'm ok with a helper, it's the "vcpu" part that I find misleading, because the "vcpu" namespace in selftest typically means "send this command into a vCPU ioctl".
kvm_x86_state_xxx() appears to be the standard namespace, let's go with that?
Re: [PATCH v3 10/10] KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test
Quoted 16 lines · Sean Christopherson
Quoted 14 lines · Yosry Ahmed
Quoted 12 lines · Sean Christopherson
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 221
Quoted 8 lines
static bool
parse_args_nested(int argc, char *argv[]){ bool nested = false;tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +1
-0@@ -192,10 +218,13 @@ int main(int argc, char *argv[])gva_t gva;u64 pte; +TEST_REQUIRE (kvm_has_cap (KVM_CAP_EXCEPTION_PAYLOAD ));But
KVM_CAP_EXCEPTION_PAYLOAD_isn't_ required, it's an optional feature. Actually, this is ridiculous. The test is injecting a #UD, it doesn't have a payload. Bad AI, bad.
Quoted 6 lines
Quoted 3 lines
KVM_CAP_EXCEPTION_PAYLOADis required to inject a *pending* exception, which is needed as KVM won't check for interception on already injected exceptions. I will add a comment.Drop the
TEST_REQUIRE(), and instead only inject the pending #UD if the CAP is supported.
I prefer to keep the TEST_REQUIRE() as I don't like the test coverage silently changing based on the available caps tbh. Does it matter in practice? IIUC it's only possible for KVM_CAP_EXCEPTION_PAYLOAD to not exist if the test is run on an older kernel, right?
Quoted 32 lines
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +2
-0+ nested =parse_args_nested (argc, argv); vm =vm_create_with_one_vcpu (&vcpu, nested ? l1_guest_code : guest_access_memory);vm_install_exception_handler (vm,PF_VECTOR , guest_pf_handler); +vm_enable_cap (vm,KVM_CAP_EXCEPTION_PAYLOAD ,-2ul );Quoted 8 lines
Quoted 1 line
-2ul?
That was actually me, not the AI. Apparently the other selftests also write -2ul for some reason. I was too lazy to go change them and/or figure out why -2ul, it didn't make any sense to me. I chose the lazy option and just used the same thing here.
Someone named Sean Christopherson wrote the other two, maybe we can ask him? :P
Nah, that guy's an asshole, not worth your time.
Quoted 14 lines
Quoted 13 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 306
Quoted 11 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +5
-0if (nested) {TEST_REQUIRE (kvm_cpu_has (X86_FEATURE_SVM ) ||kvm_cpu_has (X86_FEATURE_VMX ));@@ -270,8 +299,16 @@ int main(int argc, char *argv[]) state =vcpu_save_state (vcpu); +/* +* If the vCPU is in guest mode, inject a #UD to trigger an +* L2->L1 VM-Exit every other iteration. +*/ +if (nested &&vcpu_state_is_guest_mode (state) && count %2 ==0 )Checking "nested" here is unnecessary.
Quoted 6 lines
Quoted 4 lines
It is, actually. Sashiko pointed out [1] that
vcpu_state_is_guest_mode()will read uninitialized memory otherwise.[1]https://sashiko.dev/#/patchset/20260518202514.2037078-1-yosry%40kernel.org?part=8
Oof. That's subtle. At the risk of true evil, what if we did:
As I mentioned above, I prefer taking a dependency on KVM_CAP_EXCEPTION_PAYLOAD rather than varying coverage. At least for the nested case, I think I can move the TEST_REQUIRE() into the 'nested' case, but then it's probably better to leave it as an arg to allow for meaningfully running the test in L0.
Actually, what if we just skip the nested case completely if KVM_CAP_EXCEPTION_PAYLOAD isn't available?
Quoted 8 lines
int inject_ud;
/*
* Big comment here, explaining both the CAP dependency and the need to
* check for nested before querying guest state.
*/
inject_ud = nested && kvm_has_cap(KVM_CAP_EXCEPTION_PAYLOAD);Either way yeah I think we should document why checking 'nested' is needed.
Or.. what if we just check state->nested.size inside kvm_x86_state_is_guest_mode()? or explicitly clear state->nested in vcpu_save_state() if nested_size == 0?
Quoted 12 lines
... if ((i & inject_ud) && kvm_x86_state_is_guest_mode(&state) kvm_x86_state_inject_ud(&state);Quoted 5 lines
Quoted 4 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 307
Quoted 1 line
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +1
-0+vcpu_state_inject_ud (state);Honestly, I'd rather open code this whole thing, because this doesn't actually inject a #UD. It _prepares_ state, but doesn't send that into KVM. E.g.
Quoted 8 lines
Quoted 3 lines
It injects a #UD into the state. The function name and parameter should make it clear. I prefer the helper, but I won't die on this hill.
I'm ok with a helper, it's the "vcpu" part that I find misleading, because the "vcpu" namespace in selftest typically means "send this command into a vCPU ioctl".
kvm_x86_state_xxx()appears to be the standard namespace, let's go with that?
Sounds good.
Sean Christopherson
maintainerRe: [PATCH v3 10/10] KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test
Quoted 21 lines · Yosry Ahmed
Quoted 20 lines · Sean Christopherson
Quoted 17 lines · Yosry Ahmed
Quoted 7 lines · Sean Christopherson
Quoted 7 lines
static bool
parse_args_nested(int argc, char *argv[]){ bool nested = false;tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +0
-0@@ -192,10 +218,13 @@ int main(int argc, char *argv[])gva_t gva;u64 pte;Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 221
Quoted 1 line
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +1
-0+TEST_REQUIRE (kvm_has_cap (KVM_CAP_EXCEPTION_PAYLOAD ));But
KVM_CAP_EXCEPTION_PAYLOAD_isn't_ required, it's an optional feature. Actually, this is ridiculous. The test is injecting a #UD, it doesn't have a payload. Bad AI, bad.
KVM_CAP_EXCEPTION_PAYLOADis required to inject a *pending* exception, which is needed as KVM won't check for interception on already injected exceptions. I will add a comment.
Quoted 5 lines
Quoted 2 lines
Drop the
TEST_REQUIRE(), and instead only inject the pending #UD if the CAP is supported.I prefer to keep the
TEST_REQUIRE()as I don't like the test coverage silently changing based on the available caps tbh.
That ship already sailed by agreeing to make nested support conditional :-)
Quoted 2 lines
Does it matter in practice? IIUC it's only possible for
KVM_CAP_EXCEPTION_PAYLOADto not exist if the test is run on an older kernel, right?
Correct, but people do run upstream selftests on older kernels, myself included. We do effectively break/drop backwards compatibility if there's sufficient justification, e.g. KVM_SET_USER_MEMORY_REGION2 is required for tests that create memslots so that selftests doesn't have to carry fallback code, but I don't think this one-off test qualifies for exemption.
Quoted 37 lines
Quoted 37 lines
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +2
-0+ nested =parse_args_nested (argc, argv); vm =vm_create_with_one_vcpu (&vcpu, nested ? l1_guest_code : guest_access_memory);vm_install_exception_handler (vm,PF_VECTOR , guest_pf_handler); +vm_enable_cap (vm,KVM_CAP_EXCEPTION_PAYLOAD ,-2ul );Quoted 8 lines
Quoted 1 line
-2ul?
That was actually me, not the AI. Apparently the other selftests also write -2ul for some reason. I was too lazy to go change them and/or figure out why -2ul, it didn't make any sense to me. I chose the lazy option and just used the same thing here.
Someone named Sean Christopherson wrote the other two, maybe we can ask him? :P
Nah, that guy's an asshole, not worth your time.
Quoted 18 lines
Quoted 6 lines
Quoted 6 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +0
-0if (nested) {TEST_REQUIRE (kvm_cpu_has (X86_FEATURE_SVM ) ||kvm_cpu_has (X86_FEATURE_VMX ));@@ -270,8 +299,16 @@ int main(int argc, char *argv[]) state =vcpu_save_state (vcpu);Quoted 7 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c int main(int argc, char *argv[]) · line 306
Quoted 5 lines
tools/testing/selftests/kvm/x86/stress_save_restore_pf_test.c +5
-0+/* +* If the vCPU is in guest mode, inject a #UD to trigger an +* L2->L1 VM-Exit every other iteration. +*/ +if (nested &&vcpu_state_is_guest_mode (state) && count %2 ==0 )Checking "nested" here is unnecessary.
It is, actually. Sashiko pointed out [1] that
vcpu_state_is_guest_mode()will read uninitialized memory otherwise.[1]https://sashiko.dev/#/patchset/20260518202514.2037078-1-yosry%40kernel.org?part=8
Quoted 7 lines
Quoted 1 line
Oof. That's subtle. At the risk of true evil, what if we did:
As I mentioned above, I prefer taking a dependency on
KVM_CAP_EXCEPTION_PAYLOADrather than varying coverage. At least for the nested case, I think I can move theTEST_REQUIRE()into the 'nested' case, but then it's probably better to leave it as an arg to allow for meaningfully running the test in L0.
The problem is that TEST_REQUIRE() skips the whole test, regardless of when it's called. I.e. if you go that route, passes for the non-nested case will show up as skips. TEST_REQUIRE() really is intended to be used when something is a hard requirement.
Quoted 2 lines
Actually, what if we just skip the nested case completely if
KVM_CAP_EXCEPTION_PAYLOADisn't available?
Can you use KVM_NMI instead of KVM_SET_VCPU_EVENTS to effect the nested #VMEXIT? That ioctl is so ancient that I'm a-ok skipping any CAP check for it.
Quoted 8 lines
Quoted 7 lines
int inject_ud; /* * Big comment here, explaining both the CAP dependency and the need to * check for nested before querying guest state. */ inject_ud = nested && kvm_has_cap(KVM_CAP_EXCEPTION_PAYLOAD);
Quoted 5 lines
Either way yeah I think we should document why checking 'nested' is needed.
Or.. what if we just check
state->nested.sizeinsidekvm_x86_state_is_guest_mode()? or explicitly clearstate->nestedinvcpu_save_state()ifnested_size== 0?
I like both of those ideas. If you do the former, definitely make kvm_x86_state_is_guest_mode() a "public" API.
Re: [PATCH v3 10/10] KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test
Quoted 11 lines
Quoted 5 lines
As I mentioned above, I prefer taking a dependency on
KVM_CAP_EXCEPTION_PAYLOADrather than varying coverage. At least for the nested case, I think I can move theTEST_REQUIRE()into the 'nested' case, but then it's probably better to leave it as an arg to allow for meaningfully running the test in L0.The problem is that
TEST_REQUIRE()skips the whole test, regardless of when it's called. I.e. if you go that route, passes for the non-nested case will show up as skips.TEST_REQUIRE()really is intended to be used when something is a hard requirement.
Quoted 5 lines
Quoted 2 lines
Actually, what if we just skip the nested case completely if
KVM_CAP_EXCEPTION_PAYLOADisn't available?Can you use
KVM_NMIinstead ofKVM_SET_VCPU_EVENTSto effect the nested #VMEXIT? That ioctl is so ancient that I'm a-ok skipping any CAP check for it.
Hmm actually I just realized I missed a CAP check for KVM_CAP_NESTED_STATE here. I don't think it's worth looking into dropping KVM_CAP_EXCEPTION_PAYLOAD, because we will need a CAP check anyway, and both of these were introduced very close in time (4.19 and 4.20, both 8 years ago).
So I think the simplest thing to do here is just run the nested test cases if both CAPs are available and skip it otherwise. Practically, I doubt there will be a lot of people running upstream selftests on <4.20 kernels for this to actually matter.
Quoted 9 lines
Quoted 9 lines
Quoted 8 lines
int inject_ud; /* * Big comment here, explaining both the CAP dependency and the need to * check for nested before querying guest state. */ inject_ud = nested && kvm_has_cap(KVM_CAP_EXCEPTION_PAYLOAD);
Quoted 8 lines
Quoted 5 lines
Either way yeah I think we should document why checking 'nested' is needed.
Or.. what if we just check
state->nested.sizeinsidekvm_x86_state_is_guest_mode()? or explicitly clearstate->nestedinvcpu_save_state()ifnested_size== 0?I like both of those ideas. If you do the former, definitely make
kvm_x86_state_is_guest_mode()a "public" API.
Will do that.
Sean Christopherson
maintainerRe: [PATCH v3 10/10] KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test
Quoted 23 lines · Yosry Ahmed
Quoted 11 lines
Quoted 5 lines
As I mentioned above, I prefer taking a dependency on
KVM_CAP_EXCEPTION_PAYLOADrather than varying coverage. At least for the nested case, I think I can move theTEST_REQUIRE()into the 'nested' case, but then it's probably better to leave it as an arg to allow for meaningfully running the test in L0.The problem is that
TEST_REQUIRE()skips the whole test, regardless of when it's called. I.e. if you go that route, passes for the non-nested case will show up as skips.TEST_REQUIRE()really is intended to be used when something is a hard requirement.Quoted 5 lines
Quoted 2 lines
Actually, what if we just skip the nested case completely if
KVM_CAP_EXCEPTION_PAYLOADisn't available?Can you use
KVM_NMIinstead ofKVM_SET_VCPU_EVENTSto effect the nested #VMEXIT? That ioctl is so ancient that I'm a-ok skipping any CAP check for it.Hmm actually I just realized I missed a CAP check for
KVM_CAP_NESTED_STATEhere. I don't think it's worth looking into droppingKVM_CAP_EXCEPTION_PAYLOAD, because we will need a CAP check anyway, and both of these were introduced very close in time (4.19 and 4.20, both 8 years ago).
Quoted 4 lines
So I think the simplest thing to do here is just run the nested test cases if both CAPs are available and skip it otherwise. Practically, I doubt there will be a lot of people running upstream selftests on <4.20 kernels for this to actually matter.
Yeah, works for me.