From: Paolo Bonzini <pbonzini@redhat.com>
To: Ben Gardon <bgardon@google.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org
Cc: Peter Xu <peterx@redhat.com>, Andrew Jones <drjones@redhat.com>,
Peter Shier <pshier@google.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Thomas Huth <thuth@redhat.com>, Peter Feiner <pfeiner@google.com>
Subject: Re: [PATCH 0/5] Add a dirty logging performance test
Date: Fri, 6 Nov 2020 13:48:29 +0100 [thread overview]
Message-ID: <9885dac0-ca34-c680-ee44-e1a33e56aa4e@redhat.com> (raw)
In-Reply-To: <20201027233733.1484855-1-bgardon@google.com>
On 28/10/20 00:37, Ben Gardon wrote:
> Currently KVM lacks a simple, userspace agnostic, performance benchmark for
> dirty logging. Such a benchmark will be beneficial for ensuring that dirty
> logging performance does not regress, and to give a common baseline for
> validating performance improvements. The dirty log perf test introduced in
> this series builds on aspects of the existing demand paging perf test and
> provides time-based performance metrics for enabling and disabling dirty
> logging, getting the dirty log, and dirtying memory.
>
> While the test currently only has a build target for x86, I expect it will
> work on, or be easily modified to support other architectures.
>
> Ben Gardon (5):
> KVM: selftests: Factor code out of demand_paging_test
> KVM: selftests: Remove address rounding in guest code
> KVM: selftests: Simplify demand_paging_test with timespec_diff_now
> KVM: selftests: Add wrfract to common guest code
> KVM: selftests: Introduce the dirty log perf test
>
> tools/testing/selftests/kvm/.gitignore | 1 +
> tools/testing/selftests/kvm/Makefile | 1 +
> .../selftests/kvm/demand_paging_test.c | 230 ++---------
> .../selftests/kvm/dirty_log_perf_test.c | 382 ++++++++++++++++++
> .../selftests/kvm/include/perf_test_util.h | 192 +++++++++
> .../testing/selftests/kvm/include/test_util.h | 2 +
> tools/testing/selftests/kvm/lib/test_util.c | 22 +-
> 7 files changed, 635 insertions(+), 195 deletions(-)
> create mode 100644 tools/testing/selftests/kvm/dirty_log_perf_test.c
> create mode 100644 tools/testing/selftests/kvm/include/perf_test_util.h
>
Queued, thanks.
Paolo
next prev parent reply other threads:[~2020-11-06 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 23:37 [PATCH 0/5] Add a dirty logging performance test Ben Gardon
2020-10-27 23:37 ` [PATCH 1/5] KVM: selftests: Factor code out of demand_paging_test Ben Gardon
2020-11-02 21:23 ` Peter Xu
2020-11-02 22:57 ` Ben Gardon
2020-10-27 23:37 ` [PATCH 2/5] KVM: selftests: Remove address rounding in guest code Ben Gardon
2020-11-02 21:25 ` Peter Xu
2020-10-27 23:37 ` [PATCH 3/5] KVM: selftests: Simplify demand_paging_test with timespec_diff_now Ben Gardon
2020-11-02 21:27 ` Peter Xu
2020-11-02 22:59 ` Ben Gardon
2020-10-27 23:37 ` [PATCH 4/5] KVM: selftests: Add wrfract to common guest code Ben Gardon
2020-10-27 23:37 ` [PATCH 5/5] KVM: selftests: Introduce the dirty log perf test Ben Gardon
2020-11-02 22:21 ` Peter Xu
2020-11-02 23:56 ` Ben Gardon
2020-11-03 1:12 ` Peter Xu
2020-11-03 22:17 ` Ben Gardon
2020-11-03 22:27 ` Peter Xu
2020-11-06 12:48 ` Paolo Bonzini [this message]
2020-11-09 9:21 ` [PATCH 0/5] Add a dirty logging performance test Andrew Jones
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=9885dac0-ca34-c680-ee44-e1a33e56aa4e@redhat.com \
--to=pbonzini@redhat.com \
--cc=bgardon@google.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=pfeiner@google.com \
--cc=pshier@google.com \
--cc=sean.j.christopherson@intel.com \
--cc=thuth@redhat.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