From: patchwork-bot+linux-riscv@kernel.org
To: Andy Chiu <andybnac@gmail.com>
Cc: linux-riscv@lists.infradead.org, alexghiti@rivosinc.com,
palmer@dabbelt.com, andy.chiu@sifive.com, e.shatokhin@yadro.com,
nathan@kernel.org, bjorn@rivosinc.com, palmer@rivosinc.com,
puranjay@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, llvm@lists.linux.dev,
mark.rutland@arm.com, alex@ghiti.fr,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
justinstitt@google.com, puranjay12@gmail.com,
paul.walmsley@sifive.com, greentime.hu@sifive.com,
nick.hu@sifive.com, nylon.chen@sifive.com, eric.lin@sifive.com,
vicent.chen@sifive.com, zong.li@sifive.com,
yongxuan.wang@sifive.com, samuel.holland@sifive.com,
olivia.chu@sifive.com, c2232430@gmail.com
Subject: Re: [PATCH v4 01/12] riscv: ftrace: support fastcc in Clang for WITH_ARGS
Date: Mon, 02 Jun 2025 22:12:42 +0000 [thread overview]
Message-ID: <174890236299.925497.5731685320676689356.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250407180838.42877-1-andybnac@gmail.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:
On Tue, 8 Apr 2025 02:08:25 +0800 you wrote:
> From: Andy Chiu <andy.chiu@sifive.com>
>
> Some caller-saved registers which are not defined as function arguments
> in the ABI can still be passed as arguments when the kernel is compiled
> with Clang. As a result, we must save and restore those registers to
> prevent ftrace from clobbering them.
>
> [...]
Here is the summary with links:
- [v4,01/12] riscv: ftrace: support fastcc in Clang for WITH_ARGS
https://git.kernel.org/riscv/c/7cecf4f30c33
- [v4,02/12] riscv: ftrace factor out code defined by !WITH_ARG
https://git.kernel.org/riscv/c/2efa234f5e0c
- [v4,03/12] riscv: ftrace: align patchable functions to 4 Byte boundary
https://git.kernel.org/riscv/c/cced570c2c0c
- [v4,04/12] kernel: ftrace: export ftrace_sync_ipi
(no matching commit)
- [v4,05/12] riscv: ftrace: prepare ftrace for atomic code patching
(no matching commit)
- [v4,06/12] riscv: ftrace: do not use stop_machine to update code
(no matching commit)
- [v4,07/12] riscv: vector: Support calling schedule() for preemptible Vector
https://git.kernel.org/riscv/c/e2a8cbdbe932
- [v4,08/12] riscv: add a data fence for CMODX in the kernel mode
https://git.kernel.org/riscv/c/29b59e3bbb6e
- [v4,09/12] riscv: ftrace: support PREEMPT
https://git.kernel.org/riscv/c/f48ba55bb8a8
- [v4,10/12] riscv: Implement HAVE_DYNAMIC_FTRACE_WITH_CALL_OPS
(no matching commit)
- [v4,11/12] riscv: ftrace: support direct call using call_ops
https://git.kernel.org/riscv/c/7ef9ae7457c0
- [v4,12/12] riscv: Documentation: add a description about dynamic ftrace
https://git.kernel.org/riscv/c/0e07200b2af6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-06-02 22:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 18:08 [PATCH v4 01/12] riscv: ftrace: support fastcc in Clang for WITH_ARGS Andy Chiu
2025-04-07 18:08 ` [PATCH v4 02/12] riscv: ftrace factor out code defined by !WITH_ARG Andy Chiu
2025-04-07 18:08 ` [PATCH v4 03/12] riscv: ftrace: align patchable functions to 4 Byte boundary Andy Chiu
2025-04-07 18:08 ` [PATCH v4 04/12] kernel: ftrace: export ftrace_sync_ipi Andy Chiu
2025-04-08 22:31 ` kernel test robot
2025-04-23 8:13 ` Alexandre Ghiti
2025-04-07 18:08 ` [PATCH v4 05/12] riscv: ftrace: prepare ftrace for atomic code patching Andy Chiu
2025-04-11 13:15 ` Robbin Ehn
2025-04-23 8:22 ` Alexandre Ghiti
2025-05-05 14:06 ` Alexandre Ghiti
2025-05-07 14:18 ` Andy Chiu
2025-05-07 14:35 ` Alexandre Ghiti
2025-04-07 18:08 ` [PATCH v4 06/12] riscv: ftrace: do not use stop_machine to update code Andy Chiu
2025-04-07 18:08 ` [PATCH v4 07/12] riscv: vector: Support calling schedule() for preemptible Vector Andy Chiu
2025-04-07 18:08 ` [PATCH v4 08/12] riscv: add a data fence for CMODX in the kernel mode Andy Chiu
2025-04-07 18:08 ` [PATCH v4 09/12] riscv: ftrace: support PREEMPT Andy Chiu
2025-04-07 18:08 ` [PATCH v4 10/12] riscv: Implement HAVE_DYNAMIC_FTRACE_WITH_CALL_OPS Andy Chiu
2026-02-21 12:15 ` Conor Dooley
2026-02-23 15:18 ` Puranjay Mohan
2026-02-23 15:27 ` Conor Dooley
2026-02-23 15:41 ` Puranjay Mohan
2026-02-23 16:29 ` Conor Dooley
2026-02-23 17:36 ` Puranjay Mohan
2026-02-23 17:41 ` Conor Dooley
2025-04-07 18:08 ` [PATCH v4 11/12] riscv: ftrace: support direct call using call_ops Andy Chiu
2025-04-07 18:08 ` [PATCH v4 12/12] riscv: Documentation: add a description about dynamic ftrace Andy Chiu
2025-04-11 12:02 ` Robbin Ehn
2025-04-10 20:05 ` [PATCH v4 01/12] riscv: ftrace: support fastcc in Clang for WITH_ARGS Björn Töpel
2025-05-07 13:58 ` Andy Chiu
2025-06-02 22:12 ` 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=174890236299.925497.5731685320676689356.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=alexghiti@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=andybnac@gmail.com \
--cc=bjorn@rivosinc.com \
--cc=c2232430@gmail.com \
--cc=e.shatokhin@yadro.com \
--cc=eric.lin@sifive.com \
--cc=greentime.hu@sifive.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nick.hu@sifive.com \
--cc=nylon.chen@sifive.com \
--cc=olivia.chu@sifive.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=puranjay12@gmail.com \
--cc=puranjay@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=vicent.chen@sifive.com \
--cc=yongxuan.wang@sifive.com \
--cc=zong.li@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