[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ee86ajig.fsf@igel.home>
Date: Wed, 27 Oct 2021 11:45:27 +0200
From: Andreas Schwab <schwab@...ux-m68k.org>
To: Alexandre Ghiti <alexandre.ghiti@...onical.com>
Cc: Palmer Dabbelt <palmer@...belt.com>, alex@...ti.fr,
Paul Walmsley <paul.walmsley@...ive.com>,
aou@...s.berkeley.edu, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org, kernel-team@...roid.com,
Palmer Dabbelt <palmerdabbelt@...gle.com>
Subject: Re: [PATCH] RISC-V: Make CONFIG_RELOCATABLE user selectable
On Okt 27 2021, Alexandre Ghiti wrote:
> On Wed, Oct 27, 2021 at 10:03 AM Andreas Schwab <schwab@...ux-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@...ux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
Powered by blists - more mailing lists