Changes in Kconfig

f9aad622 - mm: rename GENERIC_PTDUMP and PTDUMP_CORE

Wed, 26 Feb 2025 12:24:04 +0000

mm: rename GENERIC_PTDUMP and PTDUMP_COREPlatforms subscribe into generic ptdump implementation via GENERIC_PTDUMP.But generic ptdump gets enabled via PTDUMP_CORE. These configscombination is confusing as they sound very similar and does notdifferentiate between platform's feature subscription and featureenablement for ptdump. Rename the configs as ARCH_HAS_PTDUMP and PTDUMPmaking it more clear and improve readability.Link: https://lkml.kernel.org/r/20250226122404.1927473-6-anshuman.khandual@arm.comSigned-off-by: Anshuman Khandual Reviewed-by: Christophe Leroy (powerpc)Acked-by: Catalin Marinas [arm64]Cc: Will Deacon Cc: Jonathan Corbet Cc: Marc Zyngier Cc: Michael Ellerman Cc: Nicholas Piggin Cc: Paul Walmsley Cc: Palmer Dabbelt Cc: Heiko Carstens Cc: Vasily Gorbik Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Christophe Leroy Cc: Madhavan Srinivasan Cc: Mark Rutland Cc: Steven Price Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/arm64/kvm/Kconfig

7c4f7354 - KVM: arm64: Register ptdump with debugfs on guest creation

Mon, 09 Sep 2024 12:47:21 +0000

KVM: arm64: Register ptdump with debugfs on guest creationWhile arch/*/mem/ptdump handles the kernel pagetable dumping code,introduce KVM/ptdump to show the guest stage-2 pagetables. Theseparation is necessary because most of the definitions from thestage-2 pagetable reside in the KVM path and we will be invokingfunctionality specific to KVM. Introduce the PTDUMP_STAGE2_DEBUGFS config.When a guest is created, register a new file entry under the guestdebugfs dir which allows userspace to show the contents of the gueststage-2 pagetables when accessed.[maz: moved function prototypes from kvm_host.h to kvm_mmu.h]Signed-off-by: Sebastian Ene Reviewed-by: Vincent Donnefort Link: https://lore.kernel.org/r/20240909124721.1672199-6-sebastianene@google.comSigned-off-by: Marc Zyngier List of files: /linux-6.15/arch/arm64/kvm/Kconfig

10f2ad03 - KVM: arm64: Enforce dependency on an ARMv8.4-aware toolchain

Wed, 07 Aug 2024 11:51:44 +0000

KVM: arm64: Enforce dependency on an ARMv8.4-aware toolchainWith the NV support of TLBI-range operations, KVM makes use ofinstructions that are only supported by binutils versions >= 2.30.This breaks the build for very old toolchains.Make KVM support conditional on having ARMv8.4 support in theassembler, side-stepping the issue.Fixes: 5d476ca57d7d ("KVM: arm64: nv: Add handling of range-based TLBI operations")Reported-by: Viresh Kumar Suggested-by: Arnd Bergmann Signed-off-by: Marc Zyngier Acked-by: Arnd Bergmann Link: https://lore.kernel.org/r/20240807115144.3237260-1-maz@kernel.orgSigned-off-by: Oliver Upton List of files: /linux-6.15/arch/arm64/kvm/Kconfig

82affc97 - Revert "KVM: arm64: Snapshot all non-zero RES0/RES1 sysreg fields for later checking"

Sat, 16 Mar 2024 00:24:57 +0000

Revert "KVM: arm64: Snapshot all non-zero RES0/RES1 sysreg fields for later checking"This reverts commits 99101dda29e3186b1356b0dc4dbb835c02c71ac9 andb80b701d5a67d07f4df4a21e09cb31f6bc1feeca.Linus reports that the sysreg reserved bit checks in KVM have led tobuild failures, arising from commit fdd867fe9b32 ("arm64/sysreg: Addregister fields for ID_AA64DFR1_EL1") giving meaning to fields that werepreviously RES0.Of course, this is a genuine issue, since KVM's sysreg emulation dependsheavily on the definition of reserved fields. But at this point thebuild breakage is far more offensive, and the right course of action isto revert and retry later.All of these build-time assertions were on by default beforecommit 99101dda29e3 ("KVM: arm64: Make build-time check of RES0/RES1bits optional"), so deliberately revert it all atomically to avoidintroducing further breakage of bisection.Link: https://lore.kernel.org/all/CAHk-=whCvkhc8BbFOUf1ddOsgSGgEjwoKv77=HEY1UiVCydGqw@mail.gmail.com/Acked-by: Marc Zyngier Signed-off-by: Oliver Upton Signed-off-by: Linus Torvalds List of files: /linux-6.15/arch/arm64/kvm/Kconfig

99101dda - KVM: arm64: Make build-time check of RES0/RES1 bits optional

Thu, 22 Feb 2024 14:12:09 +0000

KVM: arm64: Make build-time check of RES0/RES1 bits optionalIn order to ease the transition towards a state of absoluteparanoia where all RES0/RES1 bits gets checked against whatKVM know of them, make the checks optional and guarded by aconfig symbol (CONFIG_KVM_ARM64_RES_BITS_PARANOIA) default to n.Signed-off-by: Marc Zyngier Link: https://lore.kernel.org/kvm/87frxka7ud.wl-maz@kernel.org/Signed-off-by: Oliver Upton List of files: /linux-6.15/arch/arm64/kvm/Kconfig

52571d05 - KVM: arm64: Drop the requirement for XARRAY_MULTI

Wed, 14 Feb 2024 13:18:12 +0000

KVM: arm64: Drop the requirement for XARRAY_MULTINow that we don't use xa_store_range() anymore, drop the addedcomplexity of XARRAY_MULTI for KVM. It is likely still pulledin by other bits of the kernel though.Reviewed-by: Joey Gouly Signed-off-by: Marc Zyngier Link: https://lore.kernel.org/r/20240214131827.2856277-12-maz@kernel.orgSigned-off-by: Oliver Upton List of files: /linux-6.15/arch/arm64/kvm/Kconfig

f48212ee - treewide: remove CONFIG_HAVE_KVM

Thu, 04 Jan 2024 16:34:25 +0000

treewide: remove CONFIG_HAVE_KVMIt has no users anymore.Signed-off-by: Paolo Bonzini List of files: /linux-6.15/arch/arm64/kvm/Kconfig

61df71ee - kvm: move "select IRQ_BYPASS_MANAGER" to common code

Thu, 11 Jan 2024 08:02:05 +0000

kvm: move "select IRQ_BYPASS_MANAGER" to common codeCONFIG_IRQ_BYPASS_MANAGER is a dependency of the common code included byCONFIG_HAVE_KVM_IRQ_BYPASS. There is no advantage in adding the corresponding"select" directive to each architecture.Signed-off-by: Paolo Bonzini List of files: /linux-6.15/arch/arm64/kvm/Kconfig

8886640d - kvm: replace __KVM_HAVE_READONLY_MEM with Kconfig symbol

Thu, 11 Jan 2024 08:00:34 +0000

kvm: replace __KVM_HAVE_READONLY_MEM with Kconfig symbolKVM uses __KVM_HAVE_* symbols in the architecture-dependent uapi/asm/kvm.h to maskunused definitions in include/uapi/linux/kvm.h. __KVM_HAVE_READONLY_MEM howeverwas nothing but a misguided attempt to define KVM_CAP_READONLY_MEM only onarchitectures where KVM_CHECK_EXTENSION(KVM_CAP_READONLY_MEM) could possiblyreturn nonzero. This however does not make sense, and it prevented userspacefrom supporting this architecture-independent feature without recompilation.Therefore, these days __KVM_HAVE_READONLY_MEM does not mask anything andis only used in virt/kvm/kvm_main.c. Userspace does not need to test itand there should be no need for it to exist. Remove it and replace itwith a Kconfig symbol within Linux source code.Signed-off-by: Paolo Bonzini List of files: /linux-6.15/arch/arm64/kvm/Kconfig

42dfa94d - KVM: arm64: Do not source virt/lib/Kconfig twice

Sun, 04 Feb 2024 07:43:05 +0000

KVM: arm64: Do not source virt/lib/Kconfig twiceFor ARCH=arm64, virt/lib/Kconfig is sourced twice,from arch/arm64/kvm/Kconfig and from drivers/vfio/Kconfig.There is no good reason to parse virt/lib/Kconfig twice.Commit 2412405b3141 ("KVM: arm/arm64: register irq bypass consumeron ARM/ARM64") should not have added this 'source' directive.Signed-off-by: Masahiro Yamada Signed-off-by: Marc Zyngier Link: https://lore.kernel.org/r/20240204074305.31492-1-masahiroy@kernel.org List of files: /linux-6.15/arch/arm64/kvm/Kconfig

caadf876 - KVM: introduce CONFIG_KVM_COMMON

Thu, 04 Jan 2024 16:15:07 +0000

KVM: introduce CONFIG_KVM_COMMONCONFIG_HAVE_KVM is currently used by some architectures to eitherenabled the KVM config proper, or to enable host-side code that isnot part of the KVM module. However, CONFIG_KVM's "select" statementin virt/kvm/Kconfig corresponds to a third meaning, namely toenable common Kconfigs required by all architectures that supportKVM.These three meanings can be replaced respectively by anarchitecture-specific Kconfig, by IS_ENABLED(CONFIG_KVM), or bya new Kconfig symbol that is in turn selected by thearchitecture-specific "config KVM".Start by introducing such a new Kconfig symbol, CONFIG_KVM_COMMON.Unlike CONFIG_HAVE_KVM, it is selected by CONFIG_KVM, not byarchitecture code, and it brings in all dependencies of commonKVM code. In particular, INTERVAL_TREE was missing in loongarchand riscv, so that is another thing that is fixed.Fixes: 8132d887a702 ("KVM: remove CONFIG_HAVE_KVM_EVENTFD", 2023-12-08)Reported-by: Randy Dunlap Closes: https://lore.kernel.org/all/44907c6b-c5bd-4e4a-a921-e4d3825539d8@infradead.org/Reviewed-by: Andrew Jones Signed-off-by: Paolo Bonzini List of files: /linux-6.15/arch/arm64/kvm/Kconfig

c5b31cc2 - KVM: remove CONFIG_HAVE_KVM_IRQFD

Wed, 18 Oct 2023 16:07:32 +0000

KVM: remove CONFIG_HAVE_KVM_IRQFDAll platforms with a kernel irqchip have support for irqfd. Unify thetwo configuration items so that userspace can expect to use irqfd toinject interrupts into the irqchip.Signed-off-by: Paolo Bonzini List of files: /linux-6.15/arch/arm64/kvm/Kconfig

8132d887 - KVM: remove CONFIG_HAVE_KVM_EVENTFD

Wed, 18 Oct 2023 16:11:56 +0000

KVM: remove CONFIG_HAVE_KVM_EVENTFDvirt/kvm/eventfd.c is compiled unconditionally, meaning that the ioeventfdsmember of struct kvm is accessed unconditionally. CONFIG_HAVE_KVM_EVENTFDtherefore must be defined for KVM common code to compile successfully,remove it.Signed-off-by: Paolo Bonzini List of files: /linux-6.15/arch/arm64/kvm/Kconfig

f128cf8c - KVM: Convert KVM_ARCH_WANT_MMU_NOTIFIER to CONFIG_KVM_GENERIC_MMU_NOTIFIER

Fri, 27 Oct 2023 18:21:49 +0000

KVM: Convert KVM_ARCH_WANT_MMU_NOTIFIER to CONFIG_KVM_GENERIC_MMU_NOTIFIERConvert KVM_ARCH_WANT_MMU_NOTIFIER into a Kconfig and select it whereappropriate to effectively maintain existing behavior. Using a properKconfig will simplify building more functionality on top of KVM'smmu_notifier infrastructure.Add a forward declaration of kvm_gfn_range to kvm_types.h so thatincluding arch/powerpc/include/asm/kvm_ppc.h's with CONFIG_KVM=n doesn'tgenerate warnings due to kvm_gfn_range being undeclared. PPC defineshooks for PR vs. HV without guarding them via #ifdeffery, e.g. bool (*unmap_gfn_range)(struct kvm *kvm, struct kvm_gfn_range *range); bool (*age_gfn)(struct kvm *kvm, struct kvm_gfn_range *range); bool (*test_age_gfn)(struct kvm *kvm, struct kvm_gfn_range *range); bool (*set_spte_gfn)(struct kvm *kvm, struct kvm_gfn_range *range);Alternatively, PPC could forward declare kvm_gfn_range, but there's nogood reason not to define it in common KVM.Acked-by: Anup Patel Signed-off-by: Sean Christopherson Reviewed-by: Paolo Bonzini Reviewed-by: Fuad Tabba Tested-by: Fuad Tabba Message-Id: <20231027182217.3615211-8-seanjc@google.com>Signed-off-by: Paolo Bonzini List of files: /linux-6.15/arch/arm64/kvm/Kconfig

60046980 - KVM: arm64: nv: Select XARRAY_MULTI to fix build error

Wed, 16 Aug 2023 21:09:49 +0000

KVM: arm64: nv: Select XARRAY_MULTI to fix build errorpopulate_nv_trap_config() uses xa_store_range(), which is only builtwhen XARRAY_MULTI is set, so select that symbol to prevent the build error.aarch64-linux-ld: arch/arm64/kvm/emulate-nested.o: in function `populate_nv_trap_config':emulate-nested.c:(.init.text+0x17c): undefined reference to `xa_store_range'Fixes: e58ec47bf68d ("KVM: arm64: nv: Add trap forwarding infrastructure")Signed-off-by: Randy Dunlap Cc: Marc Zyngier Cc: Oliver Upton Cc: kvmarm@lists.linux.devCc: Catalin Marinas Cc: Will Deacon Cc: linux-arm-kernel@lists.infradead.orgSigned-off-by: Marc Zyngier Link: https://lore.kernel.org/r/20230816210949.17117-1-rdunlap@infradead.org List of files: /linux-6.15/arch/arm64/kvm/Kconfig

32121c81 - KVM: arm64: Use kvm_arch_flush_remote_tlbs()

Fri, 11 Aug 2023 04:51:16 +0000

KVM: arm64: Use kvm_arch_flush_remote_tlbs()Stop depending on CONFIG_HAVE_KVM_ARCH_TLB_FLUSH_ALL and opt tostandardize on kvm_arch_flush_remote_tlbs() since it avoidsduplicating the generic TLB stats across architectures that implementtheir own remote TLB flush.This adds an extra function call to the ARM64 kvm_flush_remote_tlbs()path, but that is a small cost in comparison to flushing remote TLBs.In addition, instead of just incrementing remote_tlb_flush_requestsstat, the generic interface would also increment theremote_tlb_flush stat.Signed-off-by: Raghavendra Rao Ananta Reviewed-by: Shaoqin Huang Reviewed-by: Gavin Shan Signed-off-by: Marc Zyngier Link: https://lore.kernel.org/r/20230811045127.3308641-4-rananta@google.com List of files: /linux-6.15/arch/arm64/kvm/Kconfig

79cf833b - kvm: Remove "select SRCU"

Fri, 24 Mar 2023 20:52:47 +0000

kvm: Remove "select SRCU"Now that the SRCU Kconfig option is unconditionally selected, there isno longer any point in selecting it. Therefore, remove the "select SRCU"Kconfig statements from the various KVM Kconfig files.Acked-by: Sean Christopherson (x86)Signed-off-by: Paul E. McKenney Cc: Huacai Chen Cc: Aleksandar Markovic Cc: Thomas Bogendoerfer Cc: Michael Ellerman Cc: Christophe Leroy Cc: Sean Christopherson Cc: Paolo Bonzini Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Borislav Petkov Cc: Dave Hansen Cc: "H. Peter Anvin" Cc: Acked-by: Marc Zyngier (arm64)Acked-by: Michael Ellerman (powerpc)Acked-by: Anup Patel (riscv)Acked-by: Heiko Carstens (s390)Reviewed-by: John Ogness Signed-off-by: Joel Fernandes (Google) List of files: /linux-6.15/arch/arm64/kvm/Kconfig

441f7bfa - KVM: Opt out of generic hardware enabling on s390 and PPC

Wed, 30 Nov 2022 23:09:33 +0000

KVM: Opt out of generic hardware enabling on s390 and PPCAllow architectures to opt out of the generic hardware enabling logic,and opt out on both s390 and PPC, which don't need to manually enablevirtualization as it's always on (when available).In addition to letting s390 and PPC drop a bit of dead code, this willhopefully also allow ARM to clean up its related code, e.g. ARM has itsown per-CPU flag to track which CPUs have enable hardware due to theneed to keep hardware enabled indefinitely when pKVM is enabled.Signed-off-by: Sean Christopherson Acked-by: Anup Patel Message-Id: <20221130230934.1014142-50-seanjc@google.com>Signed-off-by: Paolo Bonzini List of files: /linux-6.15/arch/arm64/kvm/Kconfig

9cb1096f - KVM: arm64: Enable ring-based dirty memory tracking

Thu, 10 Nov 2022 10:49:11 +0000

KVM: arm64: Enable ring-based dirty memory trackingEnable ring-based dirty memory tracking on ARM64: - Enable CONFIG_HAVE_KVM_DIRTY_RING_ACQ_REL. - Enable CONFIG_NEED_KVM_DIRTY_RING_WITH_BITMAP. - Set KVM_DIRTY_LOG_PAGE_OFFSET for the ring buffer's physical page offset. - Add ARM64 specific kvm_arch_allow_write_without_running_vcpu() to keep the site of saving vgic/its tables out of the no-running-vcpu radar.Signed-off-by: Gavin Shan Signed-off-by: Marc Zyngier Link: https://lore.kernel.org/r/20221110104914.31280-5-gshan@redhat.com List of files: /linux-6.15/arch/arm64/kvm/Kconfig

03fe9cd0 - KVM: arm64: Move PROTECTED_NVHE_STACKTRACE around

Wed, 27 Jul 2022 14:29:01 +0000

KVM: arm64: Move PROTECTED_NVHE_STACKTRACE aroundMake the dependency with EL2_DEBUG more obvious by moving thestacktrace configurtion *after* it.Signed-off-by: Marc Zyngier Reviewed-by: Kalesh Singh Tested-by: Kalesh Singh Reviewed-by: Oliver Upton Link: https://lore.kernel.org/r/20220727142906.1856759-2-maz@kernel.org List of files: /linux-6.15/arch/arm64/kvm/Kconfig