[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<171642190795.9409.3531878731027938184.git-patchwork-notify@kernel.org>
Date: Wed, 22 May 2024 23:51:47 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Puranjay Mohan <puranjay@...nel.org>
Cc: linux-riscv@...ts.infradead.org, alexghiti@...osinc.com,
andy.chiu@...ive.com, paul.walmsley@...ive.com, palmer@...belt.com,
aou@...s.berkeley.edu, rostedt@...dmis.org, mhiramat@...nel.org,
mark.rutland@....com, samitolvanen@...gle.com, guoren@...nel.org,
leyfoon.tan@...rfivetech.com, debug@...osinc.com,
jeeheng.sia@...rfivetech.com, suagrfillet@...il.com, bjorn@...osinc.com,
cleger@...osinc.com, viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, puranjay12@...il.com
Subject: Re: [PATCH] ftrace: riscv: move from REGS to ARGS
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@...osinc.com>:
On Fri, 5 Apr 2024 14:24:53 +0000 you wrote:
> This commit replaces riscv's support for FTRACE_WITH_REGS with support
> for FTRACE_WITH_ARGS. This is required for the ongoing effort to stop
> relying on stop_machine() for RISCV's implementation of ftrace.
>
> The main relevant benefit that this change will bring for the above
> use-case is that now we don't have separate ftrace_caller and
> ftrace_regs_caller trampolines. This will allow the callsite to call
> ftrace_caller by modifying a single instruction. Now the callsite can
> do something similar to:
>
> [...]
Here is the summary with links:
- ftrace: riscv: move from REGS to ARGS
https://git.kernel.org/riscv/c/aa4cc1761cca
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists