From: Sean Christopherson <seanjc@google.com>
To: Vipin Sharma <vipinsh@google.com>
Cc: Ben Gardon <bgardon@google.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>, Peter Xu <peterx@redhat.com>,
David Matlack <dmatlack@google.com>,
Ricardo Koller <ricarkol@google.com>
Subject: Re: [PATCH v4 0/2] selftests: KVM: Add a test for eager page splitting
Date: Tue, 31 Jan 2023 16:57:32 +0000 [thread overview]
Message-ID: <Y9lIfGtMEEsaw6cd@google.com> (raw)
In-Reply-To: <CAHVum0eKdcsZ-6L0ypqL1CBW+2quyj_dPiqw83b-XMShoRkvig@mail.gmail.com>
On Thu, Jan 26, 2023, Vipin Sharma wrote:
> On Wed, Jan 25, 2023 at 10:23 AM Ben Gardon <bgardon@google.com> wrote:
> >
> > David Matlack recently added a feature known as eager page splitting
> > to x86 KVM. This feature improves vCPU performance during dirty
> > logging because the splitting operation is moved out of the page
> > fault path, avoiding EPT/NPT violations or allowing the vCPU threads
> > to resolve the violation in the fast path.
> >
> > While this feature is a great performance improvement, it does not
> > have adequate testing in KVM selftests. Add a test to provide coverage
> > of eager page splitting.
> >
> > Patch 1 is a quick refactor to be able to re-use some code from
> > dirty_log_perf_test.
> > Patch 2 adds the actual test.
> >
> > V1->V2:
> Links of previous versions of patches are helpful and avoid searching
> if one wants to read previous discussions.
+1
I also strongly prefer versioning to go from newest=>oldest instead of oldest=>newest,
that way reviewers can quickly see the delta for _this_ version. It doesn't matter
too much when the delta is small, but oldest=>newest gets _really_ annoying the
longer the list gets.
> > Run test in multiple modes, as suggested by David and Ricardo
> > Cleanups from shameful copy-pasta, as suggested by David
> > V2->V3:
> > Removed copyright notice from the top of
> > dirty_log_page_splitting.c
> > Adopted ASSERT_EQ for test assertions
> > Now skipping testing with MANUAL_PROTECT if unsupported
> > V3->V4:
> > Added the copyright notices back. Thanks Vipin for the right
> > thing to do there.
Please do _something_ to differentiate line items. I would also drop the tabs in
favor of a single space or two so that you don't end up wrapping so much. E.g.
(choose your preferred flavor of list item identifiers)
V3->V4:
- Added the copyright notices back. Thanks Vipin for the right thing to do
there
V2->V3:
- Removed copyright notice from the top of dirty_log_page_splitting.c
- Adopted ASSERT_EQ for test assertions
- Now skipping testing with MANUAL_PROTECT if unsupported
prev parent reply other threads:[~2023-01-31 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 18:23 [PATCH v4 0/2] selftests: KVM: Add a test for eager page splitting Ben Gardon
2023-01-25 18:23 ` [PATCH v4 1/2] selftests: KVM: Move dirty logging functions to memstress.(c|h) Ben Gardon
2023-01-25 18:23 ` [PATCH v4 2/2] selftests: KVM: Add dirty logging page splitting test Ben Gardon
2023-01-26 20:06 ` Vipin Sharma
2023-01-26 22:51 ` Ben Gardon
2023-01-26 23:03 ` Vipin Sharma
2023-01-26 23:11 ` Ben Gardon
2023-01-27 0:13 ` David Matlack
2023-01-26 20:09 ` [PATCH v4 0/2] selftests: KVM: Add a test for eager page splitting Vipin Sharma
2023-01-31 16:57 ` Sean Christopherson [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=Y9lIfGtMEEsaw6cd@google.com \
--to=seanjc@google.com \
--cc=bgardon@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=ricarkol@google.com \
--cc=vipinsh@google.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