From: Ingo Molnar <mingo@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
x86@kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"KarimAllah Ahmed" <karahmed@amazon.de>,
"David Woodhouse" <dwmw@amazon.co.uk>,
"Jim Mattson" <jmattson@google.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 0/2] x86/pti: KVM: fixes and optimizations for IBRS
Date: Fri, 23 Feb 2018 08:26:24 +0100 [thread overview]
Message-ID: <20180223072624.iy2n6wxo5g54s2x4@gmail.com> (raw)
In-Reply-To: <20180222154318.20361-1-pbonzini@redhat.com>
* Paolo Bonzini <pbonzini@redhat.com> wrote:
> Two tiny patches for the IBRS code. They should go in
> through the x86/pti tree and should apply to both 4.9 and 4.14 trees.
>
> Thanks,
>
> Paolo
>
> v1->v2: remove patch 2, the same bug has already been fixed
>
> Paolo Bonzini (3):
> KVM: x86: use native MSR ops for SPEC_CTRL
> KVM: VMX: mark RDMSR path as unlikely
>
> arch/x86/kvm/svm.c | 9 +++++----
> arch/x86/kvm/vmx.c | 9 +++++----
> 2 files changed, 10 insertions(+), 8 deletions(-)
Applied to tip:x86/pti, with minor tweaks to the titles/changelogs.
If all goes fine in testing I will send all pending tip:x86/pti changes to Linus
later today, so the KVM development tree should be able to pull in these changes
via upstream pretty soon.
Thanks,
Ingo
prev parent reply other threads:[~2018-02-23 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 15:43 Paolo Bonzini
2018-02-22 15:43 ` [PATCH v2 1/2] KVM: x86: use native MSR ops for SPEC_CTRL Paolo Bonzini
2018-02-23 8:26 ` [tip:x86/pti] KVM/x86: Remove indirect MSR op calls from SPEC_CTRL tip-bot for Paolo Bonzini
2018-02-22 15:43 ` [PATCH v2 2/2] KVM: VMX: mark RDMSR path as unlikely Paolo Bonzini
2018-02-23 8:26 ` [tip:x86/pti] KVM/VMX: Optimize vmx_vcpu_run() and svm_vcpu_run() by marking the RDMSR path as unlikely() tip-bot for Paolo Bonzini
2018-02-23 7:26 ` Ingo Molnar [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=20180223072624.iy2n6wxo5g54s2x4@gmail.com \
--to=mingo@kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=jmattson@google.com \
--cc=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®