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.14-rc6
Date: Sun, 15 Aug 2021 02:56:17 -0400 [thread overview]
Message-ID: <20210815065617.3754533-1-pbonzini@redhat.com> (raw)
Linus,
The following changes since commit d5aaad6f83420efb8357ac8e11c868708b22d0a9:
KVM: x86/mmu: Fix per-cpu counter corruption on 32-bit builds (2021-08-05 03:33:56 -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 6e949ddb0a6337817330c897e29ca4177c646f02:
Merge branch 'kvm-tdpmmu-fixes' into kvm-master (2021-08-13 03:33:13 -0400)
----------------------------------------------------------------
ARM:
- Plug race between enabling MTE and creating vcpus
- Fix off-by-one bug when checking whether an address range is RAM
x86:
- Fixes for the new MMU, especially a memory leak on hosts with <39
physical address bits
- Remove bogus EFER.NX checks on 32-bit non-PAE hosts
- WAITPKG fix
----------------------------------------------------------------
David Brazdil (1):
KVM: arm64: Fix off-by-one in range_is_memory
Junaid Shahid (1):
kvm: vmx: Sync all matching EPTPs when injecting nested EPT fault
Paolo Bonzini (4):
KVM: x86: remove dead initialization
Merge branch 'kvm-vmx-secctl' into kvm-master
Merge tag 'kvmarm-fixes-5.14-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD
Merge branch 'kvm-tdpmmu-fixes' into kvm-master
Sean Christopherson (6):
KVM: VMX: Use current VMCS to query WAITPKG support for MSR emulation
KVM: x86: Allow guest to set EFER.NX=1 on non-PAE 32-bit kernels
KVM: nVMX: Use vmx_need_pf_intercept() when deciding if L0 wants a #PF
KVM: x86/mmu: Don't leak non-leaf SPTEs when zapping all SPTEs
KVM: x86/mmu: Don't step down in the TDP iterator when zapping all SPTEs
KVM: x86/mmu: Protect marking SPs unsync when using TDP MMU with spinlock
Steven Price (1):
KVM: arm64: Fix race when enabling KVM_ARM_CAP_MTE
Documentation/virt/kvm/locking.rst | 8 ++---
arch/arm64/kvm/arm.c | 12 +++++---
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 2 +-
arch/x86/include/asm/kvm_host.h | 7 +++++
arch/x86/kvm/cpuid.c | 28 +-----------------
arch/x86/kvm/hyperv.c | 2 +-
arch/x86/kvm/mmu/mmu.c | 28 ++++++++++++++++++
arch/x86/kvm/mmu/tdp_mmu.c | 35 +++++++++++++++-------
arch/x86/kvm/vmx/nested.c | 56 +++++++++++++++++++++++++++--------
arch/x86/kvm/vmx/vmx.h | 2 +-
10 files changed, 118 insertions(+), 62 deletions(-)
next reply other threads:[~2021-08-15 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 6:56 Paolo Bonzini [this message]
2021-08-15 17:00 ` [GIT PULL] KVM fixes for Linux 5.14-rc6 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=20210815065617.3754533-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 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.