From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, rostedt@goodmis.org,
mhiramat@kernel.org, mark.rutland@arm.com,
parri.andrea@gmail.com, bjorn@rivosinc.com,
conor.dooley@microchip.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Fix early ftrace nop patching
Date: Thu, 23 May 2024 18:00:33 +0000 [thread overview]
Message-ID: <171648723308.17418.17188308425434687140.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240523115134.70380-1-alexghiti@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 23 May 2024 13:51:34 +0200 you wrote:
> Commit c97bf629963e ("riscv: Fix text patching when IPI are used")
> converted ftrace_make_nop() to use patch_insn_write() which does not
> emit any icache flush relying entirely on __ftrace_modify_code() to do
> that.
>
> But we missed that ftrace_make_nop() was called very early directly when
> converting mcount calls into nops (actually on riscv it converts 2B nops
> emitted by the compiler into 4B nops).
>
> [...]
Here is the summary with links:
- riscv: Fix early ftrace nop patching
https://git.kernel.org/riscv/c/6ca445d8af0e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-05-23 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 11:51 [PATCH] riscv: Fix early ftrace nop patching Alexandre Ghiti
2024-05-23 12:48 ` Björn Töpel
2024-05-23 14:13 ` Conor Dooley
2024-05-23 18:00 ` patchwork-bot+linux-riscv [this message]
2024-06-13 7:48 ` Conor Dooley
2024-06-17 13:23 ` Alexandre Ghiti
2024-06-18 12:02 ` Alexandre Ghiti
2024-06-18 12:48 ` Andy Chiu
2024-06-18 13:39 ` Alexandre Ghiti
2024-06-19 3:40 ` Andy Chiu
2024-06-20 17:03 ` Alexandre Ghiti
2024-06-24 8:08 ` Alexandre Ghiti
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=171648723308.17418.17188308425434687140.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=conor.dooley@microchip.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=parri.andrea@gmail.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.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