kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ricardo Koller <ricarkol@google.com>
To: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu
Cc: drjones@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
	maciej.szmigiero@oracle.com, maz@kernel.org, oupton@google.com,
	jingzhangos@google.com, pshier@google.com, rananta@google.com,
	reijiw@google.com, Ricardo Koller <ricarkol@google.com>
Subject: [PATCH 0/2] KVM: selftests: enable the memslot tests in ARM64
Date: Fri,  3 Sep 2021 16:11:52 -0700	[thread overview]
Message-ID: <20210903231154.25091-1-ricarkol@google.com> (raw)

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).

Ricardo Koller (2):
  KVM: selftests: make memslot_perf_test arch independent
  KVM: selftests: build the memslot tests for arm64

 tools/testing/selftests/kvm/Makefile          |  2 +
 .../testing/selftests/kvm/memslot_perf_test.c | 56 +++++++++++--------
 2 files changed, 36 insertions(+), 22 deletions(-)

-- 
2.33.0.153.gba50c8fa24-goog


             reply	other threads:[~2021-09-03 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 23:11 Ricardo Koller [this message]
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

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=20210903231154.25091-1-ricarkol@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).