From: James Clark <james.clark@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
german.gomez@arm.com, John Garry <john.garry@huawei.com>,
Will Deacon <will@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Leo Yan <leo.yan@linaro.org>, Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v1 1/6] perf: arm64: Add SVE vector granule register to user regs
Date: Tue, 10 May 2022 10:34:45 +0100 [thread overview]
Message-ID: <34e48640-24a1-eaa2-e873-f7137aa47ba3@arm.com> (raw)
In-Reply-To: <Ynk3vTtJApO13peb@sirena.org.uk>
On 09/05/2022 16:48, Mark Brown wrote:
> On Mon, May 09, 2022 at 03:42:49PM +0100, James Clark wrote:
>> Dwarf based unwinding in a function that pushes SVE registers onto
>> the stack requires the unwinder to know the length of the SVE register
>> to calculate the stack offsets correctly. This was added to the Arm
>> specific Dwarf spec as the VG pseudo register[1].
>>
>> Add the vector length at position 46 if it's requested by userspace and
>> SVE is supported. If it's not supported then fail to open the event.
>>
>> The vector length must be on each sample because it can be changed
>> at runtime via a prctl or ptrace call. Also by adding it as a register
>> rather than a separate attribute, minimal changes will be required in an
>> unwinder that already indexes into the register list.
>
>> +static u64 perf_ext_regs_value(int idx)
>> +{
>> + switch (idx) {
>> + case PERF_REG_ARM64_VG:
>> + if (WARN_ON_ONCE(!system_supports_sve()))
>> + return 0;
>
> These WARN_ON_ONCE()s seem a bit loud but I do see they are idiomatic
> for this code so
They should never ever be hit because the mask is validated when opening
the event so hopefully it's not an issue.
>
> Reviewed-by: Mark Brown <broonie@kernel.org>
Thanks Mark
next prev parent reply other threads:[~2022-05-10 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 14:42 [PATCH v1 0/6] perf: arm64: Support for Dwarf unwinding through SVE functions James Clark
2022-05-09 14:42 ` [PATCH v1 1/6] perf: arm64: Add SVE vector granule register to user regs James Clark
2022-05-09 15:48 ` Mark Brown
2022-05-10 9:34 ` James Clark [this message]
2022-05-09 14:42 ` [PATCH v1 2/6] arm64/sve: Add Perf extensions documentation James Clark
2022-05-09 15:45 ` Mark Brown
2022-05-09 14:42 ` [PATCH v1 3/6] perf tools: arm64: Copy perf_regs.h from the kernel James Clark
2022-05-09 14:42 ` [PATCH v1 4/6] perf tools: Use dynamic register set for Dwarf unwind James Clark
2022-05-26 15:44 ` Arnaldo Carvalho de Melo
2022-05-26 18:19 ` Arnaldo Carvalho de Melo
2022-05-27 6:18 ` Leo Yan
2022-05-27 16:08 ` Arnaldo Carvalho de Melo
2022-05-09 14:42 ` [PATCH v1 5/6] perf tools: arm64: Decouple Libunwind register names from Perf James Clark
2022-05-09 14:42 ` [PATCH v1 6/6] perf tools: arm64: Add support for VG register 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=34e48640-24a1-eaa2-e873-f7137aa47ba3@arm.com \
--to=james.clark@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=broonie@kernel.org \
--cc=german.gomez@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=namhyung@kernel.org \
--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).