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, guoren@kernel.org,
heiko@sntech.de, philipp.tomsich@vrull.eu,
linux-kernel@vger.kernel.org, conor.dooley@microchip.com,
syzbot+cfbcb82adf6d7279fd35@syzkaller.appspotmail.com
Subject: Re: [PATCH -fixes v2] riscv: Fix RISCV_ALTERNATIVE_EARLY
Date: Tue, 03 Sep 2024 19:10:33 +0000 [thread overview]
Message-ID: <172539063376.409367.11331685769005840751.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240829165048.49756-1-alexghiti@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 29 Aug 2024 18:50:48 +0200 you wrote:
> RISCV_ALTERNATIVE_EARLY will issue sbi_ecall() very early in the boot
> process, before the first memory mapping is setup so we can't have any
> instrumentation happening here.
>
> In addition, when the kernel is relocatable, we must also not issue any
> relocation this early since they would have been patched virtually only.
>
> [...]
Here is the summary with links:
- [-fixes,v2] riscv: Fix RISCV_ALTERNATIVE_EARLY
https://git.kernel.org/riscv/c/1ff95eb2bebd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-09-03 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 16:50 [PATCH -fixes v2] riscv: Fix RISCV_ALTERNATIVE_EARLY Alexandre Ghiti
2024-09-03 19:10 ` 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=172539063376.409367.11331685769005840751.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=philipp.tomsich@vrull.eu \
--cc=syzbot+cfbcb82adf6d7279fd35@syzkaller.appspotmail.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