On 4/5/23 20:03, Li, Xin3 wrote:
If the second exception does not cause a vmexit, it is handled as usual by the
processor (by checking if the two exceptions are benign, contributory or page
faults). The behavior is the same even if the first exception comes from VMX
event injection.
The case I was thinking is, both the first and the second exception don't cause
any VM exit, however the first exception triggered an EPT violation. Later
KVM injects the first exception and delivering of the first exception by the
CPU triggers the second exception, then the information about the first
KVM-injected exception is lost, and it can be re-generated once the second
exception is correctly handled.
That's not a problem, the behavior is the same as on bare metal
(depending on whether the two exceptions are benign/contributory/page
faults).
Paolo
