Re: [PATCH v2] KVM: nVMX: Consult only the "basic" exit reason when routing nested exit

2020-06-09 Thread Paolo Bonzini
On 08/06/20 21:18, Sean Christopherson wrote: > Consult only the basic exit reason, i.e. bits 15:0 of vmcs.EXIT_REASON, > when determining whether a nested VM-Exit should be reflected into L1 or > handled by KVM in L0. > > For better or worse, the switch statements nested_vmx_l0_wants_exit() > and

Re: [PATCH v2] KVM: nVMX: Consult only the "basic" exit reason when routing nested exit

2020-06-08 Thread Oliver Upton
On Mon, Jun 8, 2020 at 12:19 PM Sean Christopherson wrote: > > Consult only the basic exit reason, i.e. bits 15:0 of vmcs.EXIT_REASON, > when determining whether a nested VM-Exit should be reflected into L1 or > handled by KVM in L0. > > For better or worse, the switch statements nested_vmx_l0_wan

[PATCH v2] KVM: nVMX: Consult only the "basic" exit reason when routing nested exit

2020-06-08 Thread Sean Christopherson
Consult only the basic exit reason, i.e. bits 15:0 of vmcs.EXIT_REASON, when determining whether a nested VM-Exit should be reflected into L1 or handled by KVM in L0. For better or worse, the switch statements nested_vmx_l0_wants_exit() and nested_vmx_l1_wants_exit() default to reflecting the VM-E