From: John Garry <john.g.garry@oracle.com>
To: James Clark <james.clark@arm.com>,
linux-perf-users@vger.kernel.org, irogers@google.com,
renyu.zj@linux.alibaba.com
Cc: Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
Leo Yan <leo.yan@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Kajol Jain <kjain@linux.ibm.com>,
Nick Forrington <nick.forrington@arm.com>,
Kan Liang <kan.liang@linux.intel.com>,
Eduard Zingerman <eddyz87@gmail.com>,
Sohom Datta <sohomdatta1@gmail.com>,
Rob Herring <robh@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org
Subject: Re: [PATCH v5 3/6] perf test: Add a test for the new Arm CPU ID comparison behavior
Date: Wed, 16 Aug 2023 11:27:27 +0100 [thread overview]
Message-ID: <ff8f7055-70c6-169c-1242-25e6c56f87db@oracle.com> (raw)
In-Reply-To: <fc71f840-8c4e-eeac-580b-5e0065a4cbee@arm.com>
On 16/08/2023 10:14, James Clark wrote:
>
>
> On 15/08/2023 10:47, John Garry wrote:
>> On 11/08/2023 15:39, James Clark wrote:
>>> Now that variant and revision fields are taken into account the behavior
>>> is slightly more complicated so add a test to ensure that this behaves
>>> as expected.
>>>
>>> Signed-off-by: James Clark <james.clark@arm.com>
>>> ---
>>> tools/perf/arch/arm64/include/arch-tests.h | 3 ++
>>> tools/perf/arch/arm64/tests/Build | 1 +
>>> tools/perf/arch/arm64/tests/arch-tests.c | 4 +++
>>> tools/perf/arch/arm64/tests/cpuid-match.c | 38 ++++++++++++++++++++++
>>> 4 files changed, 46 insertions(+)
>>> create mode 100644 tools/perf/arch/arm64/tests/cpuid-match.c
>>>
>>> diff --git a/tools/perf/arch/arm64/include/arch-tests.h
>>> b/tools/perf/arch/arm64/include/arch-tests.h
>>> index 452b3d904521..474d7cf5afbd 100644
>>> --- a/tools/perf/arch/arm64/include/arch-tests.h
>>> +++ b/tools/perf/arch/arm64/include/arch-tests.h
>>> @@ -2,6 +2,9 @@
>>> #ifndef ARCH_TESTS_H
>>> #define ARCH_TESTS_H
>>> +struct test_suite;
>>> +
>>> +int test__cpuid_match(struct test_suite *test, int subtest);
>>> extern struct test_suite *arch_tests[];
>>> #endif
>>> diff --git a/tools/perf/arch/arm64/tests/Build
>>> b/tools/perf/arch/arm64/tests/Build
>>> index a61c06bdb757..e337c09e7f56 100644
>>> --- a/tools/perf/arch/arm64/tests/Build
>>> +++ b/tools/perf/arch/arm64/tests/Build
>>> @@ -2,3 +2,4 @@ perf-y += regs_load.o
>>> perf-$(CONFIG_DWARF_UNWIND) += dwarf-unwind.o
>>> perf-y += arch-tests.o
>>> +perf-y += cpuid-match.o
>>> diff --git a/tools/perf/arch/arm64/tests/arch-tests.c
>>> b/tools/perf/arch/arm64/tests/arch-tests.c
>>> index ad16b4f8f63e..74932e72c727 100644
>>> --- a/tools/perf/arch/arm64/tests/arch-tests.c
>>> +++ b/tools/perf/arch/arm64/tests/arch-tests.c
>>> @@ -3,9 +3,13 @@
>>> #include "tests/tests.h"
>>> #include "arch-tests.h"
>>> +
>>> +DEFINE_SUITE("arm64 CPUID matching", cpuid_match);
>>> +
>>> struct test_suite *arch_tests[] = {
>>> #ifdef HAVE_DWARF_UNWIND_SUPPORT
>>> &suite__dwarf_unwind,
>>> #endif
>>> + &suite__cpuid_match,
>>> NULL,
>>> };
>>> diff --git a/tools/perf/arch/arm64/tests/cpuid-match.c
>>> b/tools/perf/arch/arm64/tests/cpuid-match.c
>>> new file mode 100644
>>> index 000000000000..af0871b54ae7
>>> --- /dev/null
>>> +++ b/tools/perf/arch/arm64/tests/cpuid-match.c
>>> @@ -0,0 +1,38 @@
>>> +// SPDX-License-Identifier: GPL-2.0
>>> +#include <linux/compiler.h>
>>> +
>>> +#include "arch-tests.h"
>>> +#include "tests/tests.h"
>>> +#include "util/header.h"
>>> +
>>> +int test__cpuid_match(struct test_suite *test __maybe_unused,
>>> + int subtest __maybe_unused)
>>> +{
>>> + /* midr with no leading zeros matches */
>>> + if (strcmp_cpuid_str("0x410fd0c0", "0x00000000410fd0c0"))
>>> + return -1;
>>> + /* Upper case matches */
>>> + if (strcmp_cpuid_str("0x410fd0c0", "0x00000000410FD0C0"))
>>> + return -1;
>>> + /* r0p0 = r0p0 matches */
>>> + if (strcmp_cpuid_str("0x00000000410fd480", "0x00000000410fd480"))
>>> + return -1;
>>> + /* r0p1 > r0p0 matches */
>>> + if (strcmp_cpuid_str("0x00000000410fd480", "0x00000000410fd481"))
>>> + return -1;
>>> + /* r1p0 > r0p0 matches*/
>>> + if (strcmp_cpuid_str("0x00000000410fd480", "0x00000000411fd480"))
>>> + return -1;
>>> + /* r0p0 < r0p1 doesn't match */
>>> + if (!strcmp_cpuid_str("0x00000000410fd481", "0x00000000410fd480"))
>>> + return -1;
>>> + /* r0p0 < r1p0 doesn't match */
>>> + if (!strcmp_cpuid_str("0x00000000411fd480", "0x00000000410fd480"))
>>> + return -1;
>>> + /* Different CPU doesn't match */
>>> + if (!strcmp_cpuid_str("0x00000000410fd4c0", "0x00000000430f0af0"))
>>> + return -1;
>>> +
>>> + return 0;
>>> +}
>>> +
>>
>> Would it be possible to put this in core test code, since x86 also
>> supports strcmp_cpuid_str()?
>>
>
> That's how I started, but Ian suggested to move it to an arch specific
> folder because that's what it was testing.
>
Yeah, I see that comment now.
> We could still add test__cpuid_match() in the x86 folder rather than
> adding it with #ifdefs
I was thinking to make cpuid_match_array[] exposed by the arch code and
have a "weak", i.e. version for other archs.
, but I don't think it needs to be done here
> because I haven't touched the x86 code.
For the moment, I don't feel too strongly about this and it can be done
as a follow-up
Reviewed-by: John Garry <john.g.garry@oracle.com>
>
>> Maybe we would have an structure per arch of cpuids and expected
>> results, like
>>
>> struct cpuid_match {
>> char *cpuid1;
>> char *cpuid1;
>> int expected_result;
>> };
>>
>>
>> #ifdef ARM64
>> cpuid_match_array[] = {
>> {"0x410fd0c0", "0x00000000410FD0C0", -1},
>> {"0x00000000410fd480", "0x00000000410fd480", -1},
>> ...
>> {} /* sentinel */
>>
>> };
>> #else if defined(X86)
>> cpuid_match_array[] = {
>> {....}
>> ...
>> {} /* sentinel */
>>
>> };
>> #else
>> /* no support */
>> #endif
>>
>> Thanks,
>> John
next prev parent reply other threads:[~2023-08-16 10:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 14:39 [PATCH v5 0/6] perf vendor events arm64: Update N2 and V2 metrics and events using Arm telemetry repo James Clark
2023-08-11 14:39 ` [PATCH v5 1/6] perf: cs-etm: Don't duplicate FIELD_GET() James Clark
2023-08-15 18:09 ` Arnaldo Carvalho de Melo
2023-08-11 14:39 ` [PATCH v5 2/6] perf arm64: Allow version comparisons of CPU IDs James Clark
2023-08-14 13:07 ` John Garry
2023-08-14 14:15 ` James Clark
2023-08-14 14:43 ` John Garry
2023-08-16 9:02 ` James Clark
2023-08-15 9:35 ` John Garry
2023-08-16 9:12 ` James Clark
2023-08-16 10:15 ` John Garry
2023-08-11 14:39 ` [PATCH v5 3/6] perf test: Add a test for the new Arm CPU ID comparison behavior James Clark
2023-08-15 9:47 ` John Garry
2023-08-16 9:14 ` James Clark
2023-08-16 10:27 ` John Garry [this message]
2023-08-11 14:39 ` [PATCH v5 4/6] perf vendor events arm64: Update scale units and descriptions of common topdown metrics James Clark
2023-08-11 14:53 ` John Garry
2023-08-15 18:11 ` Arnaldo Carvalho de Melo
2023-08-11 14:39 ` [PATCH v5 5/6] perf vendor events arm64: Update stall_slot workaround for N2 r0p3 James Clark
2023-08-14 13:02 ` John Garry
2023-08-14 13:44 ` James Clark
2023-08-15 9:40 ` John Garry
2023-08-16 9:16 ` James Clark
2023-08-11 14:39 ` [PATCH v5 6/6] perf vendor events arm64: Update N2 and V2 metrics and events using Arm telemetry repo James Clark
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=ff8f7055-70c6-169c-1242-25e6c56f87db@oracle.com \
--to=john.g.garry@oracle.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=eddyz87@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nick.forrington@arm.com \
--cc=peterz@infradead.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=robh@kernel.org \
--cc=sohomdatta1@gmail.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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).