From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
Ricardo Koller <ricarkol@google.com>
Cc: pshier@google.com, Paolo Bonzini <pbonzini@redhat.com>,
maciej.szmigiero@oracle.com
Subject: Re: [PATCH v2 0/2] KVM: selftests: enable the memslot tests in ARM64
Date: Thu, 21 Oct 2021 13:47:28 +0100 [thread overview]
Message-ID: <163482044194.2203130.6587124513364503568.b4-ty@kernel.org> (raw)
In-Reply-To: <20210907180957.609966-1-ricarkol@google.com>
On Tue, 7 Sep 2021 11:09:55 -0700, Ricardo Koller wrote:
> Enable memslot_modification_stress_test and memslot_perf_test in ARM64
> (second patch). memslot_modification_stress_test builds and runs in
> aarch64 without any modification. memslot_perf_test needs some nits
> regarding ucalls (first patch).
>
> Can anybody try these two tests in s390, please?
>
> [...]
Applied to next, thanks!
[1/2] KVM: selftests: make memslot_perf_test arch independent
commit: ffb4ce3c49366f02f1c064fbe2e66a96ab5f98b8
[2/2] KVM: selftests: build the memslot tests for arm64
commit: 358928fd5264f069b9758f8b29297c7bff2a06de
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
prev parent reply other threads:[~2021-10-21 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 18:09 [PATCH v2 0/2] KVM: selftests: enable the memslot tests in ARM64 Ricardo Koller
2021-09-07 18:09 ` [PATCH v2 1/2] KVM: selftests: make memslot_perf_test arch independent Ricardo Koller
2021-09-07 18:18 ` Andrew Jones
2021-09-07 19:06 ` Oliver Upton
2021-09-07 18:09 ` [PATCH v2 2/2] KVM: selftests: build the memslot tests for arm64 Ricardo Koller
2021-09-07 18:18 ` Andrew Jones
2021-09-07 19:05 ` Oliver Upton
2021-09-07 18:17 ` [PATCH v2 0/2] KVM: selftests: enable the memslot tests in ARM64 Andrew Jones
2021-09-07 20:52 ` Ricardo Koller
2021-10-19 21:17 ` Ricardo Koller
2021-10-21 12:47 ` Marc Zyngier [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=163482044194.2203130.6587124513364503568.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maciej.szmigiero@oracle.com \
--cc=pbonzini@redhat.com \
--cc=pshier@google.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 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).