summaryrefslogtreecommitdiff
path: root/lib/debugobjects.c
diff options
context:
space:
mode:
authorBen Gardon <bgardon@google.com>2020-10-28 02:37:33 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2020-11-08 14:04:08 +0300
commit4fd94ec7d566ee2f0b52111cc6d26dd311f8a7c3 (patch)
treef247960684ec0a2b9d938874d9a88b49406c2016 /lib/debugobjects.c
parent3be18630954672b889186e7be9b631f00134e954 (diff)
downloadlinux-4fd94ec7d566ee2f0b52111cc6d26dd311f8a7c3.tar.xz
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 <bgardon@google.com> Message-Id: <20201027233733.1484855-6-bgardon@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'lib/debugobjects.c')
0 files changed, 0 insertions, 0 deletions