From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
broonie@kernel.org, german.gomez@arm.com, leo.yan@linaro.org,
mathieu.poirier@linaro.org, john.garry@huawei.com,
Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.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-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] perf: arm64: Tools support for Dwarf unwinding through SVE functions
Date: Tue, 17 May 2022 11:58:38 -0300 [thread overview]
Message-ID: <YoO4Hiue7PmJ9KOS@kernel.org> (raw)
In-Reply-To: <20220517102005.3022017-1-james.clark@arm.com>
Em Tue, May 17, 2022 at 11:20:01AM +0100, James Clark escreveu:
> Changes since v1:
>
> * Split patchset into kernel side and Perf tool changes
Thanks, now I'll wait for the kernel side to be merged.
- Arnaldo
> When SVE registers are pushed onto the stack the VG register is required to
> unwind because the stack offsets would vary by the SVE register width at the
> time when the sample was taken.
>
> The patches ("[PATCH v2 0/2] perf: arm64: Kernel support for Dwarf unwinding
> through SVE functions") add support for sampling the VG register to the kernel
> and the docs. This is the patchset to add support to userspace perf.
>
> A small change is also required to libunwind or libdw depending on which
> unwinder is used, and these will be published later. Without these changes Perf
> continues to work with both libraries, although the VG register is still not
> used for unwinding.
>
> Thanks
> James
>
> James Clark (4):
> perf tools: arm64: Copy perf_regs.h from the kernel
> perf tools: Use dynamic register set for Dwarf unwind
> perf tools: arm64: Decouple Libunwind register names from Perf
> perf tools: arm64: Add support for VG register
>
> tools/arch/arm64/include/uapi/asm/perf_regs.h | 7 +-
> tools/perf/arch/arm64/util/perf_regs.c | 34 +++++++++
> tools/perf/arch/arm64/util/unwind-libunwind.c | 73 +------------------
> tools/perf/util/evsel.c | 2 +-
> tools/perf/util/perf_regs.c | 2 +
> 5 files changed, 45 insertions(+), 73 deletions(-)
>
> --
> 2.28.0
--
- Arnaldo
next prev parent reply other threads:[~2022-05-17 14:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 10:20 [PATCH v2 0/2] perf: arm64: Tools support for Dwarf unwinding through SVE functions James Clark
2022-05-17 10:20 ` [PATCH v2 1/4] perf tools: arm64: Copy perf_regs.h from the kernel James Clark
2022-05-17 10:50 ` Leo Yan
2022-05-17 10:20 ` [PATCH v2 2/4] perf tools: Use dynamic register set for Dwarf unwind James Clark
2022-05-17 11:03 ` Leo Yan
2022-05-18 13:25 ` James Clark
2022-05-18 14:00 ` Leo Yan
2022-05-17 10:20 ` [PATCH v2 3/4] perf tools: arm64: Decouple Libunwind register names from Perf James Clark
2022-05-17 12:54 ` Leo Yan
2022-05-17 10:20 ` [PATCH v2 4/4] perf tools: arm64: Add support for VG register James Clark
2022-05-17 13:19 ` Leo Yan
2022-05-18 9:44 ` James Clark
2022-05-18 9:57 ` Leo Yan
2022-05-17 14:58 ` Arnaldo Carvalho de Melo [this message]
2022-05-20 11:46 ` [PATCH v2 0/2] perf: arm64: Tools support for Dwarf unwinding through SVE functions German Gomez
2022-05-20 12:32 ` Arnaldo Carvalho de Melo
2022-05-20 14:52 ` 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=YoO4Hiue7PmJ9KOS@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=broonie@kernel.org \
--cc=german.gomez@arm.com \
--cc=james.clark@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-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).