[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <mhng-95082d33-c7f4-4d3e-9794-7e0534324218@palmerdabbelt-glaptop>
Date: Wed, 27 Oct 2021 16:09:05 -0700 (PDT)
From: Palmer Dabbelt <palmerdabbelt@...gle.com>
To: schwab@...ux-m68k.org
CC: alexandre.ghiti@...onical.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
Subject: Re: [PATCH] RISC-V: Make CONFIG_RELOCATABLE user selectable
On Wed, 27 Oct 2021 02:45:27 PDT (-0700), schwab@...ux-m68k.org wrote:
> 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.
Thanks, I forgot about that. I've added it, but this is still a bit in
flux so I'm not going to send a v2 right now (it's on top of Alex's
other patches and should probably be squashed in, anyway).
Powered by blists - more mailing lists