From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?Q2zDqW1lbnQgTMOpZ2VyIDxjbGVnZXJAcml2b3NpbmMuY29tPg==?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, linux-kernel@vger.kernel.org,
antonb@tenstorrent.com
Subject: Re: [PATCH] riscv: stacktrace: fix backtracing through exceptions
Date: Thu, 09 Jan 2025 16:16:47 +0000 [thread overview]
Message-ID: <173643940723.1375203.17763630478007232527.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241209155714.1239665-1-cleger@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 9 Dec 2024 16:57:12 +0100 you wrote:
> Prior to commit 5d5fc33ce58e ("riscv: Improve exception and system call
> latency"), backtrace through exception worked since ra was filled with
> ret_from_exception symbol address and the stacktrace code checked 'pc' to
> be equal to that symbol. Now that handle_exception uses regular 'call'
> instructions, this isn't working anymore and backtrace stops at
> handle_exception(). Since there are multiple call site to C code in the
> exception handling path, rather than checking multiple potential return
> addresses, add a new symbol at the end of exception handling and check pc
> to be in that range.
>
> [...]
Here is the summary with links:
- riscv: stacktrace: fix backtracing through exceptions
https://git.kernel.org/riscv/c/51356ce60e59
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-01-09 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 15:57 Clément Léger
2025-01-06 11:15 ` Alexandre Ghiti
2025-01-09 16:16 ` patchwork-bot+linux-riscv [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=173643940723.1375203.17763630478007232527.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc==?utf-8?b?Q2zDqW1lbnQgTMOpZ2VyIDxjbGVnZXJAcml2b3NpbmMuY29tPg==?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=antonb@tenstorrent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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
all inboxes | Powered by JetHome®