From: Jim Mattson <jmattson@google.com>
To: Julian Stecklina <jsteckli@amazon.de>
Cc: kvm list <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
js@alien8.de, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] kvm, vmx: move CR2 context switch out of assembly path
Date: Thu, 25 Oct 2018 10:02:08 -0700 [thread overview]
Message-ID: <CALMp9eQ=+jEabpDqa-a7WP7LVfTjmpW1ymWrVYeSxH4O4XOmyA@mail.gmail.com> (raw)
In-Reply-To: <09986c98c9655f1542768ecfda644ac821e67a57.1540369608.git.jsteckli@amazon.de>
On Wed, Oct 24, 2018 at 1:28 AM, Julian Stecklina <jsteckli@amazon.de> wrote:
> The VM entry/exit path is a giant inline assembly statement. Simplify it
> by doing CR2 context switching in plain C. Move CR2 restore behind IBRS
> clearing, so we reduce the amount of code we execute with IBRS on.
>
> Signed-off-by: Julian Stecklina <jsteckli@amazon.de>
> Reviewed-by: Jan H. Schönherr <jschoenh@amazon.de>
> Reviewed-by: Konrad Jan Miller <kjm@amazon.de>
Reviewed-by: Jim Mattson <jmattson@google.com>
prev parent reply other threads:[~2018-10-25 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 8:28 [PATCH 1/4] kvm, vmx: move CR2 context switch out of assembly path Julian Stecklina
2018-10-24 8:28 ` [PATCH 2/4] kvm, vmx: move register clearing " Julian Stecklina
2018-10-25 16:55 ` Jim Mattson
2018-10-26 10:31 ` Stecklina, Julian
2018-10-26 15:46 ` Sean Christopherson
2018-10-26 16:30 ` Jim Mattson
2018-10-29 13:47 ` Stecklina, Julian
2018-10-24 8:28 ` [PATCH 3/4] kvm, vmx: fix __invvpid style Julian Stecklina
2018-10-24 8:28 ` [PATCH 4/4] kvm, vmx: remove manually coded vmx instructions Julian Stecklina
2018-10-24 17:44 ` Eric Northup
2018-10-26 10:46 ` Stecklina, Julian
2018-10-26 14:30 ` Sean Christopherson
2018-10-25 17:02 ` Jim Mattson [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='CALMp9eQ=+jEabpDqa-a7WP7LVfTjmpW1ymWrVYeSxH4O4XOmyA@mail.gmail.com' \
--to=jmattson@google.com \
--cc=js@alien8.de \
--cc=jsteckli@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).