From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, rostedt@goodmis.org,
mhiramat@kernel.org, mark.rutland@arm.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, bjorn@rivosinc.com, andy.chiu@sifive.com,
puranjay12@gmail.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, conor.dooley@microchip.com
Subject: Re: [PATCH -fixes] riscv: patch: Flush the icache right after patching to avoid illegal insns
Date: Thu, 27 Jun 2024 17:50:44 +0000 [thread overview]
Message-ID: <171951064458.6762.1867426653510240080.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240624082141.153871-1-alexghiti@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 24 Jun 2024 10:21:41 +0200 you wrote:
> We cannot delay the icache flush after patching some functions as we may
> have patched a function that will get called before the icache flush.
>
> The only way to completely avoid such scenario is by flushing the icache
> as soon as we patch a function. This will probably be costly as we don't
> batch the icache maintenance anymore.
>
> [...]
Here is the summary with links:
- [-fixes] riscv: patch: Flush the icache right after patching to avoid illegal insns
https://git.kernel.org/riscv/c/edf2d546bfd6
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-06-27 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 8:21 [PATCH -fixes] riscv: patch: Flush the icache right after patching to avoid illegal insns Alexandre Ghiti
2024-06-24 11:49 ` Andy Chiu
2024-06-25 2:38 ` Andy Chiu
2024-06-26 12:59 ` Conor Dooley
2024-06-27 17:47 ` Palmer Dabbelt
2024-06-27 17:50 ` patchwork-bot+linux-riscv [this message]
2024-07-09 8:13 ` Geert Uytterhoeven
2024-07-15 8:12 ` 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=171951064458.6762.1867426653510240080.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=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=paul.walmsley@sifive.com \
--cc=puranjay12@gmail.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;
as well as URLs for NNTP newsgroup(s).