From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, rkrcmar@redhat.com, kvm@vger.kernel.org
Subject: [GIT PULL] KVM patches for Linux 5.4-rc8
Date: Tue, 12 Nov 2019 22:10:36 +0100 [thread overview]
Message-ID: <1573593036-23271-1-git-send-email-pbonzini@redhat.com> (raw)
Linus,
The following changes since commit 31f4f5b495a62c9a8b15b1c3581acd5efeb9af8c:
Linux 5.4-rc7 (2019-11-10 16:17:15 -0800)
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 a78986aae9b2988f8493f9f65a587ee433e83bc3:
KVM: MMU: Do not treat ZONE_DEVICE pages as being reserved (2019-11-12 10:17:42 +0100)
----------------------------------------------------------------
Bugfixes: unwinding of KVM_CREATE_VM failure,
VT-d posted interrupts, DAX/ZONE_DEVICE,
module unload/reload.
----------------------------------------------------------------
I delayed sending this until today, because there is a conflict between
today's processor vulnerability mitigations and commit 8a44119a98be from
this pull request ("KVM: Fix NULL-ptr deref after kvm_create_vm fails"),
and I didn't want to mess up your processing of Thomas's pull request.
It's not a particularly hard conflict, but I'm including anyway a
resolution at the end of this email.
Paolo
Chenyi Qiang (1):
KVM: X86: Fix initialization of MSR lists
Joao Martins (3):
KVM: VMX: Consider PID.PIR to determine if vCPU has pending interrupts
KVM: VMX: Do not change PID.NDST when loading a blocked vCPU
KVM: VMX: Introduce pi_is_pir_empty() helper
Liran Alon (1):
KVM: VMX: Fix comment to specify PID.ON instead of PIR.ON
Paolo Bonzini (2):
KVM: Fix NULL-ptr deref after kvm_create_vm fails
KVM: fix placement of refcount initialization
Sean Christopherson (1):
KVM: MMU: Do not treat ZONE_DEVICE pages as being reserved
arch/x86/kvm/mmu.c | 8 +++----
arch/x86/kvm/vmx/vmx.c | 23 +++++++++++++++++---
arch/x86/kvm/vmx/vmx.h | 11 ++++++++++
arch/x86/kvm/x86.c | 56 ++++++++++++++++++++++--------------------------
include/linux/kvm_host.h | 1 +
virt/kvm/kvm_main.c | 48 +++++++++++++++++++++++++++++------------
6 files changed, 96 insertions(+), 51 deletions(-)
diff --cc virt/kvm/kvm_main.c
index 4aab3547a165,0dac149ead16..000000000000
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@@ -715,15 -713,6 +735,11 @@@
return kvm;
out_err:
+#if defined(CONFIG_MMU_NOTIFIER) && defined(KVM_ARCH_WANT_MMU_NOTIFIER)
+ if (kvm->mmu_notifier.ops)
+ mmu_notifier_unregister(&kvm->mmu_notifier, current->mm);
+#endif
+out_err_no_mmu_notifier:
- cleanup_srcu_struct(&kvm->irq_srcu);
- out_err_no_irq_srcu:
- cleanup_srcu_struct(&kvm->srcu);
- out_err_no_srcu:
hardware_disable_all();
out_err_no_disable:
kvm_arch_destroy_vm(kvm);
next reply other threads:[~2019-11-12 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 21:10 Paolo Bonzini [this message]
2019-11-12 21:26 ` [GIT PULL] KVM patches for Linux 5.4-rc8 Linus Torvalds
2019-11-12 21:33 ` Paolo Bonzini
2019-11-12 21:30 ` 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=1573593036-23271-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@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;
as well as URLs for NNTP newsgroup(s).