From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, peterz@infradead.org, mingo@redhat.com,
mark.rutland@arm.com, jolsa@kernel.org, namhyung@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
kaleshsingh@google.com, ardb@kernel.org,
chenqiwu <qiwuchen55@gmail.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
alexander.shishkin@linux.intel.com,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org,
chenqiwu <qiwu.chen@transsion.com>
Subject: Re: [RESEND v3] arm64: Add USER_STACKTRACE support
Date: Fri, 3 May 2024 18:32:58 +0100 [thread overview]
Message-ID: <171474196646.3291931.10296754669267003473.b4-ty@kernel.org> (raw)
In-Reply-To: <20231219022229.10230-1-qiwu.chen@transsion.com>
On Tue, 19 Dec 2023 10:22:29 +0800, chenqiwu wrote:
> Currently, userstacktrace is unsupported for ftrace and uprobe
> tracers on arm64. This patch uses the perf_callchain_user() code
> as blueprint to implement the arch_stack_walk_user() which add
> userstacktrace support on arm64.
> Meanwhile, we can use arch_stack_walk_user() to simplify the
> implementation of perf_callchain_user().
> This patch is tested pass with ftrace, uprobe and perf tracers
> profiling userstacktrace cases.
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] arm64: Add USER_STACKTRACE support
https://git.kernel.org/will/c/410e471f8746
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2024-05-03 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 2:22 [RESEND v3] arm64: Add USER_STACKTRACE support chenqiwu
2024-04-19 13:09 ` Will Deacon
2024-04-24 14:11 ` chenqiwu
2024-05-03 13:08 ` Will Deacon
2024-05-03 17:32 ` Will Deacon [this message]
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=171474196646.3291931.10296754669267003473.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kaleshsingh@google.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.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 \
--cc=qiwu.chen@transsion.com \
--cc=qiwuchen55@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).