From: "Alex Bennée" <alex.bennee@linaro.org>
To: kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, christoffer.dall@arm.com,
maz@kernel.org, qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: [kvm-unit-tests RFC PATCH] arm64: split pmu tests into tcg/kvm variants
Date: Tue, 25 May 2021 18:42:21 +0100 [thread overview]
Message-ID: <20210525174221.16987-1-alex.bennee@linaro.org> (raw)
QEMU is able to give a counter for instructions retired under TCG but
you need to enable -icount for it to work. Split the tests into
kvm/tcg variants to support this.
[AJB: I wonder if the solution is to have a totally separate
unittests.cfg for TCG mode here?]
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
arm/unittests.cfg | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/arm/unittests.cfg b/arm/unittests.cfg
index adc1bbf..2c4cf41 100644
--- a/arm/unittests.cfg
+++ b/arm/unittests.cfg
@@ -66,24 +66,40 @@ file = pmu.flat
groups = pmu
extra_params = -append 'cycle-counter 0'
-[pmu-event-introspection]
+[pmu-event-introspection-kvm]
file = pmu.flat
groups = pmu
arch = arm64
+accel = kvm
extra_params = -append 'pmu-event-introspection'
+[pmu-event-introspection-tcg]
+file = pmu.flat
+groups = pmu
+arch = arm64
+accel = tcg
+extra_params = -append 'pmu-event-introspection' -icount shift=1
+
[pmu-event-counter-config]
file = pmu.flat
groups = pmu
arch = arm64
extra_params = -append 'pmu-event-counter-config'
-[pmu-basic-event-count]
+[pmu-basic-event-count-kvm]
file = pmu.flat
groups = pmu
arch = arm64
+accel = kvm
extra_params = -append 'pmu-basic-event-count'
+[pmu-basic-event-count-tcg]
+file = pmu.flat
+groups = pmu
+arch = arm64
+accel = tcg
+extra_params = -append 'pmu-basic-event-count' -icount shift=1
+
[pmu-mem-access]
file = pmu.flat
groups = pmu
--
2.20.1
reply other threads:[~2021-05-25 17:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210525174221.16987-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=christoffer.dall@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).