From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: aou@eecs.berkeley.edu, linux-kbuild@vger.kernel.org,
ndesaulniers@google.com, linux-kernel@vger.kernel.org,
bjorn@kernel.org, palmer@dabbelt.com, npiggin@gmail.com,
paul.walmsley@sifive.com, linux-riscv@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v9 0/6] Introduce 64b relocatable kernel
Date: Thu, 20 Apr 2023 17:40:21 +0000 [thread overview]
Message-ID: <168201242185.9373.5416270250289201005.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230329045329.64565-1-alexghiti@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 29 Mar 2023 06:53:23 +0200 you wrote:
> After multiple attempts, this patchset is now based on the fact that the
> 64b kernel mapping was moved outside the linear mapping.
>
> The first patch allows to build relocatable kernels but is not selected
> by default. That patch is a requirement for KASLR.
> The second and third patches take advantage of an already existing powerpc
> script that checks relocations at compile-time, and uses it for riscv.
>
> [...]
Here is the summary with links:
- [v9,1/6] riscv: Prepare EFI header for relocatable kernels
https://git.kernel.org/riscv/c/55de1e4ad43b
- [v9,2/6] riscv: Move .rela.dyn outside of init to avoid empty relocations
https://git.kernel.org/riscv/c/69a90d2fe107
- [v9,3/6] riscv: Introduce CONFIG_RELOCATABLE
https://git.kernel.org/riscv/c/39b33072941f
- [v9,4/6] powerpc: Move script to check relocations at compile time in scripts/
https://git.kernel.org/riscv/c/47981b5cc687
- [v9,5/6] riscv: Check relocations at compile time
https://git.kernel.org/riscv/c/c2dea0bc5339
- [v9,6/6] riscv: Use --emit-relocs in order to move .rela.dyn in init
https://git.kernel.org/riscv/c/559d1e45a16d
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:[~2023-04-20 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 4:53 [PATCH v9 0/6] Introduce 64b relocatable kernel Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 1/6] riscv: Prepare EFI header for relocatable kernels Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 2/6] riscv: Move .rela.dyn outside of init to avoid empty relocations Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 3/6] riscv: Introduce CONFIG_RELOCATABLE Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 4/6] powerpc: Move script to check relocations at compile time in scripts/ Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 5/6] riscv: Check relocations at compile time Alexandre Ghiti
2023-03-29 4:53 ` [PATCH v9 6/6] riscv: Use --emit-relocs in order to move .rela.dyn in init Alexandre Ghiti
2023-04-19 14:56 ` [PATCH v9 0/6] Introduce 64b relocatable kernel Palmer Dabbelt
2023-04-20 17:40 ` patchwork-bot+linux-riscv [this message]
2023-04-21 18:59 ` Palmer Dabbelt
2023-04-21 19:10 ` Konstantin Ryabitsev
2023-04-21 19:24 ` Conor Dooley
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=168201242185.9373.5416270250289201005.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ndesaulniers@google.com \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).