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: [RFC PATCH v2 0/2] KVM: x86: Enable dirty logging lazily for huge pages
Date: Fri, 16 Apr 2021 16:25:09 +0800 [thread overview]
Message-ID: <20210416082511.2856-1-zhukeqian1@huawei.com> (raw)
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
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 | 57 ++++++++++++++++++++++++++++-----
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, 76 insertions(+), 42 deletions(-)
--
2.23.0
next reply other threads:[~2021-04-16 8:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 8:25 Keqian Zhu [this message]
2021-04-16 8:25 ` [RFC PATCH v2 1/2] KVM: x86: Support write protect gfn with min_level Keqian Zhu
2021-04-16 8:25 ` [RFC PATCH v2 2/2] KVM: x86: Not wr-protect huge page with init_all_set dirty log Keqian Zhu
2021-04-19 19:20 ` Ben Gardon
2021-04-20 7:49 ` Keqian Zhu
2021-04-20 16:30 ` Ben Gardon
2021-04-27 5:03 ` Keqian Zhu
2021-04-27 16:33 ` Ben Gardon
2021-04-28 10:51 ` Keqian Zhu
[not found] ` <60894846.1c69fb81.6e765.161bSMTPIN_ADDED_BROKEN@mx.google.com>
2021-04-28 16:22 ` Ben Gardon
2021-04-29 3:30 ` Keqian Zhu
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=20210416082511.2856-1-zhukeqian1@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
all inboxes | Powered by JetHome®