On Sun, Feb 13, 2011, Avi Kivity wrote about "Re: [PATCH 07/29] nVMX: Hold a
vmcs02 for each vmcs12":
> I like having everything in one file. One reason is that it's always
> been this way, so it's a long standing tradition. Another is that if we
> put nvmx in i
On 02/13/2011 03:04 PM, Nadav Har'El wrote:
Hi,
On Sun, Feb 06, 2011, Avi Kivity wrote about "Re: [PATCH 07/29] nVMX: Hold a vmcs02
for each vmcs12":
> Thanks, that looks much nicer.
Apropos of looking nicer, there's something I'd like to ask your opinion ab
Hi,
On Sun, Feb 06, 2011, Avi Kivity wrote about "Re: [PATCH 07/29] nVMX: Hold a
vmcs02 for each vmcs12":
> Thanks, that looks much nicer.
Apropos of looking nicer, there's something I'd like to ask your opinion about.
So far, the nested-VMX patches put all the new cod
On 02/03/2011 02:57 PM, Nadav Har'El wrote:
On Sun, Jan 30, 2011, Avi Kivity wrote about "Re: [PATCH 07/29] nVMX: Hold a vmcs02
for each vmcs12":
>..
> >+static int nested_create_current_vmcs(struct kvm_vcpu *vcpu)
> >+{
>...
> >+ if (v
On Sun, Jan 30, 2011, Avi Kivity wrote about "Re: [PATCH 07/29] nVMX: Hold a
vmcs02 for each vmcs12":
>..
> >+static int nested_create_current_vmcs(struct kvm_vcpu *vcpu)
> >+{
>...
> >+if (vmx->nested.vmcs02_num>= NESTED_MAX_VMCS)
> >+
On 01/31/2011 11:26 AM, Nadav Har'El wrote:
Hi,
On Sun, Jan 30, 2011, Avi Kivity wrote about "Re: [PATCH 07/29] nVMX: Hold a vmcs02
for each vmcs12":
> >+/*
> >+ * Allocate an L0 VMCS (vmcs02) for the current L1 VMCS (vmcs12), if one
> >+ * does not already
Hi,
On Sun, Jan 30, 2011, Avi Kivity wrote about "Re: [PATCH 07/29] nVMX: Hold a
vmcs02 for each vmcs12":
> >+/*
> >+ * Allocate an L0 VMCS (vmcs02) for the current L1 VMCS (vmcs12), if one
> >+ * does not already exist. The allocation is done in L0 memory, so t
On 01/27/2011 10:33 AM, Nadav Har'El wrote:
In this patch we add a list of L0 (hardware) VMCSs, which we'll use to hold a
hardware VMCS for each active vmcs12 (i.e., for each L2 guest).
We call each of these L0 VMCSs a "vmcs02", as it is the VMCS that L0 uses
to run its nested guest L2.
+/*
+
In this patch we add a list of L0 (hardware) VMCSs, which we'll use to hold a
hardware VMCS for each active vmcs12 (i.e., for each L2 guest).
We call each of these L0 VMCSs a "vmcs02", as it is the VMCS that L0 uses
to run its nested guest L2.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c
