From: Ricardo Koller <ricarkol@google.com>
To: Oliver Upton <oupton@google.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
drjones@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
maciej.szmigiero@oracle.com, maz@kernel.org,
jingzhangos@google.com, pshier@google.com, rananta@google.com,
reijiw@google.com
Subject: Re: [PATCH 2/2] KVM: selftests: build the memslot tests for arm64
Date: Tue, 7 Sep 2021 10:42:01 -0700 [thread overview]
Message-ID: <YTekaQOHMzNxV8Bl@google.com> (raw)
In-Reply-To: <CAOQ_QshLu-EiLdPDY-d1dS3qvNjJBiN=B=a-W7_70Fdt=GbOcw@mail.gmail.com>
On Tue, Sep 07, 2021 at 09:39:12AM -0500, Oliver Upton wrote:
> Ricardo,
>
> On Fri, Sep 3, 2021 at 6:12 PM Ricardo Koller <ricarkol@google.com> wrote:
> >
> > Add memslot_perf_test and memslot_modification_stress_test to the list
> > of aarch64 selftests.
> >
> > Signed-off-by: Ricardo Koller <ricarkol@google.com>
>
> There isn't anything that prevents these tests from being used for
> s390x too right? Of course, we haven't anything to test on but just a
> thought.
Tbh I'm not sure. Will ask if somebody can try it in the cover letter
for v2.
Thanks,
Ricardo
>
> Besides Drew's comments:
>
> Reviewed-by: Oliver Upton <oupton@google.com>
prev parent reply other threads:[~2021-09-07 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 23:11 [PATCH 0/2] KVM: selftests: enable the memslot tests in ARM64 Ricardo Koller
2021-09-03 23:11 ` [PATCH 1/2] KVM: selftests: make memslot_perf_test arch independent Ricardo Koller
2021-09-06 6:50 ` Andrew Jones
2021-09-06 18:03 ` Maciej S. Szmigiero
2021-09-07 14:34 ` Oliver Upton
2021-09-03 23:11 ` [PATCH 2/2] KVM: selftests: build the memslot tests for arm64 Ricardo Koller
2021-09-06 6:52 ` Andrew Jones
2021-09-07 17:39 ` Ricardo Koller
2021-09-06 18:03 ` Maciej S. Szmigiero
2021-09-07 14:39 ` Oliver Upton
2021-09-07 17:42 ` Ricardo Koller [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=YTekaQOHMzNxV8Bl@google.com \
--to=ricarkol@google.com \
--cc=drjones@redhat.com \
--cc=jingzhangos@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maciej.szmigiero@oracle.com \
--cc=maz@kernel.org \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=pshier@google.com \
--cc=rananta@google.com \
--cc=reijiw@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).