From: Joel Schopp <joel.schopp@amd.com>
To: Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>, <kvm@vger.kernel.org>
Cc: David Kaplan <David.Kaplan@amd.com>,
David Kaplan <david.kaplan@amd.com>, <rkrcmar@redhat.com>,
Joerg Roedel <joro@8bytes.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
<linux-kernel@vger.kernel.org>, <--bcc=ssg.sos.patches@amd.com>,
Borislav Petkov <bp@alien8.de>
Subject: [PATCH] x86: svm: use kvm_fast_pio_in()
Date: Fri, 27 Feb 2015 18:01:34 -0600 [thread overview]
Message-ID: <20150228000134.11870.31357.stgit@joelvmguard2.amd.com> (raw)
From: David Kaplan <David.Kaplan@amd.com>
We can make the in instruction go faster the same way the out instruction is
already.
Signed-off-by: David Kaplan <David.Kaplan@amd.com>
[extracted from larger unlrelated patch, forward ported, tested]
Signed-off-by: Joel Schopp <joel.schopp@amd.com>
---
arch/x86/kvm/svm.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index d319e0c..f8c906b 100644
--- a/arch/x86/kvm/svm.c
+++ b/arch/x86/kvm/svm.c
@@ -1899,7 +1899,7 @@ static int io_interception(struct vcpu_svm *svm)
++svm->vcpu.stat.io_exits;
string = (io_info & SVM_IOIO_STR_MASK) != 0;
in = (io_info & SVM_IOIO_TYPE_MASK) != 0;
- if (string || in)
+ if (string)
return emulate_instruction(vcpu, 0) == EMULATE_DONE;
port = io_info >> 16;
@@ -1907,6 +1907,8 @@ static int io_interception(struct vcpu_svm *svm)
svm->next_rip = svm->vmcb->control.exit_info_2;
skip_emulated_instruction(&svm->vcpu);
+ if (in)
+ return kvm_fast_pio_in(vcpu, size, port);
return kvm_fast_pio_out(vcpu, size, port);
}
next reply other threads:[~2015-02-28 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 0:01 Joel Schopp [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-28 0:04 [PATCH] x86: svm: use kvm_fast_pio_in() Joel Schopp
2015-03-02 13:38 ` Radim Krčmář
2015-03-02 16:03 ` Joel Schopp
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=20150228000134.11870.31357.stgit@joelvmguard2.amd.com \
--to=joel.schopp@amd.com \
--cc=--bcc=ssg.sos.patches@amd.com \
--cc=David.Kaplan@amd.com \
--cc=bp@alien8.de \
--cc=gleb@kernel.org \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--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