From: James Clark <james.clark@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Add VG register attr test with kernel version and feature detection
Date: Tue, 13 Dec 2022 15:30:37 +0000 [thread overview]
Message-ID: <634087f2-1a7a-0f61-51e8-9e6068d59e9d@arm.com> (raw)
In-Reply-To: <Y5iRhKrIb5pXOaKk@kernel.org>
On 13/12/2022 14:51, Arnaldo Carvalho de Melo wrote:
> Em Tue, Dec 13, 2022 at 11:47:35AM +0000, James Clark escreveu:
>> I didn't get any feedback on the RFC version of this that I posted a
>> while back [1]. I'd still like to add the test, especially now that
>> 6.1 has been released with this new feature, so I've rebased it onto
>> perf/core and double checked that it's still working.
>>
>> Applies to perf/core (0c3852adae83)
>
> I'm applying this locally, would this be testable on a Firefly (roc-rk3399-pc):
Thanks Arnaldo. It doesn't look like rk3399 has SVE, so
test-record-user-regs-no-sve-aarch64 will run to check that the kernel
won't give you the new register. So I suppose the answer to the question
is partially.
For test-record-user-regs-sve-aarch64, I've been running it on a
Graviton 3 on AWS which has SVE:
ubuntu@ip-10-252-130-213:~/linux$ head /proc/cpuinfo
processor : 0
BogoMIPS : 2100.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp
asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp
sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm
svebf16 i8mm bf16 dgh rng
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x1
CPU part : 0xd40
CPU revision : 1
processor : 1
>
> acme@roc-rk3399-pc:~$ head /proc/cpuinfo
> processor : 0
> BogoMIPS : 48.00
> Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
> CPU implementer : 0x41
> CPU architecture: 8
> CPU variant : 0x0
> CPU part : 0xd03
> CPU revision : 4
>
> processor : 1
> acme@roc-rk3399-pc:~$
>
> - Arnaldo
>
>> Thanks
>> James
>>
>> [1]: https://lore.kernel.org/bpf/20220927154104.869029-1-james.clark@arm.com/
>>
>> James Clark (4):
>> perf test: Add ability to test exit code for attr tests
>> perf test: Add mechanism for skipping attr tests on auxiliary vector
>> values
>> perf test: Add mechanism for skipping attr tests on kernel versions
>> perf test arm64: Add attr tests for new VG register
>>
>> tools/perf/tests/attr.py | 71 +++++++++++++++++--
>> .../attr/test-record-user-regs-no-sve-aarch64 | 9 +++
>> .../test-record-user-regs-old-sve-aarch64 | 10 +++
>> .../attr/test-record-user-regs-sve-aarch64 | 14 ++++
>> 4 files changed, 99 insertions(+), 5 deletions(-)
>> create mode 100644 tools/perf/tests/attr/test-record-user-regs-no-sve-aarch64
>> create mode 100644 tools/perf/tests/attr/test-record-user-regs-old-sve-aarch64
>> create mode 100644 tools/perf/tests/attr/test-record-user-regs-sve-aarch64
>>
>> --
>> 2.25.1
>
next prev parent reply other threads:[~2022-12-13 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 11:47 [PATCH v2 0/4] Add VG register attr test with kernel version and feature detection James Clark
2022-12-13 11:47 ` [PATCH v2 1/4] perf test: Add ability to test exit code for attr tests James Clark
2022-12-13 11:47 ` [PATCH v2 2/4] perf test: Add mechanism for skipping attr tests on auxiliary vector values James Clark
2022-12-13 11:47 ` [PATCH v2 3/4] perf test: Add mechanism for skipping attr tests on kernel versions James Clark
2022-12-13 11:47 ` [PATCH v2 4/4] perf test arm64: Add attr tests for new VG register James Clark
2022-12-13 14:51 ` [PATCH v2 0/4] Add VG register attr test with kernel version and feature detection Arnaldo Carvalho de Melo
2022-12-13 15:30 ` James Clark [this message]
2022-12-14 14:38 ` Arnaldo Carvalho de Melo
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=634087f2-1a7a-0f61-51e8-9e6068d59e9d@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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