From: Sean Christopherson <seanjc@google.com>
To: Colton Lewis <coltonlewis@google.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, maz@kernel.org,
dmatlack@google.com, oupton@google.com, ricarkol@google.com
Subject: Re: [PATCH v7 0/3] KVM: selftests: randomize memory access of dirty_log_perf_test
Date: Wed, 26 Oct 2022 21:13:22 +0000 [thread overview]
Message-ID: <Y1mi8l4YwG/FlaKt@google.com> (raw)
In-Reply-To: <20221019221321.3033920-1-coltonlewis@google.com>
On Wed, Oct 19, 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.
>
> v7:
>
> Encapsulate the random state inside a struct. Add detail to names of
> those functions. Change interface so random function returns the next
> random number rather than using an out parameter.
>
> Rebased to kvm/queue to ensure freshness.
>
> Colton Lewis (3):
> KVM: selftests: implement random number generation for guest code
> KVM: selftests: randomize which pages are written vs read
> KVM: selftests: randomize page access order
A few mechanical comments, but otherwise looks good.
prev parent reply other threads:[~2022-10-26 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 22:13 [PATCH v7 0/3] KVM: selftests: randomize memory access of dirty_log_perf_test Colton Lewis
2022-10-19 22:13 ` [PATCH v7 1/3] KVM: selftests: implement random number generation for guest code Colton Lewis
2022-10-26 21:09 ` Sean Christopherson
2022-10-27 19:44 ` Colton Lewis
2022-10-27 20:17 ` Sean Christopherson
2022-10-19 22:13 ` [PATCH v7 2/3] KVM: selftests: randomize which pages are written vs read Colton Lewis
2022-10-19 22:13 ` [PATCH v7 3/3] KVM: selftests: randomize page access order Colton Lewis
2022-10-26 21:13 ` Sean Christopherson
2022-10-27 19:44 ` Colton Lewis
2022-10-26 21:13 ` Sean Christopherson [this message]
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=Y1mi8l4YwG/FlaKt@google.com \
--to=seanjc@google.com \
--cc=coltonlewis@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=ricarkol@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.