From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: Joel Schopp <joel.schopp@amd.com>, Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, David Kaplan <David.Kaplan@amd.com>,
Joerg Roedel <joro@8bytes.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] x86: svm: make wbinvd faster
Date: Mon, 2 Mar 2015 14:59:25 +0100 [thread overview]
Message-ID: <20150302135925.GA26739@potion.brq.redhat.com> (raw)
In-Reply-To: <jpg4mq45dyn.fsf@redhat.com>
2015-03-01 21:29-0500, Bandan Das:
> Joel Schopp <joel.schopp@amd.com> writes:
>
> > From: David Kaplan <David.Kaplan@amd.com>
> > No need to re-decode WBINVD since we know what it is from the intercept.
> >
> > 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>
> > ---
> > diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> > +static int wbinvd_interception(struct vcpu_svm *svm)
> > +{
> > + kvm_emulate_wbinvd(&svm->vcpu);
> > + skip_emulated_instruction(&svm->vcpu);
> > + return 1;
> > +}
> > +
> > +
> Can't we merge this to kvm_emulate_wbinvd, and just call that function
> directly for both vmx and svm ?
kvm_emulate_wbinvd() lives in x86.c and skip_emulated_instruction() is
from svm.c/vmx.c: so we'd have to create a new x86 op and change the
emulator code as well ... it's probably better like this.
> > static int xsetbv_interception(struct vcpu_svm *svm)
> > {
> > u64 new_bv = kvm_read_edx_eax(&svm->vcpu);
> > @@ -3376,7 +3384,7 @@ static int (*const svm_exit_handlers[])(struct vcpu_svm *svm) = {
> > [SVM_EXIT_STGI] = stgi_interception,
> > [SVM_EXIT_CLGI] = clgi_interception,
> > [SVM_EXIT_SKINIT] = skinit_interception,
> > - [SVM_EXIT_WBINVD] = emulate_on_interception,
> So, this means x86_emulate_insn() in emulate.c has no callers left for the
> wbinvd case ? vmx calls kvm_emulate_wbinvd directly too..
I think that invalid state emulation might still hit wbinvd.
next prev parent reply other threads:[~2015-03-02 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 0:19 [PATCH] x86: svm: make wbinvd faster Joel Schopp
2015-03-02 2:29 ` Bandan Das
2015-03-02 13:59 ` Radim Krčmář [this message]
2015-03-02 15:25 ` Bandan Das
2015-03-02 16:03 ` Radim Krčmář
2015-03-02 16:58 ` Joel Schopp
2015-03-02 14:09 ` Radim Krčmář
2015-03-09 23:28 ` Marcelo Tosatti
2015-03-10 11:01 ` Radim Krčmář
2015-03-10 22:37 ` Marcelo Tosatti
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=20150302135925.GA26739@potion.brq.redhat.com \
--to=rkrcmar@redhat.com \
--cc=David.Kaplan@amd.com \
--cc=bp@alien8.de \
--cc=bsd@redhat.com \
--cc=gleb@kernel.org \
--cc=joel.schopp@amd.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@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