diff options
| author | Ben Gardon <[email protected]> | 2020-10-27 16:37:33 -0700 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2020-11-08 06:04:08 -0500 |
| commit | 4fd94ec7d566ee2f0b52111cc6d26dd311f8a7c3 (patch) | |
| tree | f247960684ec0a2b9d938874d9a88b49406c2016 /tools/perf/util/trace-event-scripting.c | |
| parent | 3be18630954672b889186e7be9b631f00134e954 (diff) | |
KVM: selftests: Introduce the dirty log perf test
The dirty log perf test will time verious dirty logging operations
(enabling dirty logging, dirtying memory, getting the dirty log,
clearing the dirty log, and disabling dirty logging) in order to
quantify dirty logging performance. This test can be used to inform
future performance improvements to KVM's dirty logging infrastructure.
This series was tested by running the following invocations on an Intel
Skylake machine:
dirty_log_perf_test -b 20m -i 100 -v 64
dirty_log_perf_test -b 20g -i 5 -v 4
dirty_log_perf_test -b 4g -i 5 -v 32
demand_paging_test -b 20m -v 64
demand_paging_test -b 20g -v 4
demand_paging_test -b 4g -v 32
All behaved as expected.
Signed-off-by: Ben Gardon <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions