Searched hist:"870 d4d4ed82779e717ec7fb0f9b64f43bd7a736b" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/arch/x86/kvm/ |
| H A D | Kconfig | diff 870d4d4ed82779e717ec7fb0f9b64f43bd7a736b Fri Jul 28 19:47:19 CDT 2023 Sean Christopherson <seanjc@google.com> KVM: x86/mmu: Replace MMU_DEBUG with proper KVM_PROVE_MMU Kconfig
Replace MMU_DEBUG, which requires manually modifying KVM to enable the
macro, with a proper Kconfig, KVM_PROVE_MMU. Now that pgprintk() and
rmap_printk() are gone, i.e. the macro guards only KVM_MMU_WARN_ON() and
won't flood the kernel logs, enabling the option for debug kernels is both
desirable and feasible.
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Link: https://lore.kernel.org/r/20230729004722.1056172-10-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|
| /openbmc/linux/arch/x86/kvm/mmu/ |
| H A D | mmu.c | diff 870d4d4ed82779e717ec7fb0f9b64f43bd7a736b Fri Jul 28 19:47:19 CDT 2023 Sean Christopherson <seanjc@google.com> KVM: x86/mmu: Replace MMU_DEBUG with proper KVM_PROVE_MMU Kconfig
Replace MMU_DEBUG, which requires manually modifying KVM to enable the
macro, with a proper Kconfig, KVM_PROVE_MMU. Now that pgprintk() and
rmap_printk() are gone, i.e. the macro guards only KVM_MMU_WARN_ON() and
won't flood the kernel logs, enabling the option for debug kernels is both
desirable and feasible.
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Link: https://lore.kernel.org/r/20230729004722.1056172-10-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|