[lkml]   [2020]   [May]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 17/30] KVM: nSVM: synchronize VMCB controls updated by the processor on every vmexit
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 enter_svm_guest_mode():
>     svm->vmcb->control.int_vector = nested_vmcb->control.int_vector;
> If int_vector is used only to trigger a #VMEXIT after we have decided to
> inject a virtual interrupt, we probably don't the vector value from the
> nested vmcb.

KVM does not use int_vector, but other hypervisor sometimes trigger
virtual interrupts using int_ctl+int_vector instead of eventinj.
(Unlike KVM they don't intercept EXIT_VINTR). Hyper-V operates like that.


 \ /
  Last update: 2020-05-30 07:11    [W:0.067 / U:6.456 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site