From: Matthieu Baerts <matttbe@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Sasha Levin <sashal@kernel.org>
Cc: Carlos Llamas <cmllamas@google.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] decode_stacktrace: Support caller address decoding
Date: Thu, 5 Mar 2026 18:05:59 +0100 [thread overview]
Message-ID: <7f47295b-803b-4d17-900f-8e19f2931407@kernel.org> (raw)
In-Reply-To: <177272956276.1018623.6026552620206046640.stgit@mhiramat.tok.corp.google.com>
Hi Masami,
Thank you for the new version, and your previous reply!
On 05/03/2026 17:52, Masami Hiramatsu (Google) wrote:
> Add -c option to decodecall address instead of the return address.
> With this option, it decodes the line info 1byte before the return
> address which will be the call(branch) instruction address.
> If the return address is a symbol address, it falls back to
> decoding the return address.
From what I got from Sasha, this "addr-1" trick seems quite common. Why
not using this new feature by default, and having an option to disable it?
Or no option if someone can validate the new behaviour on architectures
which have these delay slots you mentioned?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-03-05 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 16:52 [PATCH v2] decode_stacktrace: Support caller address decoding Masami Hiramatsu (Google)
2026-03-05 17:05 ` Matthieu Baerts [this message]
2026-03-05 20:47 ` Sasha Levin
2026-03-06 0:31 ` Masami Hiramatsu
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=7f47295b-803b-4d17-900f-8e19f2931407@kernel.org \
--to=matttbe@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cmllamas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=mhiramat@kernel.org \
--cc=sashal@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