[v9,0/4] randomize memory access of dirty_log_perf_test

Message

Colton Lewis Nov. 2, 2022, 4 p.m. UTC

Add the ability to randomize parts of dirty_log_perf_test,
specifically the order pages are accessed and whether pages are read
or written.

v9:

Move declaration of rand_state to one commit later to reflect where it
is first used.

Formatting.

Colton Lewis (4):
  KVM: selftests: implement random number generator for guest code
  KVM: selftests: create -r argument to specify random seed
  KVM: selftests: randomize which pages are written vs read
  KVM: selftests: randomize page access order

 .../selftests/kvm/access_tracking_perf_test.c |  2 +-
 .../selftests/kvm/dirty_log_perf_test.c       | 57 ++++++++++++++-----
 .../selftests/kvm/include/perf_test_util.h    |  8 ++-
 .../testing/selftests/kvm/include/test_util.h |  7 +++
 .../selftests/kvm/lib/perf_test_util.c        | 33 +++++++++--
 tools/testing/selftests/kvm/lib/test_util.c   | 17 ++++++
 6 files changed, 100 insertions(+), 24 deletions(-)

--
2.38.1.273.g43a17bfeac-goog

Comments

Sean Christopherson Nov. 2, 2022, 11:38 p.m. UTC | #1

On Wed, Nov 02, 2022, Colton Lewis wrote:
> Add the ability to randomize parts of dirty_log_perf_test,
> specifically the order pages are accessed and whether pages are read
> or written.

David, or anyone else that's intimately familiar with dirty_log_perf_test, can
you look over the changes in patches 3 and 4?  They look good to me, but that
doesn't mean a whole lot :-)

David Matlack Nov. 2, 2022, 11:55 p.m. UTC | #2

On Wed, Nov 2, 2022 at 4:38 PM Sean Christopherson <[e-mail]> wrote:
>
> On Wed, Nov 02, 2022, Colton Lewis wrote:
> > Add the ability to randomize parts of dirty_log_perf_test,
> > specifically the order pages are accessed and whether pages are read
> > or written.
>
> David, or anyone else that's intimately familiar with dirty_log_perf_test, can
> you look over the changes in patches 3 and 4?  They look good to me, but that
> doesn't mean a whole lot :-)

Sure, will do.