From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [PATCH 10/11] KVM: nVMX: Synchronize VMCS12 content with the shadow vmcs Date: Sun, 14 Apr 2013 13:00:10 +0300 Message-ID: <20130414100010.GI17919@redhat.com> References: <20130310224335.GA16549@fermat.math.technion.ac.il> <20130409131435.GX17919@redhat.com> <20130411065411.GO17919@redhat.com> <20130412103117.GC25219@redhat.com> <20130412104804.GD25219@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dongxiao.xu@intel.com, jun.nakajima@intel.com, kvm@vger.kernel.org, kvm-owner@vger.kernel.org, "Nadav Har'El" , owasserm@redhat.com To: Abel Gordon Return-path: Received: from mx1.redhat.com ([209.132.183.28]:53720 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750878Ab3DNKA3 (ORCPT ); Sun, 14 Apr 2013 06:00:29 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Sun, Apr 14, 2013 at 12:51:34PM +0300, Abel Gordon wrote: > > > Gleb Natapov wrote on 12/04/2013 01:48:04 PM: > > > On Fri, Apr 12, 2013 at 01:44:14PM +0300, Abel Gordon wrote: > > > > > > Ok, so then you prefer to add the inline functions to read/write to the > > > vmcs12 > > > fields, (to set the request bit if shadowed field changed) and you are > not > > > concerned > > > about any merge/rebase mess. I will work on this direction. > > > I'll first send an independent patch to introduce the accessors. Once > you > > > apply this patch, I'll continue and send you v2 patches for shadow > vmcs. > > > > > > Do you agree ? > > Yes. > > Looking again at the code it seems like we could avoid adding the > accessors. > We could just set a flag in nested_vmx_vmexit and > nested_vmx_entry_failure. Then, in vmx_vcpu_run we check/reset the flag and > call copy_vmcs12_to_shadow (if required). > > What do you think ? Good idea! With accessors we can do further optimization by copying only things that changed, but it will be premature optimization at this point. -- Gleb.