Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 19 Jan 2023 20:54:04 +0000
In-Reply-To: <20230105100310.6700-1-jiangshanlai@gmail.com>
Mime-Version: 1.0
References: <20230105100310.6700-1-jiangshanlai@gmail.com>
Message-ID: <167408804666.2363885.5695334430262199072.b4-ty@google.com>
Subject: Re: [PATCH] kvm: x86/mmu: Don't clear write flooding for direct SP
From:   Sean Christopherson <seanjc@google.com>
To:     Sean Christopherson <seanjc@google.com>,
        linux-kernel@vger.kernel.org,
        Lai Jiangshan <jiangshanlai@gmail.com>
Cc:     Paolo Bonzini <pbonzini@redhat.com>,
        Lai Jiangshan <jiangshan.ljs@antgroup.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
        Dave Hansen <dave.hansen@linux.intel.com>, x86@kernel.org,
        "H. Peter Anvin" <hpa@zytor.com>, kvm@vger.kernel.org
Content-Type: text/plain; charset="utf-8"
Precedence: bulk

On Thu, 05 Jan 2023 18:03:10 +0800, Lai Jiangshan wrote:
> Although there is no harm, but there is no point to clear write
> flooding for direct SP.
> 
> 

Applied to kvm-x86 mmu, thanks!

[1/1] kvm: x86/mmu: Don't clear write flooding for direct SP
      https://github.com/kvm-x86/linux/commit/5ee0c3718540

--
https://github.com/kvm-x86/linux/tree/next
https://github.com/kvm-x86/linux/tree/fixes