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 5.0-rc2
Date: Sat, 12 Jan 2019 13:30:38 +0100 [thread overview]
Message-ID: <20190112123031.GA2992@flask> (raw)
Linus,
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -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 826c1362e79abcd36f99092acd083b5a2d576676:
x86/kvm/nVMX: don't skip emulated instruction twice when vmptr address is not backed (2019-01-11 18:41:53 +0100)
----------------------------------------------------------------
KVM fixes for 5.0-rc2
Minor fixes for new code, corner cases, and documentation.
Patches are isolated and sufficiently described by the shortlog.
----------------------------------------------------------------
Christophe de Dinechin (1):
Documentation/virtual/kvm: Update URL for AMD SEV API specification
David Rientjes (1):
kvm: sev: Fail KVM_SEV_INIT if already initialized
Gustavo A. R. Silva (1):
KVM: x86: Fix bit shifting in update_intel_pt_cfg
Lan Tianyu (1):
KVM/VMX: Avoid return error when flush tlb successfully in the hv_remote_flush_tlb_with_range()
Tomas Bortoli (1):
KVM: validate userspace input in kvm_clear_dirty_log_protect()
Vitaly Kuznetsov (1):
x86/kvm/nVMX: don't skip emulated instruction twice when vmptr address is not backed
Documentation/virtual/kvm/amd-memory-encryption.rst | 2 +-
arch/x86/kvm/svm.c | 3 +++
arch/x86/kvm/vmx/nested.c | 3 +--
arch/x86/kvm/vmx/vmx.c | 4 ++--
virt/kvm/kvm_main.c | 9 +++++++--
5 files changed, 14 insertions(+), 7 deletions(-)
next reply other threads:[~2019-01-12 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 12:30 Radim Krčmář [this message]
2019-01-12 18:45 ` [GIT PULL] KVM fixes for Linux 5.0-rc2 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=20190112123031.GA2992@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.