> On Oct 4, 2020, at 12:19 AM, Qi, Yadong <yadong.qi@xxxxxxxxx> wrote: > >> -----Original Message----- >> From: Qi, Yadong <yadong.qi@xxxxxxxxx> >> Sent: Friday, September 25, 2020 3:36 PM >> To: kvm@xxxxxxxxxxxxxxx >> Cc: pbonzini@xxxxxxxxxx; Qi, Yadong <yadong.qi@xxxxxxxxx> >> Subject: [kvm-unit-tests PATCH] x86: vmx: Add test for SIPI signal processing >> >> From: Yadong Qi <yadong.qi@xxxxxxxxx> >> >> The test verifies the following functionality: >> A SIPI signal received when CPU is in VMX non-root mode: >> if ACTIVITY_STATE == WAIT_SIPI >> VMExit with (reason == 4) >> else >> SIPI signal is ignored >> >> The test cases depends on IA32_VMX_MISC:bit(8), if this bit is 1 then the test >> cases would be executed, otherwise the test cases would be skiped. >> >> Signed-off-by: Yadong Qi <yadong.qi@xxxxxxxxx> [ snip ] > > Hi, Paolo > > Any comments of this patch? > It is test case for https://patchwork.kernel.org/patch/11791499/ On my bare-metal machine, I get a #GP on the WRMSR that writes the EOI inside ipi() : Test suite: vmx_sipi_signal_test Unhandled exception 13 #GP at ip 0000000000417eba error_code=0000 rflags=00010002 cs=00000008 rax=0000000000000000 rcx=000000000000080b rdx=0000000000000000 rbx=0000000000000000 rbp=000000000053a238 rsi=0000000000000000 rdi=000000000000000b r8=000000000000000a r9=00000000000003f8 r10=000000000000000d r11=0000000000000000 r12=000000000040c7a5 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 cr0=0000000080000011 cr2=0000000000000000 cr3=000000000041f000 cr4=0000000000000020 cr8=0000000000000000 STACK: @417eba 417f36 417481 417383 I did not dig much deeper. Could it be that there is some confusion between xapic/x2apic ?
