On Tue, May 17, 2011, Marcelo Tosatti wrote about "Re: [PATCH 08/31] nVMX: Fix local_vcpus_link handling": > > this is what I planned to do, until it dawned on me that I can't, because > > "cpu" > > isn't part of vmx (where the vmcs and launched sit in the standard KVM), but >... > vcpu->cpu remains there. There is a new ->cpu field on struct vmcs, just > as saved_vmcs has in the current patches, to note the cpu which the VMCS > was last loaded.
So we'll have two fields, vmx.vcpu.cpu and vmx.vmcs.cpu, which are supposed to always contain the same value. Are you fine with that? > As mentioned there is no need to set "vcpu->cpu = -1" in __vcpu_clear, > the IPI handler, that can be done in vcpu_clear. Right, this is true. -- Nadav Har'El | Tuesday, May 17 2011, 14 Iyyar 5771 n...@math.technion.ac.il |----------------------------------------- Phone +972-523-790466, ICQ 13349191 |"A mathematician is a device for turning http://nadav.harel.org.il |coffee into theorems" -- P. Erdos -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
