From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] More KVM fixes for Linux 6.1-rc4
Date: Sun, 6 Nov 2022 03:46:56 -0500 [thread overview]
Message-ID: <20221106084656.148797-1-pbonzini@redhat.com> (raw)
Linus,
The following changes since commit 8e5423e991e8cd0988d0c4a3f4ac4ca1af7d148a:
Merge tag 'parisc-for-6.1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux (2022-11-02 11:25:12 -0700)
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 f4298cac2bfcced49ab308756dc8fef684f3da81:
Merge tag 'kvmarm-fixes-6.1-3' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD (2022-11-06 03:30:49 -0500)
----------------------------------------------------------------
ARM:
* Fix the pKVM stage-1 walker erronously using the stage-2 accessor
* Correctly convert vcpu->kvm to a hyp pointer when generating
an exception in a nVHE+MTE configuration
* Check that KVM_CAP_DIRTY_LOG_* are valid before enabling them
* Fix SMPRI_EL1/TPIDR2_EL0 trapping on VHE
* Document the boot requirements for FGT when entering the kernel
at EL1
x86:
* Use SRCU to protect zap in __kvm_set_or_clear_apicv_inhibit()
* Make argument order consistent for kvcalloc()
* Userspace API fixes for DEBUGCTL and LBRs
----------------------------------------------------------------
Ben Gardon (1):
KVM: x86: Use SRCU to protect zap in __kvm_set_or_clear_apicv_inhibit()
Gavin Shan (1):
KVM: Check KVM_CAP_DIRTY_LOG_{RING, RING_ACQ_REL} prior to enabling them
Liao Chang (1):
KVM: x86: Fix a typo about the usage of kvcalloc()
Marc Zyngier (1):
KVM: arm64: Fix SMPRI_EL1/TPIDR2_EL0 trapping on VHE
Mark Brown (1):
arm64: booting: Document our requirements for fine grained traps with SME
Paolo Bonzini (2):
Merge branch 'kvm-master' into HEAD
Merge tag 'kvmarm-fixes-6.1-3' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD
Quentin Perret (1):
KVM: arm64: Use correct accessor to parse stage-1 PTEs
Ryan Roberts (1):
KVM: arm64: Fix bad dereference on MTE-enabled systems
Sean Christopherson (3):
KVM: VMX: Advertise PMU LBRs if and only if perf supports LBRs
KVM: VMX: Fold vmx_supported_debugctl() into vcpu_supported_debugctl()
KVM: VMX: Ignore guest CPUID for host userspace writes to DEBUGCTL
Documentation/arm64/booting.rst | 8 ++++++++
arch/arm64/kvm/hyp/exception.c | 3 ++-
arch/arm64/kvm/hyp/include/hyp/switch.h | 20 ++++++++++++++++++++
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 2 +-
arch/arm64/kvm/hyp/nvhe/switch.c | 26 --------------------------
arch/arm64/kvm/hyp/vhe/switch.c | 8 --------
arch/x86/kvm/cpuid.c | 2 +-
arch/x86/kvm/vmx/capabilities.h | 19 +++----------------
arch/x86/kvm/vmx/vmx.c | 18 +++++++++++-------
arch/x86/kvm/x86.c | 3 +++
virt/kvm/kvm_main.c | 3 +++
11 files changed, 52 insertions(+), 60 deletions(-)
next reply other threads:[~2022-11-06 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 8:46 Paolo Bonzini [this message]
2022-11-06 18:49 ` 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=20221106084656.148797-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®