Avi Kivity <avi@xxxxxxxxxx> wrote on 06/09/2009 12:29:58: > From: > > Avi Kivity <avi@xxxxxxxxxx> > > To: > > Orit Wasserman/Haifa/IBM@IBMIL > > Cc: > > Abel Gordon/Haifa/IBM@IBMIL, aliguori@xxxxxxxxxx, Ben-Ami Yassour1/ > Haifa/IBM@IBMIL, kvm@xxxxxxxxxxxxxxx, mmday@xxxxxxxxxx, Muli Ben- > Yehuda/Haifa/IBM@IBMIL > > Date: > > 06/09/2009 12:30 > > Subject: > > Re: [PATCH 5/6] Nested VMX patch 5 implements vmlaunch and vmresume > > On 09/03/2009 05:53 PM, Orit Wasserman wrote: > >> > >> Need to auto-ack the interrupt if requested by the guest. > >> > > The is_interrupt means L1 has interrupts, kvm regular code will handle it. > > > > If the VM-Exit Controls bit 15 (Acknowledge interrupts on exit) is set, > when the nested guest exits you need to run kvm_cpu_get_interrupt() and > put the vector number in the VM-Exit interruption-information field. > kvm doesn't set this bit but I think Xen does. VMware doesn't set it either. We have to run L2 with the bit off even if the L1 hypervisor set it, and emulate the L2 exit to L1 hypervisor correctly. I will look at it. > > -- > error compiling committee.c: too many arguments to function > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
