From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, alex@ghiti.fr, bjorn@rivosinc.com,
cyrevolt@googlemail.com, lizhengyu3@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH fixes] riscv/purgatory: 4B align purgatory_start
Date: Thu, 03 Apr 2025 16:20:34 +0000 [thread overview]
Message-ID: <174369723499.2563936.2453990084533442499.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250328085313.1193815-1-bjorn@kernel.org>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:
On Fri, 28 Mar 2025 09:53:11 +0100 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> When a crashkernel is launched on RISC-V, the entry to purgatory is
> done by trapping via the stvec CSR. From riscv_kexec_norelocate():
>
> | ...
> | /*
> | * Switch to physical addressing
> | * This will also trigger a jump to CSR_STVEC
> | * which in this case is the address of the new
> | * kernel.
> | */
> | csrw CSR_STVEC, a2
> | csrw CSR_SATP, zero
>
> [...]
Here is the summary with links:
- [fixes] riscv/purgatory: 4B align purgatory_start
https://git.kernel.org/riscv/c/3f7023171df4
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:[~2025-04-03 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 8:53 [PATCH fixes] riscv/purgatory: 4B align purgatory_start Björn Töpel
2025-03-28 12:54 ` Alexandre Ghiti
2025-04-03 16:20 ` 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=174369723499.2563936.2453990084533442499.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=alex@ghiti.fr \
--cc=bjorn@rivosinc.com \
--cc=cyrevolt@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lizhengyu3@huawei.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@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