From: David Matlack <dmatlack@google.com>
To: Colton Lewis <coltonlewis@google.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, maz@kernel.org,
seanjc@google.com, oupton@google.com, ricarkol@google.com
Subject: Re: [PATCH 2/3] KVM: selftests: Randomize which pages are written vs read
Date: Wed, 10 Aug 2022 16:33:44 -0700 [thread overview]
Message-ID: <YvRAWKGXbPzool6j@google.com> (raw)
In-Reply-To: <20220810175830.2175089-3-coltonlewis@google.com>
On Wed, Aug 10, 2022 at 05:58:29PM +0000, Colton Lewis wrote:
> Randomize which pages are written vs read by using the random number
Same thing here about stating what the patch does first.
> table for each page modulo 100. This changes how the -w argument
s/-f/-w/
Although I would love it if you renamed -f to -w in the code instead.
> works. It is now a percentage from 0 to 100 inclusive that represents
> what percentage of accesses are writes. It keeps the same default of
> 100 percent writes.
>
> Signed-off-by: Colton Lewis <coltonlewis@google.com>
> ---
> tools/testing/selftests/kvm/dirty_log_perf_test.c | 12 +++++++-----
access_tracking_perf_test.c also uses wr_fract and will need to be
updated.
> tools/testing/selftests/kvm/lib/perf_test_util.c | 4 ++--
> 2 files changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/dirty_log_perf_test.c b/tools/testing/selftests/kvm/dirty_log_perf_test.c
> index 80a1cbe7fbb0..dcc5d44fc757 100644
> --- a/tools/testing/selftests/kvm/dirty_log_perf_test.c
> +++ b/tools/testing/selftests/kvm/dirty_log_perf_test.c
> @@ -381,8 +381,8 @@ static void help(char *name)
> " (default: 1G)\n");
> printf(" -f: specify the fraction of pages which should be written to\n"
s/fraction/percentage/
> " as opposed to simply read, in the form\n"
> - " 1/<fraction of pages to write>.\n"
> - " (default: 1 i.e. all pages are written to.)\n");
> + " [0-100]%% of pages to write.\n"
> + " (default: 100 i.e. all pages are written to.)\n");
Mention that the implementation is probabilistic.
> printf(" -v: specify the number of vCPUs to run.\n");
> printf(" -o: Overlap guest memory accesses instead of partitioning\n"
> " them into a separate region of memory for each vCPU.\n");
> @@ -399,7 +399,7 @@ int main(int argc, char *argv[])
> int max_vcpus = kvm_check_cap(KVM_CAP_MAX_VCPUS);
> struct test_params p = {
> .iterations = TEST_HOST_LOOP_N,
> - .wr_fract = 1,
> + .wr_fract = 100,
Please rename wr_fract to e.g. write_percent to reflect the new
semantics. Same goes for perf_test_set_wr_fract(),
perf_test_args.wr_fract, etc.
> .partition_vcpu_memory_access = true,
> .backing_src = DEFAULT_VM_MEM_SRC,
> .slots = 1,
> @@ -439,8 +439,10 @@ int main(int argc, char *argv[])
> break;
> case 'f':
> p.wr_fract = atoi(optarg);
> - TEST_ASSERT(p.wr_fract >= 1,
> - "Write fraction cannot be less than one");
> + TEST_ASSERT(p.wr_fract >= 0,
> + "Write fraction cannot be less than 0");
> + TEST_ASSERT(p.wr_fract <= 100,
> + "Write fraction cannot be greater than 100");
nit: This could be combined into a single assert pretty easily.
> break;
> case 'v':
> nr_vcpus = atoi(optarg);
> diff --git a/tools/testing/selftests/kvm/lib/perf_test_util.c b/tools/testing/selftests/kvm/lib/perf_test_util.c
> index b04e8d2c0f37..3c7b93349fef 100644
> --- a/tools/testing/selftests/kvm/lib/perf_test_util.c
> +++ b/tools/testing/selftests/kvm/lib/perf_test_util.c
> @@ -64,7 +64,7 @@ void perf_test_guest_code(uint32_t vcpu_idx)
> for (i = 0; i < pages; i++) {
> uint64_t addr = gva + (i * pta->guest_page_size);
>
> - if (i % pta->wr_fract == 0)
> + if (random_table[vcpu_idx][i] % 100 < pta->wr_fract)
> *(uint64_t *)addr = 0x0123456789ABCDEF;
> else
> READ_ONCE(*(uint64_t *)addr);
> @@ -168,7 +168,7 @@ struct kvm_vm *perf_test_create_vm(enum vm_guest_mode mode, int nr_vcpus,
> pr_info("Testing guest mode: %s\n", vm_guest_mode_string(mode));
>
> /* By default vCPUs will write to memory. */
> - pta->wr_fract = 1;
> + pta->wr_fract = 100;
>
> /*
> * Snapshot the non-huge page size. This is used by the guest code to
> --
> 2.37.1.559.g78731f0fdb-goog
>
next prev parent reply other threads:[~2022-08-10 23:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 17:58 [PATCH 0/3] KVM: selftests: Randomize memory access of dirty_log_perf_test Colton Lewis
2022-08-10 17:58 ` [PATCH 1/3] KVM: selftests: Add random table to randomize memory access Colton Lewis
2022-08-10 23:18 ` David Matlack
2022-08-10 23:26 ` David Matlack
2022-08-12 16:09 ` Colton Lewis
2022-08-10 17:58 ` [PATCH 2/3] KVM: selftests: Randomize which pages are written vs read Colton Lewis
2022-08-10 23:33 ` David Matlack [this message]
2022-08-10 23:37 ` David Matlack
2022-08-12 16:11 ` Colton Lewis
2022-08-10 17:58 ` [PATCH 3/3] KVM: selftests: Randomize page access order Colton Lewis
2022-08-10 23:49 ` David Matlack
2022-08-12 16:24 ` Colton Lewis
2022-08-12 16:28 ` David Matlack
2022-08-12 16:40 ` Colton Lewis
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=YvRAWKGXbPzool6j@google.com \
--to=dmatlack@google.com \
--cc=coltonlewis@google.com \
--cc=kvm@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=ricarkol@google.com \
--cc=seanjc@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.