From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: bsd@redhat.com, rkrcmar@redhat.com
Subject: Re: [RFC PATCH 0/2] KVM: x86: guest exit microoptimization
Date: Fri, 1 Jul 2016 18:45:14 +0200 [thread overview]
Message-ID: <7399af63-a751-a2dd-d8a4-77aee0bf5996@redhat.com> (raw)
In-Reply-To: <1466065297-4644-1-git-send-email-pbonzini@redhat.com>
On 16/06/2016 10:21, Paolo Bonzini wrote:
> This saves about 20 clock cycles per vmexit by avoiding a
> local_irq_save/restore pair. The price is that nested VMX will break
> with KVM hosts < 3.16, because the "acknowledge interrupt on exit"
> feature becomes mandatory. What do you think?
I'm pushing these patches.
Paolo
prev parent reply other threads:[~2016-07-01 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 8:21 [RFC PATCH 0/2] KVM: x86: guest exit microoptimization Paolo Bonzini
2016-06-16 8:21 ` [RFC PATCH 1/2] KVM: x86: always use "acknowledge interrupt on exit" Paolo Bonzini
2016-06-16 21:53 ` Bandan Das
2016-06-16 8:21 ` [RFC PATCH 2/2] KVM: x86: use __kvm_guest_exit Paolo Bonzini
2016-06-16 16:43 ` David Matlack
2016-06-16 16:47 ` Paolo Bonzini
2016-06-16 17:03 ` David Matlack
2016-06-16 17:21 ` Paolo Bonzini
2016-06-16 22:01 ` Bandan Das
2016-06-17 5:20 ` Paolo Bonzini
2016-07-01 16:45 ` Paolo Bonzini [this message]
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=7399af63-a751-a2dd-d8a4-77aee0bf5996@redhat.com \
--to=pbonzini@redhat.com \
--cc=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@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;
as well as URLs for NNTP newsgroup(s).