提交 21ea4578 编写于 作者: J Julia Lawall 提交者: Marc Zyngier

KVM: arm64: fix typos in comments

Various spelling mistakes in comments.
Detected with the help of Coccinelle.
Signed-off-by: NJulia Lawall <Julia.Lawall@inria.fr>
Signed-off-by: NMarc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20220318103729.157574-24-Julia.Lawall@inria.fr
上级 06394531
...@@ -1690,7 +1690,7 @@ static void init_cpu_logical_map(void) ...@@ -1690,7 +1690,7 @@ static void init_cpu_logical_map(void)
/* /*
* Copy the MPIDR <-> logical CPU ID mapping to hyp. * Copy the MPIDR <-> logical CPU ID mapping to hyp.
* Only copy the set of online CPUs whose features have been chacked * Only copy the set of online CPUs whose features have been checked
* against the finalized system capabilities. The hypervisor will not * against the finalized system capabilities. The hypervisor will not
* allow any other CPUs from the `possible` set to boot. * allow any other CPUs from the `possible` set to boot.
*/ */
......
...@@ -282,7 +282,7 @@ static int set_core_reg(struct kvm_vcpu *vcpu, const struct kvm_one_reg *reg) ...@@ -282,7 +282,7 @@ static int set_core_reg(struct kvm_vcpu *vcpu, const struct kvm_one_reg *reg)
break; break;
/* /*
* Otherwide, this is a priviledged mode, and *all* the * Otherwise, this is a privileged mode, and *all* the
* registers must be narrowed to 32bit. * registers must be narrowed to 32bit.
*/ */
default: default:
......
...@@ -248,7 +248,7 @@ int handle_exit(struct kvm_vcpu *vcpu, int exception_index) ...@@ -248,7 +248,7 @@ int handle_exit(struct kvm_vcpu *vcpu, int exception_index)
case ARM_EXCEPTION_HYP_GONE: case ARM_EXCEPTION_HYP_GONE:
/* /*
* EL2 has been reset to the hyp-stub. This happens when a guest * EL2 has been reset to the hyp-stub. This happens when a guest
* is pre-empted by kvm_reboot()'s shutdown call. * is pre-emptied by kvm_reboot()'s shutdown call.
*/ */
run->exit_reason = KVM_EXIT_FAIL_ENTRY; run->exit_reason = KVM_EXIT_FAIL_ENTRY;
return 0; return 0;
......
...@@ -102,7 +102,7 @@ static void __hyp_attach_page(struct hyp_pool *pool, ...@@ -102,7 +102,7 @@ static void __hyp_attach_page(struct hyp_pool *pool,
* Only the first struct hyp_page of a high-order page (otherwise known * Only the first struct hyp_page of a high-order page (otherwise known
* as the 'head') should have p->order set. The non-head pages should * as the 'head') should have p->order set. The non-head pages should
* have p->order = HYP_NO_ORDER. Here @p may no longer be the head * have p->order = HYP_NO_ORDER. Here @p may no longer be the head
* after coallescing, so make sure to mark it HYP_NO_ORDER proactively. * after coalescing, so make sure to mark it HYP_NO_ORDER proactively.
*/ */
p->order = HYP_NO_ORDER; p->order = HYP_NO_ORDER;
for (; (order + 1) < pool->max_order; order++) { for (; (order + 1) < pool->max_order; order++) {
...@@ -110,7 +110,7 @@ static void __hyp_attach_page(struct hyp_pool *pool, ...@@ -110,7 +110,7 @@ static void __hyp_attach_page(struct hyp_pool *pool,
if (!buddy) if (!buddy)
break; break;
/* Take the buddy out of its list, and coallesce with @p */ /* Take the buddy out of its list, and coalesce with @p */
page_remove_from_list(buddy); page_remove_from_list(buddy);
buddy->order = HYP_NO_ORDER; buddy->order = HYP_NO_ORDER;
p = min(p, buddy); p = min(p, buddy);
......
...@@ -615,7 +615,7 @@ static struct kvm_pgtable_mm_ops kvm_s2_mm_ops = { ...@@ -615,7 +615,7 @@ static struct kvm_pgtable_mm_ops kvm_s2_mm_ops = {
}; };
/** /**
* kvm_init_stage2_mmu - Initialise a S2 MMU strucrure * kvm_init_stage2_mmu - Initialise a S2 MMU structure
* @kvm: The pointer to the KVM structure * @kvm: The pointer to the KVM structure
* @mmu: The pointer to the s2 MMU structure * @mmu: The pointer to the s2 MMU structure
* *
......
...@@ -37,7 +37,7 @@ struct vgic_global kvm_vgic_global_state __ro_after_init = { ...@@ -37,7 +37,7 @@ struct vgic_global kvm_vgic_global_state __ro_after_init = {
* If you need to take multiple locks, always take the upper lock first, * If you need to take multiple locks, always take the upper lock first,
* then the lower ones, e.g. first take the its_lock, then the irq_lock. * then the lower ones, e.g. first take the its_lock, then the irq_lock.
* If you are already holding a lock and need to take a higher one, you * If you are already holding a lock and need to take a higher one, you
* have to drop the lower ranking lock first and re-aquire it after having * have to drop the lower ranking lock first and re-acquire it after having
* taken the upper one. * taken the upper one.
* *
* When taking more than one ap_list_lock at the same time, always take the * When taking more than one ap_list_lock at the same time, always take the
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册