Hello,
Avi Kivity wrote:
We get a page fault immediately (next instruction) after returning fromAh... okay, that's tricky but IIRC faults like that can be
the guest when running with oprofile. The page fault address does not
match anything the instruction does, so presumably it is one of the
accesses the processor performs in order to service an NMI (ordinary
interrupts are masked; and the fact that it happens with oprofile
strengthens this assumption).
distinguished from regular ones via processor state, right?
Here is the code in question:Can you please post the full oops (including kernel debug messages
3ae7: 75 05 jne 3aee<vmx_vcpu_run+0x26a>^^^ fault, but not at (%rsp)
3ae9: 0f 01 c2 vmlaunch
3aec: eb 03 jmp 3af1<vmx_vcpu_run+0x26d>
3aee: 0f 01 c3 vmresume
3af1: 48 87 0c 24 xchg %rcx,(%rsp)
during boot) or give me a pointer to the original message?
Also, does
the faulting address coincide with any symbol?