From: Andreas Schwab <schwab@linux-m68k.org>
To: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
alex@ghiti.fr, Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com,
Palmer Dabbelt <palmerdabbelt@google.com>
Subject: Re: [PATCH] RISC-V: Make CONFIG_RELOCATABLE user selectable
Date: Wed, 27 Oct 2021 11:45:27 +0200 [thread overview]
Message-ID: <87ee86ajig.fsf@igel.home> (raw)
In-Reply-To: <CA+zEjCuRuKtZAhkS_RFyby6UhLvYmg=4BdnXEwUdaCdtbB7ZAA@mail.gmail.com> (Alexandre Ghiti's message of "Wed, 27 Oct 2021 10:58:44 +0200")
On Okt 27 2021, Alexandre Ghiti wrote:
> On Wed, Oct 27, 2021 at 10:03 AM Andreas Schwab <schwab@linux-m68k.org> wrote:
>>
>> On Okt 26 2021, Palmer Dabbelt wrote:
>>
>> > +config RELOCATABLE
>> > + bool "Build a relocatable kernel"
>> > + depends on MMU && 64BIT && !XIP_KERNEL
>> > + help
>> > + This builds a kernel as a Position Independent Executable (PIE),
>> > + which retains all relocation metadata required to relocate the
>> > + kernel binary at runtime to a different virtual address than the
>> > + address it was linked at.
>> > + Since RISCV uses the RELA relocation format, this requires a
>> > + relocation pass at runtime even if the kernel is loaded at the
>> > + same address it was linked at.
>>
>> When in doubt, do what?
>
> Then do not enable.
Please add that to the help string.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-10-27 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 21:28 [PATCH] RISC-V: Make CONFIG_RELOCATABLE user selectable Palmer Dabbelt
2021-10-27 5:07 ` Alexandre ghiti
2021-10-27 8:00 ` Andreas Schwab
2021-10-27 8:58 ` Alexandre Ghiti
2021-10-27 9:45 ` Andreas Schwab [this message]
2021-10-27 23:09 ` Palmer Dabbelt
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=87ee86ajig.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=alex@ghiti.fr \
--cc=alexandre.ghiti@canonical.com \
--cc=aou@eecs.berkeley.edu \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.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