[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230223142130.2338972-1-quanfafu@gmail.com>
Date: Thu, 23 Feb 2023 22:21:30 +0800
From: Quanfa Fu <quanfafu@...il.com>
To: seanjc@...gle.com, pbonzini@...hat.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
hpa@...or.com
Cc: x86@...nel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Quanfa Fu <quanfafu@...il.com>
Subject: [PATCH] KVM/x86: fix comment that should be user fault
The content of comment should be user fault not read. In order to avoid
confusion, fix the comment.
Signed-off-by: Quanfa Fu <quanfafu@...il.com>
---
arch/x86/kvm/vmx/vmx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
index 7eec0226d56a..3c1012039517 100644
--- a/arch/x86/kvm/vmx/vmx.c
+++ b/arch/x86/kvm/vmx/vmx.c
@@ -5668,7 +5668,7 @@ static int handle_ept_violation(struct kvm_vcpu *vcpu)
gpa = vmcs_read64(GUEST_PHYSICAL_ADDRESS);
trace_kvm_page_fault(vcpu, gpa, exit_qualification);
- /* Is it a read fault? */
+ /* Is it a user fault? */
error_code = (exit_qualification & EPT_VIOLATION_ACC_READ)
? PFERR_USER_MASK : 0;
/* Is it a write fault? */
--
2.31.1
Powered by blists - more mailing lists