summaryrefslogtreecommitdiffstats
path: root/include/acpi/button.h
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2023-10-27 11:21:49 -0700
committerPaolo Bonzini <pbonzini@redhat.com>2023-11-13 05:29:09 -0500
commitf128cf8cfbecccf95e891ae90d9c917df5117c7a (patch)
tree1f390105ca6528c1641644879861e6906ddf0b63 /include/acpi/button.h
parent4a2e993faad3880962540ab8e3b68f22e48b18e8 (diff)
downloadlinux-stable-f128cf8cfbecccf95e891ae90d9c917df5117c7a.tar.gz
linux-stable-f128cf8cfbecccf95e891ae90d9c917df5117c7a.tar.bz2
linux-stable-f128cf8cfbecccf95e891ae90d9c917df5117c7a.zip
KVM: Convert KVM_ARCH_WANT_MMU_NOTIFIER to CONFIG_KVM_GENERIC_MMU_NOTIFIER
Convert KVM_ARCH_WANT_MMU_NOTIFIER into a Kconfig and select it where appropriate to effectively maintain existing behavior. Using a proper Kconfig will simplify building more functionality on top of KVM's mmu_notifier infrastructure. Add a forward declaration of kvm_gfn_range to kvm_types.h so that including arch/powerpc/include/asm/kvm_ppc.h's with CONFIG_KVM=n doesn't generate warnings due to kvm_gfn_range being undeclared. PPC defines hooks 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 no good reason not to define it in common KVM. Acked-by: Anup Patel <anup@brainfault.org> Signed-off-by: Sean Christopherson <seanjc@google.com> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> Reviewed-by: Fuad Tabba <tabba@google.com> Tested-by: Fuad Tabba <tabba@google.com> Message-Id: <20231027182217.3615211-8-seanjc@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'include/acpi/button.h')
0 files changed, 0 insertions, 0 deletions