Re: [PATCH 17/30] KVM: nSVM: synchronize VMCB controls updated by the processor on every vmexit

2020-05-29 Thread Paolo Bonzini
On 30/05/20 04:06, Krish Sadhukhan wrote: >> >>   -    nested_vmcb->control.int_ctl   = vmcb->control.int_ctl; >> -    nested_vmcb->control.int_vector    = vmcb->control.int_vector; > > > While it's not related to this patch, I am wondering if we need the > following line in

Re: [PATCH 17/30] KVM: nSVM: synchronize VMCB controls updated by the processor on every vmexit

2020-05-29 Thread Krish Sadhukhan
On 5/29/20 8:39 AM, Paolo Bonzini wrote: The control state changes on every L2->L0 vmexit, and we will have to serialize it in the nested state. So keep it up to date in svm->nested.ctl and just copy them back to the nested VMCB in nested_svm_vmexit. Signed-off-by: Paolo Bonzini ---