From: Alexandru Elisei <alexandru.elisei@arm.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: pbonzini@redhat.com, drjones@redhat.com, thuth@redhat.com,
kvm@vger.kernel.org, qemu-arm@nongnu.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, christoffer.dall@arm.com,
maz@kernel.org, Anders Roxell <anders.roxell@linaro.org>,
Andrew Jones <andrew.jones@linux.dev>,
Eric Auger <eric.auger@redhat.com>,
"open list:ARM" <kvmarm@lists.linux.dev>
Subject: Re: [kvm-unit-tests PATCH v1 1/2] arm/pmu: skip the PMU introspection test if missing
Date: Tue, 9 Jul 2024 09:58:25 +0100 [thread overview]
Message-ID: <Zoz7sQNoC9ePXH7w@arm.com> (raw)
In-Reply-To: <20240702163515.1964784-2-alex.bennee@linaro.org>
Hi,
On Tue, Jul 02, 2024 at 05:35:14PM +0100, Alex Bennée wrote:
> The test for number of events is not a substitute for properly
> checking the feature register. Fix the define and skip if PMUv3 is not
> available on the system. This includes emulator such as QEMU which
> don't implement PMU counters as a matter of policy.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Anders Roxell <anders.roxell@linaro.org>
> ---
> arm/pmu.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/arm/pmu.c b/arm/pmu.c
> index 9ff7a301..66163a40 100644
> --- a/arm/pmu.c
> +++ b/arm/pmu.c
> @@ -200,7 +200,7 @@ static void test_overflow_interrupt(bool overflow_at_64bits) {}
> #define ID_AA64DFR0_PERFMON_MASK 0xf
>
> #define ID_DFR0_PMU_NOTIMPL 0b0000
> -#define ID_DFR0_PMU_V3 0b0001
> +#define ID_DFR0_PMU_V3 0b0011
> #define ID_DFR0_PMU_V3_8_1 0b0100
> #define ID_DFR0_PMU_V3_8_4 0b0101
> #define ID_DFR0_PMU_V3_8_5 0b0110
> @@ -286,6 +286,11 @@ static void test_event_introspection(void)
> return;
> }
>
> + if (pmu.version < ID_DFR0_PMU_V3) {
> + report_skip("PMUv3 extensions not supported, skip ...");
> + return;
> + }
> +
I don't get this patch - test_event_introspection() is only run on 64bit. On
arm64, if there is a PMU present, that PMU is a PMUv3. A prerequisite to
running any PMU tests is for pmu_probe() to succeed, and pmu_probe() fails if
there is no PMU implemented (PMUVer is either 0, or 0b1111). As a result, if
test_event_introspection() is executed, then a PMUv3 is present.
When does QEMU advertise FEAT_PMUv3*, but no event counters (other than the cycle
counter)?
If you want to be extra correct, you can add the above check to pmu_probe() for
32bit, since I doubt that the PMU tests were designed or tested on anything
other than a PMUv3 (and probably not much interest to maintain the tests for
PMUv1 or v2 either). If do do this, may I suggest:
#if defined(__arm__)
if (pmu.version == ID_DFR0_PMU_V1 || pmu.version == ID_DFR0_PMU_V2)
return false;
#endif
That way the check is self documenting.
Thanks,
Alex
> /* PMUv3 requires an implementation includes some common events */
> required_events = is_event_supported(SW_INCR, true) &&
> is_event_supported(CPU_CYCLES, true) &&
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-07-09 8:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 16:35 [kvm-unit-tests PATCH v1 0/2] Some fixes for running under -cpu max on QEMU Alex Bennée
2024-07-02 16:35 ` [kvm-unit-tests PATCH v1 1/2] arm/pmu: skip the PMU introspection test if missing Alex Bennée
2024-07-03 7:09 ` Zenghui Yu
2024-07-03 7:23 ` Marc Zyngier
2024-07-04 10:32 ` Alex Bennée
2024-07-09 8:58 ` Alexandru Elisei [this message]
2024-07-09 9:33 ` Peter Maydell
2024-07-09 14:05 ` Alex Bennée
2024-07-09 15:05 ` Alexandru Elisei
2024-07-09 17:18 ` Eric Auger
2024-07-02 16:35 ` [kvm-unit-tests PATCH v1 2/2] arm/mmu: widen the page size check to account for LPA2 Alex Bennée
2024-07-03 3:52 ` Zenghui Yu
2024-07-03 13:34 ` Andrew Jones
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=Zoz7sQNoC9ePXH7w@arm.com \
--to=alexandru.elisei@arm.com \
--cc=alex.bennee@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=andrew.jones@linux.dev \
--cc=christoffer.dall@arm.com \
--cc=drjones@redhat.com \
--cc=eric.auger@redhat.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=pbonzini@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=thuth@redhat.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).