summaryrefslogtreecommitdiffstats
path: root/scripts/bootgraph.pl
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2024-01-04 11:15:07 -0500
committerPaolo Bonzini <pbonzini@redhat.com>2024-01-08 08:09:38 -0500
commitcaadf876bb7449bf25ef817afe7fb881df8198a2 (patch)
tree8c34dbb7814b2cc8973f0da29fe96b91f9a06b01 /scripts/bootgraph.pl
parent9cc52627c702b73c633737db40914ab8fc467de8 (diff)
downloadlinux-stable-caadf876bb7449bf25ef817afe7fb881df8198a2.tar.gz
linux-stable-caadf876bb7449bf25ef817afe7fb881df8198a2.tar.bz2
linux-stable-caadf876bb7449bf25ef817afe7fb881df8198a2.zip
KVM: introduce CONFIG_KVM_COMMON
CONFIG_HAVE_KVM is currently used by some architectures to either enabled the KVM config proper, or to enable host-side code that is not part of the KVM module. However, CONFIG_KVM's "select" statement in virt/kvm/Kconfig corresponds to a third meaning, namely to enable common Kconfigs required by all architectures that support KVM. These three meanings can be replaced respectively by an architecture-specific Kconfig, by IS_ENABLED(CONFIG_KVM), or by a new Kconfig symbol that is in turn selected by the architecture-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 by architecture code, and it brings in all dependencies of common KVM code. In particular, INTERVAL_TREE was missing in loongarch and riscv, so that is another thing that is fixed. Fixes: 8132d887a702 ("KVM: remove CONFIG_HAVE_KVM_EVENTFD", 2023-12-08) Reported-by: Randy Dunlap <rdunlap@infradead.org> Closes: https://lore.kernel.org/all/44907c6b-c5bd-4e4a-a921-e4d3825539d8@infradead.org/ Reviewed-by: Andrew Jones <ajones@ventanamicro.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/bootgraph.pl')
0 files changed, 0 insertions, 0 deletions