All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: linux-riscv@lists.infradead.org, alexghiti@rivosinc.com,
	andy.chiu@sifive.com, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, rostedt@goodmis.org,
	mhiramat@kernel.org, mark.rutland@arm.com,
	samitolvanen@google.com, guoren@kernel.org,
	leyfoon.tan@starfivetech.com, debug@rivosinc.com,
	jeeheng.sia@starfivetech.com, suagrfillet@gmail.com,
	bjorn@rivosinc.com, cleger@rivosinc.com, viro@zeniv.linux.org.uk,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	puranjay12@gmail.com
Subject: Re: [PATCH] ftrace: riscv: move from REGS to ARGS
Date: Wed, 22 May 2024 23:51:47 +0000	[thread overview]
Message-ID: <171642190795.9409.3531878731027938184.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240405142453.4187-1-puranjay@kernel.org>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.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



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: linux-riscv@lists.infradead.org, alexghiti@rivosinc.com,
	andy.chiu@sifive.com, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, rostedt@goodmis.org,
	mhiramat@kernel.org, mark.rutland@arm.com,
	samitolvanen@google.com, guoren@kernel.org,
	leyfoon.tan@starfivetech.com, debug@rivosinc.com,
	jeeheng.sia@starfivetech.com, suagrfillet@gmail.com,
	bjorn@rivosinc.com, cleger@rivosinc.com, viro@zeniv.linux.org.uk,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	puranjay12@gmail.com
Subject: Re: [PATCH] ftrace: riscv: move from REGS to ARGS
Date: Wed, 22 May 2024 23:51:47 +0000	[thread overview]
Message-ID: <171642190795.9409.3531878731027938184.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240405142453.4187-1-puranjay@kernel.org>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.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



  parent reply	other threads:[~2024-05-22 23:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 14:24 [PATCH] ftrace: riscv: move from REGS to ARGS Puranjay Mohan
2024-04-05 14:24 ` Puranjay Mohan
2024-04-24  9:13 ` Björn Töpel
2024-04-24  9:13   ` Björn Töpel
2024-05-22 23:51 ` patchwork-bot+linux-riscv [this message]
2024-05-22 23:51   ` patchwork-bot+linux-riscv

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=171642190795.9409.3531878731027938184.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alexghiti@rivosinc.com \
    --cc=andy.chiu@sifive.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bjorn@rivosinc.com \
    --cc=cleger@rivosinc.com \
    --cc=debug@rivosinc.com \
    --cc=guoren@kernel.org \
    --cc=jeeheng.sia@starfivetech.com \
    --cc=leyfoon.tan@starfivetech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=puranjay12@gmail.com \
    --cc=puranjay@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=samitolvanen@google.com \
    --cc=suagrfillet@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.