From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] Final batch of KVM fixes for 5.18
Date: Sat, 21 May 2022 02:31:33 -0400 [thread overview]
Message-ID: <20220521063133.70137-1-pbonzini@redhat.com> (raw)
Linus,
The following changes since commit 053d2290c0307e3642e75e0185ddadf084dc36c1:
KVM: VMX: Exit to userspace if vCPU has injected exception and invalid state (2022-05-06 13:08:06 -0400)
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 9f46c187e2e680ecd9de7983e4d081c3391acc76:
KVM: x86/mmu: fix NULL pointer dereference on guest INVPCID (2022-05-20 13:49:52 -0400)
Sorry for the relatively large change so close to the release, but in
terms of lines added it's mostly selftests.
----------------------------------------------------------------
ARM:
* Correctly expose GICv3 support even if no irqchip is created
so that userspace doesn't observe it changing pointlessly
(fixing a regression with QEMU)
* Don't issue a hypercall to set the id-mapped vectors when
protected mode is enabled (fix for pKVM in combination with
CPUs affected by Spectre-v3a)
x86: Five oneliners, of which the most interesting two are:
* a NULL pointer dereference on INVPCID executed with
paging disabled, but only if KVM is using shadow paging
* an incorrect bsearch comparison function which could truncate
the result and apply PMU event filtering incorrectly. This one
comes with a selftests update too.
----------------------------------------------------------------
Aaron Lewis (3):
kvm: x86/pmu: Fix the compare function used by the pmu event filter
selftests: kvm/x86: Add the helper function create_pmu_event_filter
selftests: kvm/x86: Verify the pmu event filter matches the correct event
Marc Zyngier (1):
KVM: arm64: vgic-v3: Consistently populate ID_AA64PFR0_EL1.GIC
Paolo Bonzini (2):
Merge tag 'kvmarm-fixes-5.18-3' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD
KVM: x86/mmu: fix NULL pointer dereference on guest INVPCID
Quentin Perret (1):
KVM: arm64: Don't hypercall before EL2 init
Sean Christopherson (2):
KVM: x86/mmu: Update number of zapped pages even if page list is stable
KVM: Free new dirty bitmap if creating a new memslot fails
Wanpeng Li (1):
KVM: eventfd: Fix false positive RCU usage warning
Yury Norov (1):
KVM: x86: hyper-v: fix type of valid_bank_mask
arch/arm64/kvm/arm.c | 3 +-
arch/arm64/kvm/sys_regs.c | 3 +-
arch/x86/kvm/hyperv.c | 4 +--
arch/x86/kvm/mmu/mmu.c | 16 ++++++----
arch/x86/kvm/pmu.c | 7 ++--
.../selftests/kvm/x86_64/pmu_event_filter_test.c | 37 +++++++++++++++++++---
virt/kvm/eventfd.c | 3 +-
virt/kvm/kvm_main.c | 2 +-
8 files changed, 56 insertions(+), 19 deletions(-)
next reply other threads:[~2022-05-21 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 6:31 Paolo Bonzini [this message]
2022-05-21 6:39 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-05-21 6:31 Paolo Bonzini
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=20220521063133.70137-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
all inboxes | Powered by JetHome®