From: Keqian Zhu <zhukeqian1@huawei.com>
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>
Cc: <wanghaibin.wang@huawei.com>
Subject: Re: [PATCH v3 0/2] KVM: x86: Enable dirty logging lazily for huge pages
Date: Tue, 11 May 2021 14:49:20 +0800 [thread overview]
Message-ID: <cca6e81d-fec6-d461-3580-54865f11ee51@huawei.com> (raw)
In-Reply-To: <20210429034115.35560-1-zhukeqian1@huawei.com>
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(-)
>
prev parent reply other threads:[~2021-05-11 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 3:41 [PATCH v3 0/2] KVM: x86: Enable dirty logging lazily for huge pages Keqian Zhu
2021-04-29 3:41 ` [PATCH v3 1/2] KVM: x86: Support write protect gfn with min_level Keqian Zhu
2021-04-29 3:41 ` [PATCH v3 2/2] KVM: x86: Not wr-protect huge page with init_all_set dirty log Keqian Zhu
2021-05-24 12:12 ` Paolo Bonzini
2021-05-11 6:49 ` Keqian Zhu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cca6e81d-fec6-d461-3580-54865f11ee51@huawei.com \
--to=zhukeqian1@huawei.com \
--cc=bgardon@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=wanghaibin.wang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).