From: "Alex Bennée" <alex.bennee@linaro.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Zenghui Yu <yuzenghui@huawei.com>,
pbonzini@redhat.com, thuth@redhat.com, kvm@vger.kernel.org,
qemu-arm@nongnu.org, linux-arm-kernel@lists.infradead.org,
christoffer.dall@arm.com,
Anders Roxell <anders.roxell@linaro.org>,
Andrew Jones <andrew.jones@linux.dev>,
Alexandru Elisei <alexandru.elisei@arm.com>,
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: Thu, 04 Jul 2024 11:32:23 +0100 [thread overview]
Message-ID: <87ed89o3bc.fsf@draig.linaro.org> (raw)
In-Reply-To: <74e184afbc4b58fba984b91964915a9e@kernel.org> (Marc Zyngier's message of "Wed, 03 Jul 2024 08:23:37 +0100")
Marc Zyngier <maz@kernel.org> writes:
> On 2024-07-03 08:09, Zenghui Yu wrote:
>> On 2024/7/3 0:35, 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
>> Why? This is a macro used for AArch64 and DDI0487J.a (D19.2.59, the
>> description of the PMUVer field) says that
>> "0b0001 Performance Monitors Extension, PMUv3 implemented."
>> while 0b0011 is a reserved value.
>
> I think this is a mix of 32bit and 64bit views (ID_DFR0_EL1.PerfMon
> instead of ID_AA64DFR0_EL1.PMUVer), and the whole thing is a mess
> (ID_AA64DFR0_PERFMON_MASK is clearly confused...).
>
> I haven't looked at how this patch fits in the rest of the code
> though.
Doh - yes different set of values for 32 bit.
>
> M.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2024-07-04 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240702163515.1964784-1-alex.bennee@linaro.org>
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 [this message]
2024-07-09 8:58 ` Alexandru Elisei
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=87ed89o3bc.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=alexandru.elisei@arm.com \
--cc=anders.roxell@linaro.org \
--cc=andrew.jones@linux.dev \
--cc=christoffer.dall@arm.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--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 \
--cc=yuzenghui@huawei.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