KVM: x86: Unify pr_fmt to use module name for all KVM modules

[linux-block.git] / arch / x86 / kvm / mmu / spte.h

diff --git a/arch/x86/kvm/mmu/spte.h b/arch/x86/kvm/mmu/spte.h
index 1f03701b943a1cac91fe7dac6a5f3514c5b9d6dc..0d8deefee66ce46938908ee5dafa71448969d50f 100644 (file)
--- a/arch/x86/kvm/mmu/spte.h
+++ b/arch/x86/kvm/mmu/spte.h
@@ -363,7 +363,7 @@ static __always_inline bool is_rsvd_spte(struct rsvd_bits_validate *rsvd_check,
  * A shadow-present leaf SPTE may be non-writable for 4 possible reasons:
  *
  *  1. To intercept writes for dirty logging. KVM write-protects huge pages
- *     so that they can be split be split down into the dirty logging
+ *     so that they can be split down into the dirty logging
  *     granularity (4KiB) whenever the guest writes to them. KVM also
  *     write-protects 4KiB pages so that writes can be recorded in the dirty log
  *     (e.g. if not using PML). SPTEs are write-protected for dirty logging
@@ -435,11 +435,11 @@ static inline void check_spte_writable_invariants(u64 spte)
 {
        if (spte & shadow_mmu_writable_mask)
                WARN_ONCE(!(spte & shadow_host_writable_mask),
-                         "kvm: MMU-writable SPTE is not Host-writable: %llx",
+                         KBUILD_MODNAME ": MMU-writable SPTE is not Host-writable: %llx",
                          spte);
        else
                WARN_ONCE(is_writable_pte(spte),
-                         "kvm: Writable SPTE is not MMU-writable: %llx", spte);
+                         KBUILD_MODNAME ": Writable SPTE is not MMU-writable: %llx", spte);
 }
 
 static inline bool is_mmu_writable_spte(u64 spte)