From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: x86: Fixes for 6.7-rcN
Date: Thu, 7 Dec 2023 18:07:34 -0800 [thread overview]
Message-ID: <20231208020734.1705867-1-seanjc@google.com> (raw)
Please pull a handful of fixes for 6.7-rcN (hopefully N=5). These have all
been in -next for a week or so.
The following changes since commit ffc253263a1375a65fa6c9f62a893e9767fbebfa:
Linux 6.6 (2023-10-29 16:31:08 -1000)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-fixes-6.7-rcN
for you to fetch changes up to ef8d89033c3f1f6a64757f066b2c17e76d1189f8:
KVM: x86: Remove 'return void' expression for 'void function' (2023-12-01 08:14:27 -0800)
----------------------------------------------------------------
KVM fixes for 6.7-rcN:
- 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.
- 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.
- Fix a benign "return void" that was recently introduced.
----------------------------------------------------------------
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'
Sean Christopherson (2):
KVM: Set file_operations.owner appropriately for all such structures
Revert "KVM: Prevent module exit until all VMs are freed"
arch/x86/kvm/debugfs.c | 1 +
arch/x86/kvm/x86.c | 9 ++++++---
virt/kvm/kvm_main.c | 18 ++++++++----------
3 files changed, 15 insertions(+), 13 deletions(-)
next reply other threads:[~2023-12-08 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 2:07 Sean Christopherson [this message]
2023-12-08 18:14 ` 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=20231208020734.1705867-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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®