From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] KVM fixes for Linux 5.6 final (or -rc8)
Date: Thu, 26 Mar 2020 16:03:11 -0400 [thread overview]
Message-ID: <20200326200311.28222-1-pbonzini@redhat.com> (raw)
Linus,
The following changes since commit 018cabb694e3923998fdc2908af5268f1d89f48f:
Merge branch 'kvm-null-pointer-fix' into kvm-master (2020-03-14 12:49:37 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to e1be9ac8e6014a9b0a216aebae7250f9863e9fc3:
KVM: X86: Narrow down the IPI fastpath to single target IPI (2020-03-26 05:44:21 -0400)
----------------------------------------------------------------
x86 bug fixes.
----------------------------------------------------------------
He Zhe (1):
KVM: LAPIC: Mark hrtimer for period or oneshot mode to expire in hard interrupt context
Nick Desaulniers (1):
KVM: VMX: don't allow memory operands for inline asm that modifies SP
Paolo Bonzini (2):
KVM: x86: remove bogus user-triggerable WARN_ON
KVM: SVM: document KVM_MEM_ENCRYPT_OP, let userspace detect if SEV is available
Tom Lendacky (1):
KVM: SVM: Issue WBINVD after deactivating an SEV guest
Wanpeng Li (2):
KVM: LAPIC: Also cancel preemption timer when disarm LAPIC timer
KVM: X86: Narrow down the IPI fastpath to single target IPI
Documentation/virt/kvm/amd-memory-encryption.rst | 25 ++++++++++++++++++++++++
arch/x86/kvm/lapic.c | 8 +++++++-
arch/x86/kvm/svm.c | 25 ++++++++++++++++--------
arch/x86/kvm/vmx/vmx.c | 2 +-
arch/x86/kvm/x86.c | 6 ++++--
5 files changed, 54 insertions(+), 12 deletions(-)
next reply other threads:[~2020-03-26 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 20:03 Paolo Bonzini [this message]
2020-03-26 22:55 ` [GIT PULL] KVM fixes for Linux 5.6 final (or -rc8) pr-tracker-bot
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=20200326200311.28222-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).