[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220701065558.9073-1-jiaming@nfschina.com>
Date: Fri, 1 Jul 2022 14:55:58 +0800
From: Zhang Jiaming <jiaming@...china.com>
To: pbonzini@...hat.com, seanjc@...gle.com, vkuznets@...hat.com,
wanpengli@...cent.com, jmattson@...gle.com, joro@...tes.org,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
liqiong@...china.com, renyu@...china.com,
Zhang Jiaming <jiaming@...china.com>
Subject: [PATCH] KVM: LAPIC: Fix a spelling mistake in comments
There is a typo (writeable) in kvm_apic_match_physical_addr's comments.
Fix it.
Signed-off-by: Zhang Jiaming <jiaming@...china.com>
---
arch/x86/kvm/lapic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
index 0e68b4c937fc..ace161bf3744 100644
--- a/arch/x86/kvm/lapic.c
+++ b/arch/x86/kvm/lapic.c
@@ -808,7 +808,7 @@ static bool kvm_apic_match_physical_addr(struct kvm_lapic *apic, u32 mda)
* Hotplug hack: Make LAPIC in xAPIC mode also accept interrupts as if
* it were in x2APIC mode. Hotplugged VCPUs start in xAPIC mode and
* this allows unique addressing of VCPUs with APIC ID over 0xff.
- * The 0xff condition is needed because writeable xAPIC ID.
+ * The 0xff condition is needed because writable xAPIC ID.
*/
if (kvm_x2apic_id(apic) > 0xff && mda == kvm_x2apic_id(apic))
return true;
--
2.25.1
Powered by blists - more mailing lists