From: Maxim Levitsky <mlevitsk@redhat.com>
Date: Wed, 2 Mar 2022 10:24:57 +0000 (+0200)
Subject: KVM: x86: mmu: trace kvm_mmu_set_spte after the new SPTE was set
X-Git-Tag: baikal/mips/sdk6.1~6044^2~13
X-Git-Url: https://git.baikalelectronics.ru/sdk/?a=commitdiff_plain;h=b9f091766b90e1d9e4823b1ec92b726d65ca704f;p=kernel.git

KVM: x86: mmu: trace kvm_mmu_set_spte after the new SPTE was set

It makes more sense to print new SPTE value than the
old value.

Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
Reviewed-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20220302102457.588450-1-mlevitsk@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---

diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
index e6ce39a798b8f..8f19ea7527042 100644
--- a/arch/x86/kvm/mmu/mmu.c
+++ b/arch/x86/kvm/mmu/mmu.c
@@ -2696,8 +2696,8 @@ static int mmu_set_spte(struct kvm_vcpu *vcpu, struct kvm_memory_slot *slot,
 	if (*sptep == spte) {
 		ret = RET_PF_SPURIOUS;
 	} else {
-		trace_kvm_mmu_set_spte(level, gfn, sptep);
 		flush |= mmu_spte_update(sptep, spte);
+		trace_kvm_mmu_set_spte(level, gfn, sptep);
 	}
 
 	if (wrprot) {