Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH v3 0/2] KVM: x86: Enable dirty logging lazily for huge
 pages
To:     <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
        Paolo Bonzini <pbonzini@redhat.com>,
        Sean Christopherson <seanjc@google.com>,
        Ben Gardon <bgardon@google.com>
References: <20210429034115.35560-1-zhukeqian1@huawei.com>
CC:     <wanghaibin.wang@huawei.com>
From:   Keqian Zhu <zhukeqian1@huawei.com>
Message-ID: <cca6e81d-fec6-d461-3580-54865f11ee51@huawei.com>
Date:   Tue, 11 May 2021 14:49:20 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20210429034115.35560-1-zhukeqian1@huawei.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

ping. ^_^

On 2021/4/29 11:41, Keqian Zhu wrote:
> Hi,
> 
> Currently during start dirty logging, if we're with init-all-set,
> we write protect huge pages and leave normal pages untouched, for
> that we can enable dirty logging for these pages lazily.
> 
> Actually enable dirty logging lazily for huge pages is feasible
> too, which not only reduces the time of start dirty logging, also
> greatly reduces side-effect on guest when there is high dirty rate.
> 
> Thanks,
> Keqian
> 
> Changelog:
> 
> v3:
>  - Discussed with Ben and delete RFC comments. Thanks.
> 
> Keqian Zhu (2):
>   KVM: x86: Support write protect gfn with min_level
>   KVM: x86: Not wr-protect huge page with init_all_set dirty log
> 
>  arch/x86/kvm/mmu/mmu.c          | 38 ++++++++++++++++++++++++++-------
>  arch/x86/kvm/mmu/mmu_internal.h |  3 ++-
>  arch/x86/kvm/mmu/page_track.c   |  2 +-
>  arch/x86/kvm/mmu/tdp_mmu.c      | 16 ++++++++++----
>  arch/x86/kvm/mmu/tdp_mmu.h      |  3 ++-
>  arch/x86/kvm/x86.c              | 37 +++++++++-----------------------
>  6 files changed, 57 insertions(+), 42 deletions(-)
>