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 6.7-rc5
Date: Sun, 10 Dec 2023 06:01:01 -0500 [thread overview]
Message-ID: <20231210110101.2435586-1-pbonzini@redhat.com> (raw)
Linus,
The following changes since commit 33cc938e65a98f1d29d0a18403dbbee050dcad9a:
Linux 6.7-rc4 (2023-12-03 18:52:56 +0900)
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 4cdf351d3630a640ab6a05721ef055b9df62277f:
KVM: SVM: Update EFER software model on CR0 trap for SEV-ES (2023-12-08 13:37:05 -0500)
----------------------------------------------------------------
Generic:
* Set .owner for various KVM file_operations so that files refcount the
KVM module until KVM is done executing _all_ code, including the last
few instructions of kvm_put_kvm(). And then revert the misguided
attempt to rely on "struct kvm" refcounts to pin KVM-the-module.
ARM:
* Do not redo the mapping of vLPIs, if they have already been mapped
s390:
* Do not leave bits behind in PTEs
* Properly catch page invalidations that affect the prefix of a nested
guest
x86:
* When checking if a _running_ vCPU is "in-kernel", i.e. running at CPL0,
get the CPL directly instead of relying on preempted_in_kernel (which
is valid if and only if the vCPU was preempted, i.e. NOT running).
* Fix a benign "return void" that was recently introduced.
Selftests:
* Makefile tweak for dependency generation
* -Wformat fix
----------------------------------------------------------------
Claudio Imbrenda (2):
KVM: s390: vsie: fix wrong VIR 37 when MSO is used
KVM: s390/mm: Properly reset no-dat
David Woodhouse (1):
KVM: selftests: add -MP to CFLAGS
Kunkun Jiang (1):
KVM: arm64: GICv4: Do not perform a map to a mapped vLPI
Like Xu (2):
KVM: x86: Get CPL directly when checking if loaded vCPU is in kernel mode
KVM: x86: Remove 'return void' expression for 'void function'
Paolo Bonzini (3):
Merge tag 'kvmarm-fixes-6.7-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into kvm-master
Merge tag 'kvm-s390-master-6.7-1' of https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into kvm-master
Merge tag 'kvm-x86-fixes-6.7-rcN' of https://github.com/kvm-x86/linux into kvm-master
Sean Christopherson (3):
KVM: Set file_operations.owner appropriately for all such structures
Revert "KVM: Prevent module exit until all VMs are freed"
KVM: SVM: Update EFER software model on CR0 trap for SEV-ES
angquan yu (1):
KVM: selftests: Actually print out magic token in NX hugepages skip message
arch/arm64/kvm/vgic/vgic-v4.c | 4 ++++
arch/s390/kvm/vsie.c | 4 ----
arch/s390/mm/pgtable.c | 2 +-
arch/x86/kvm/debugfs.c | 1 +
arch/x86/kvm/svm/svm.c | 8 +++++---
arch/x86/kvm/x86.c | 9 ++++++---
tools/testing/selftests/kvm/Makefile | 2 +-
.../testing/selftests/kvm/x86_64/nx_huge_pages_test.c | 2 +-
virt/kvm/kvm_main.c | 18 ++++++++----------
9 files changed, 27 insertions(+), 23 deletions(-)
next reply other threads:[~2023-12-10 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 11:01 Paolo Bonzini [this message]
2023-12-10 19:12 ` [GIT PULL] KVM fixes for Linux 6.7-rc5 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=20231210110101.2435586-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.