From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: [PATCH v2 0/3] Minor vcpu->requests improvements
Date: Sun, 20 May 2012 16:49:25 +0300 [thread overview]
Message-ID: <1337521768-14182-1-git-send-email-avi@redhat.com> (raw)
Nothing spectacular, just regularization of the code.
v2:
fix endless loop in patch 3 where a reload would set a bit in
vcpu->requests and abort the entry
Avi Kivity (3):
KVM: Simplify KVM_REQ_EVENT/req_int_win handling
KVM: Optimize vcpu->requests slow path slightly
KVM: Move mmu reload out of line
arch/x86/kvm/mmu.c | 4 ++-
arch/x86/kvm/svm.c | 1 +
arch/x86/kvm/x86.c | 73 ++++++++++++++++++++++++++++------------------------
3 files changed, 43 insertions(+), 35 deletions(-)
--
1.7.10.1
next reply other threads:[~2012-05-20 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 13:49 Avi Kivity [this message]
2012-05-20 13:49 ` [PATCH v2 1/3] KVM: Simplify KVM_REQ_EVENT/req_int_win handling Avi Kivity
2012-05-20 13:49 ` [PATCH v2 2/3] KVM: Optimize vcpu->requests slow path slightly Avi Kivity
2012-05-30 20:03 ` Marcelo Tosatti
2012-05-31 9:27 ` Avi Kivity
2012-06-02 0:23 ` Marcelo Tosatti
2012-05-20 13:49 ` [PATCH v2 3/3] KVM: Move mmu reload out of line 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=1337521768-14182-1-git-send-email-avi@redhat.com \
--to=avi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox