From: Mingwei Zhang <mizhang@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>,
David Matlack <dmatlack@google.com>,
Jing Zhang <jingzhangos@google.com>, Peter Xu <peterx@redhat.com>,
Ben Gardon <bgardon@google.com>,
Mingwei Zhang <mizhang@google.com>
Subject: [PATCH v3 0/2] selftests: KVM: verify page stats in kvm x86/mmu
Date: Mon, 30 Aug 2021 04:44:23 +0000 [thread overview]
Message-ID: <20210830044425.2686755-1-mizhang@google.com> (raw)
This patch set leverages the existing dirty logging performance selftest to
verify whether the page stats work correctly in KVM x86/mmu especially with
the consequence of dirty logging.
v2 -> v3:
- fix the build error. [mizhang]
v1 -> v2:
- split the page alignment fix into a different commit [bgardon]
- update the TEST_ASSERT conditions [bgardon]
Mingwei Zhang (2):
selftests: KVM: align guest physical memory base address to 1GB
selftests: KVM: use dirty logging to check if page stats work
correctly
.../selftests/kvm/dirty_log_perf_test.c | 44 +++++++++++++++++++
.../testing/selftests/kvm/include/test_util.h | 1 +
.../selftests/kvm/include/x86_64/processor.h | 7 +++
.../selftests/kvm/lib/perf_test_util.c | 8 ++--
tools/testing/selftests/kvm/lib/test_util.c | 29 ++++++++++++
5 files changed, 85 insertions(+), 4 deletions(-)
--
2.33.0.259.gc128427fd7-goog
next reply other threads:[~2021-08-30 4:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 4:44 Mingwei Zhang [this message]
2021-08-30 4:44 ` [PATCH v3 1/2] selftests: KVM: align guest physical memory base address to 1GB Mingwei Zhang
2021-08-30 20:58 ` Ben Gardon
2021-08-30 4:44 ` [PATCH v3 2/2] selftests: KVM: use dirty logging to check if page stats work correctly Mingwei Zhang
2021-08-30 21:10 ` Ben Gardon
2021-08-31 16:58 ` Sean Christopherson
2021-09-06 20:05 ` Mingwei Zhang
2021-09-08 16:07 ` Mingwei Zhang
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=20210830044425.2686755-1-mizhang@google.com \
--to=mizhang@google.com \
--cc=bgardon@google.com \
--cc=dmatlack@google.com \
--cc=jingzhangos@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=seanjc@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;
as well as URLs for NNTP newsgroup(s).