From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
Ricardo Koller <ricarkol@google.com>,
David Matlack <dmatlack@google.com>,
kvmarm@lists.linux.dev, Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH 0/2] KVM: selftests: Enable access_tracking_perf_test for arm64
Date: Fri, 11 Nov 2022 23:19:44 +0000 [thread overview]
Message-ID: <20221111231946.944807-1-oliver.upton@linux.dev> (raw)
Message-ID: <20221111231944.kPfNXtdM--vgDNiWuK_JIxb60rI0haZTIg6p1xxsrZk@z> (raw)
Small series to add support for arm64 to access_tracking_perf_test.
Well, really this corrects a bug that is benign on x86, but you get the
point.
Tested on an Ampere Altra system w/ all supported guest modes for that
platform.
Oliver Upton (2):
KVM: selftests: Allow >1 guest mode in access_tracking_perf_test
KVM: selftests: Build access_tracking_perf_test for arm64
tools/testing/selftests/kvm/Makefile | 1 +
tools/testing/selftests/kvm/access_tracking_perf_test.c | 3 +++
2 files changed, 4 insertions(+)
base-commit: 30a0b95b1335e12efef89dd78518ed3e4a71a763
--
2.38.1.431.g37b22c650d-goog
next reply other threads:[~2022-11-11 23:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 23:19 Oliver Upton [this message]
2022-11-11 23:19 ` [PATCH 0/2] KVM: selftests: Enable access_tracking_perf_test for arm64 Oliver Upton
2022-11-11 23:19 ` [PATCH 1/2] KVM: selftests: Allow >1 guest mode in access_tracking_perf_test Oliver Upton
2022-11-11 23:19 ` Oliver Upton
2022-11-12 10:03 ` Gavin Shan
2022-11-12 10:03 ` Gavin Shan
2022-11-14 17:12 ` Sean Christopherson
2022-11-14 17:12 ` Sean Christopherson
2022-11-14 21:57 ` Oliver Upton
2022-11-14 21:57 ` Oliver Upton
2022-11-11 23:19 ` [PATCH 2/2] KVM: selftests: Build access_tracking_perf_test for arm64 Oliver Upton
2022-11-11 23:19 ` Oliver Upton
2022-11-12 10:04 ` Gavin Shan
2022-11-12 10:04 ` Gavin Shan
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=20221111231946.944807-1-oliver.upton@linux.dev \
--to=oliver.upton@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=dmatlack@google.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--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).