On 05/17/2011 10:52 PM, Marcelo Tosatti wrote:
On Tue, May 17, 2011 at 10:30:30PM +0300, Nadav Har'El wrote:
> 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?
Yes. Avi?
Yes.
They have different meanings. vcpu->cpu means where the task that runs
the vcpu is running (or last ran). vmcs->cpu means which cpu has the
vmcs cached. They need not be the same when we have multiple vmcs's for
a vcpu; but vmx->vmcs->cpu will chase vcpu->cpu as it changes.
Please post this patch separately instead of reposting the entire
series, we can apply it independently.
--
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
