From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] KVM fixes for Linux 4.16-rc4
Date: Fri, 2 Mar 2018 22:42:31 +0100 [thread overview]
Message-ID: <20180302214231.GB28948@flask> (raw)
Linus,
The following changes since commit d4858aaf6bd8a90e2dacc0dfec2077e334dcedbf:
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm (2018-02-26 09:28:35 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm tags/for-linus
for you to fetch changes up to b7e31be385584afe7f073130e8e570d53c95f7fe:
KVM: x86: fix vcpu initialization with userspace lapic (2018-03-01 22:32:45 +0100)
----------------------------------------------------------------
KVM fixes for v4.16-rc4
x86:
- fix NULL dereference when using userspace lapic
- optimize spectre v1 mitigations by allowing guests to use LFENCE
- make microcode revision configurable to prevent guests from
unnecessarily blacklisting spectre v2 mitigation features
----------------------------------------------------------------
Radim Krčmář (1):
KVM: x86: fix vcpu initialization with userspace lapic
Tom Lendacky (2):
KVM: x86: Add a framework for supporting MSR-based features
KVM: SVM: Add MSR-based feature support for serializing LFENCE
Wanpeng Li (2):
KVM: X86: Introduce kvm_get_msr_feature()
KVM: X86: Allow userspace to define the microcode version
Documentation/virtual/kvm/api.txt | 40 ++++++++++-----
arch/x86/include/asm/kvm_host.h | 3 ++
arch/x86/kvm/lapic.c | 10 ++--
arch/x86/kvm/svm.c | 44 ++++++++++++++--
arch/x86/kvm/vmx.c | 7 +++
arch/x86/kvm/x86.c | 102 +++++++++++++++++++++++++++++++++++---
include/uapi/linux/kvm.h | 2 +
7 files changed, 179 insertions(+), 29 deletions(-)
reply other threads:[~2018-03-02 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180302214231.GB28948@flask \
--to=rkrcmar@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=torvalds@linux-foundation.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