[PATCH] kvm: x86/mmu: Remove duplicated "be split" in spte.h

Lai Jiangshan posted 1 patch 2 years, 9 months ago
arch/x86/kvm/mmu/spte.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[PATCH] kvm: x86/mmu: Remove duplicated "be split" in spte.h
Posted by Lai Jiangshan 2 years, 9 months ago
From: Lai Jiangshan <jiangshan.ljs@antgroup.com>

"be split be split" -> "be split"

Signed-off-by: Lai Jiangshan <jiangshan.ljs@antgroup.com>
---
 arch/x86/kvm/mmu/spte.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/kvm/mmu/spte.h b/arch/x86/kvm/mmu/spte.h
index 1f03701b943a..6f54dc9409c9 100644
--- 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
-- 
2.19.1.6.gb485710b
Re: [PATCH] kvm: x86/mmu: Remove duplicated "be split" in spte.h
Posted by Paolo Bonzini 2 years, 9 months ago
On 12/7/22 13:05, Lai Jiangshan wrote:
> From: Lai Jiangshan <jiangshan.ljs@antgroup.com>
> 
> "be split be split" -> "be split"
> 
> Signed-off-by: Lai Jiangshan <jiangshan.ljs@antgroup.com>
> ---
>   arch/x86/kvm/mmu/spte.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kvm/mmu/spte.h b/arch/x86/kvm/mmu/spte.h
> index 1f03701b943a..6f54dc9409c9 100644
> --- 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

Queued, thanks.

Paolo