From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, Gleb Natapov <gleb@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH 7/9] KVM: VMX: Refactor vmx_complete_atomic_exit()
Date: Mon, 21 Mar 2011 10:55:08 +0200 [thread overview]
Message-ID: <4D87126C.6090301@redhat.com> (raw)
In-Reply-To: <20110315214000.GA31424@amt.cnet>
On 03/15/2011 11:40 PM, Marcelo Tosatti wrote:
> On Tue, Mar 08, 2011 at 03:57:43PM +0200, Avi Kivity wrote:
> > Move the exit reason checks to the front of the function, for early
> > exit in the common case.
> >
>
> >
> > static void vmx_complete_atomic_exit(struct vcpu_vmx *vmx)
> > {
> > - u32 exit_intr_info = vmx->exit_intr_info;
> > + u32 exit_intr_info;
> > +
> > + if (!(vmx->exit_reason == EXIT_REASON_MCE_DURING_VMENTRY
> > + || vmx->exit_reason == EXIT_REASON_EXCEPTION_NMI))
> > + return;
> > +
> > + exit_intr_info = vmx->exit_intr_info;
>
> So you're saving a vmread on exception and mce_during_vmentry exits?
Well, the real goal is patch 8, which removes the unconditional read of
VM_EXIT_INTR_INFO. Right now we have 2 reads on exceptions and one on
other exits, we drop both by 1.
> Managing nmi_known_unmasked appears tricky... perhaps worthwhile to
> have it in a helper that sets the bit in interruptibility info +
> nmi_known_unmasked.
I'll look into it, likely as an add-on patch.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-03-21 8:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 13:57 [PATCH 0/9] Some vmx vmexit optimizations Avi Kivity
2011-03-08 13:57 ` [PATCH 1/9] KVM: Use kvm_get_rflags() and kvm_set_rflags() instead of the raw versions Avi Kivity
2011-03-08 13:57 ` [PATCH 2/9] KVM: VMX: Optimize vmx_get_rflags() Avi Kivity
2011-03-08 13:57 ` [PATCH 3/9] KVM: VMX: Optimize vmx_get_cpl() Avi Kivity
2011-03-08 13:57 ` [PATCH 4/9] KVM: VMX: Cache cpl Avi Kivity
2011-03-08 14:20 ` Gleb Natapov
2011-03-08 14:29 ` Avi Kivity
2011-03-08 14:38 ` Gleb Natapov
2011-03-08 13:57 ` [PATCH 5/9] KVM: VMX: Avoid vmx_recover_nmi_blocking() when unneeded Avi Kivity
2011-03-08 13:57 ` [PATCH 6/9] KVM: VMX: Qualify check for host NMI Avi Kivity
2011-03-08 13:57 ` [PATCH 7/9] KVM: VMX: Refactor vmx_complete_atomic_exit() Avi Kivity
2011-03-15 21:40 ` Marcelo Tosatti
2011-03-21 8:55 ` Avi Kivity [this message]
2011-03-08 13:57 ` [PATCH 8/9] KVM: VMX: Don't VMREAD VM_EXIT_INTR_INFO unconditionally Avi Kivity
2011-03-08 13:57 ` [PATCH 9/9] KVM: VMX: Use cached VM_EXIT_INTR_INFO in handle_exception Avi Kivity
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=4D87126C.6090301@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.