From: Gleb Natapov <gleb@redhat.com>
To: Abel Gordon <ABELG@il.ibm.com>
Cc: dongxiao.xu@intel.com, jun.nakajima@intel.com,
kvm@vger.kernel.org, nadav@harel.org.il, owasserm@redhat.com
Subject: Re: [PATCH 09/10] KVM: nVMX: Synchronize VMCS12 content with the shadow vmcs
Date: Wed, 17 Apr 2013 18:39:01 +0300 [thread overview]
Message-ID: <20130417153901.GC8997@redhat.com> (raw)
In-Reply-To: <OF1038CA74.BB243ED9-ONC2257B50.0050FCF0-C2257B50.005261F1@il.ibm.com>
On Wed, Apr 17, 2013 at 05:59:50PM +0300, Abel Gordon wrote:
>
>
> Gleb Natapov <gleb@redhat.com> wrote on 17/04/2013 05:34:49 PM:
>
> > > @@ -5716,6 +5725,10 @@ static void nested_vmx_failValid(struct
> > > X86_EFLAGS_SF | X86_EFLAGS_OF))
> > > | X86_EFLAGS_ZF);
> > > get_vmcs12(vcpu)->vm_instruction_error = vm_instruction_error;
> > > + /*
> > > + * We don't need to force a shadow sync because
> > > + * VM_INSTRUCTION_ERROR is not shdowed
> > ---------------------------------------^ shadowed.
> > But lets just request sync. This is slow path anyway.
>
> Why then ?
Because we do not care how fast the error case is handled, so no point
breaking the rules for it.
> Note this will require to call copy_shadow_to_vmcs12
> because nested_vmx_failValid can be called while L0 handles a L1
> exit (for vmx instruction emulation) and the shadow vmcs could
> have been modified by L1 before the exit.
>
Right, not a big deal if this is the only case when it happens. When we
discussed accessors vs sync_shadow_vmcs flag approach I said that flag
will work only if no vmcs12 fields are changed not as part of vmexit or
vmwrite emulations. This one is such a field unfortunately. Hope it is
the only one.
--
Gleb.
next prev parent reply other threads:[~2013-04-17 15:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 11:50 [PATCH 0/10] KVM: nVMX: shadow VMCS support, v2 Abel Gordon
2013-04-17 11:51 ` [PATCH 01/10] KVM: nVMX: Shadow-vmcs control fields/bits Abel Gordon
2013-04-17 11:51 ` [PATCH 02/10] KVM: nVMX: Detect shadow-vmcs capability Abel Gordon
2013-04-17 13:51 ` Gleb Natapov
2013-04-17 14:33 ` Abel Gordon
2013-04-17 11:52 ` [PATCH 03/10] KVM: nVMX: Introduce vmread and vmwrite bitmaps Abel Gordon
2013-04-17 11:52 ` [PATCH 04/10] KVM: nVMX: Refactor handle_vmwrite Abel Gordon
2013-04-17 11:53 ` [PATCH 05/10] KVM: nVMX: Allocate shadow vmcs Abel Gordon
2013-04-17 14:10 ` Gleb Natapov
2013-04-17 14:41 ` Abel Gordon
2013-04-17 14:44 ` Gleb Natapov
2013-04-17 11:53 ` [PATCH 06/10] KVM: nVMX: Release " Abel Gordon
2013-04-17 11:54 ` [PATCH 07/10] KVM: nVMX: Copy processor-specific shadow-vmcs to VMCS12 Abel Gordon
2013-04-17 11:54 ` [PATCH 08/10] KVM: nVMX: Copy VMCS12 to processor-specific shadow vmcs Abel Gordon
2013-04-17 11:55 ` [PATCH 09/10] KVM: nVMX: Synchronize VMCS12 content with the " Abel Gordon
2013-04-17 14:34 ` Gleb Natapov
2013-04-17 14:59 ` Abel Gordon
2013-04-17 15:39 ` Gleb Natapov [this message]
2013-04-17 16:03 ` Abel Gordon
2013-04-17 21:59 ` Paolo Bonzini
2013-04-18 6:24 ` Abel Gordon
2013-04-18 6:54 ` Gleb Natapov
2013-04-18 6:59 ` Paolo Bonzini
2013-04-17 11:55 ` [PATCH 10/10] KVM: nVMX: Enable and disable shadow vmcs functionality Abel Gordon
2013-04-17 14:41 ` Gleb Natapov
2013-04-17 15:18 ` Abel Gordon
2013-04-17 15:20 ` Gleb Natapov
-- strict thread matches above, loose matches on Subject: below --
2013-04-17 17:05 [PATCH 0/10] KVM: nVMX: shadow VMCS support, v3 Abel Gordon
2013-04-17 17:09 ` [PATCH 09/10] KVM: nVMX: Synchronize VMCS12 content with the shadow vmcs Abel Gordon
2013-04-18 6:41 ` Gleb Natapov
2013-04-18 7:07 ` Abel Gordon
2013-04-18 7:10 ` Gleb Natapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130417153901.GC8997@redhat.com \
--to=gleb@redhat.com \
--cc=ABELG@il.ibm.com \
--cc=dongxiao.xu@intel.com \
--cc=jun.nakajima@intel.com \
--cc=kvm@vger.kernel.org \
--cc=nadav@harel.org.il \
--cc=owasserm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox