Avi Kivity <[email protected]> wrote on 02/09/2009 22:38:22:
> From: > > Avi Kivity <[email protected]> > > To: > > Orit Wasserman/Haifa/i...@ibmil > > Cc: > > [email protected], Ben-Ami Yassour1/Haifa/i...@ibmil, Muli Ben- > Yehuda/Haifa/i...@ibmil, Abel Gordon/Haifa/i...@ibmil, > [email protected], [email protected] > > Date: > > 02/09/2009 23:01 > > Subject: > > Re: [PATCH 2/6] Nested VMX patch 2 implements vmclear > > On 09/02/2009 06:38 PM, [email protected] wrote: > > From: Orit Wasserman<[email protected]> > > > > --- > > arch/x86/kvm/vmx.c | 24 +++++++++++++++++++++++- > > 1 files changed, 23 insertions(+), 1 deletions(-) > > > > diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c > > index abba325..2b1fc3b 100644 > > --- a/arch/x86/kvm/vmx.c > > +++ b/arch/x86/kvm/vmx.c > > @@ -70,6 +70,8 @@ struct vmcs { > > struct nested_vmx { > > /* Has the level1 guest done vmon? */ > > bool vmon; > > + /* Has the level1 guest done vmclear? */ > > + bool vmclear; > > }; > > > > Doesn't seem these two belong in the same structure - vmclear is > per-vmcs... but you're probably aware of that with the multi-guest > support coming. You are right vmclear flag is part of the L2 guest state. > > > -- > I have a truly marvellous patch that fixes the bug which this > signature is too narrow to contain. > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
