From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [PATCH 0/2] KVM: require generic MMU notifier implementation
Date: Thu, 12 Feb 2026 11:52:09 +0100 [thread overview]
Message-ID: <20260212105211.1555876-1-pbonzini@redhat.com> (raw)
With s390's switch to MMU notifier, all architectures select
CONFIG_KVM_GENERIC_MMU_NOTIFIER and define KVM_CAP_SYNC_MMU,
so remove the possibility to _not_ have them.
The only intricate Kconfig-ery is powerpc's, but there is
a nice pre-existing BUILD_BUG_ON to tell us that it *does*
in fact require CONFIG_KVM_GENERIC_MMU_NOTIFIER.
Paolo
Paolo Bonzini (2):
KVM: remove CONFIG_KVM_GENERIC_MMU_NOTIFIER
KVM: always define KVM_CAP_SYNC_MMU
Documentation/virt/kvm/api.rst | 10 ++++------
arch/arm64/kvm/Kconfig | 1 -
arch/arm64/kvm/arm.c | 1 -
arch/loongarch/kvm/Kconfig | 1 -
arch/loongarch/kvm/vm.c | 1 -
arch/mips/kvm/Kconfig | 1 -
arch/mips/kvm/mips.c | 1 -
arch/powerpc/kvm/Kconfig | 4 ----
arch/powerpc/kvm/powerpc.c | 6 ------
arch/riscv/kvm/Kconfig | 1 -
arch/riscv/kvm/vm.c | 1 -
arch/s390/kvm/Kconfig | 1 -
arch/s390/kvm/kvm-s390.c | 1 -
arch/x86/kvm/Kconfig | 1 -
arch/x86/kvm/x86.c | 1 -
include/linux/kvm_host.h | 7 +------
virt/kvm/Kconfig | 8 --------
virt/kvm/kvm_main.c | 17 +----------------
18 files changed, 6 insertions(+), 58 deletions(-)
--
2.52.0
next reply other threads:[~2026-02-12 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 10:52 Paolo Bonzini [this message]
2026-02-12 10:52 ` [PATCH 1/2] KVM: remove CONFIG_KVM_GENERIC_MMU_NOTIFIER Paolo Bonzini
2026-02-12 17:16 ` kernel test robot
2026-02-12 18:00 ` kernel test robot
2026-02-12 20:05 ` kernel test robot
2026-02-12 10:52 ` [PATCH 2/2] KVM: always define KVM_CAP_SYNC_MMU 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=20260212105211.1555876-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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®