From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: Colton Lewis <coltonlewis@google.com>,
kvm@vger.kernel.org, pbonzini@redhat.com, dmatlack@google.com,
seanjc@google.com, ricarkol@google.com
Subject: Re: [PATCH v10 0/4] randomize memory access of dirty_log_perf_test
Date: Wed, 30 Nov 2022 18:11:53 +0000 [thread overview]
Message-ID: <87mt88tiqe.wl-maz@kernel.org> (raw)
In-Reply-To: <Y4eY/Yjj+FP+vf7Y@google.com>
On Wed, 30 Nov 2022 17:55:09 +0000,
Oliver Upton <oliver.upton@linux.dev> wrote:
>
> On Mon, Nov 07, 2022 at 06:22:04PM +0000, 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.
> >
> > v10:
> >
> > Move setting default random seed to argument parsing code.
> >
> > 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
>
> Does someone want to pick this up for 6.2? Also, what tree are we
> routing these architecture-generic selftests changes through, Paolo's?
That's the usual route, but I can also take them if that makes
someone's life easier. Just let me know.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-11-30 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 18:22 [PATCH v10 0/4] randomize memory access of dirty_log_perf_test Colton Lewis
2022-11-07 18:22 ` [PATCH v10 1/4] KVM: selftests: implement random number generator for guest code Colton Lewis
2022-11-07 18:22 ` [PATCH v10 2/4] KVM: selftests: create -r argument to specify random seed Colton Lewis
2022-11-07 21:11 ` David Matlack
2022-11-07 18:22 ` [PATCH v10 3/4] KVM: selftests: randomize which pages are written vs read Colton Lewis
2022-11-07 18:22 ` [PATCH v10 4/4] KVM: selftests: randomize page access order Colton Lewis
2022-11-30 17:55 ` [PATCH v10 0/4] randomize memory access of dirty_log_perf_test Oliver Upton
2022-11-30 18:11 ` Marc Zyngier [this message]
2022-11-30 20:11 ` Sean Christopherson
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=87mt88tiqe.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=coltonlewis@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).