[RFC PATCH 0/3] arm64 initrd mapping/relocation

[Ard Biesheuvel]

On 3 February 2016 at 15:22, Mark Salter <msalter at redhat.com> wrote:
> On Tue, 2016-02-02 at 18:06 +0000, Will Deacon wrote:
>> On Tue, Feb 02, 2016 at 06:56:39PM +0100, Ard Biesheuvel wrote:
>> > After discussing in linux-efi with Mark, and on #armlinux with Will, this is
>> > a proposal for dealing with initrd memory that is potentially not covered by
>> > the linear region.
>> >
>> > Note that this will look slightly differently when some of the KASLR work gets
>> > merged, but this should only affect the way we deal with the initrd if it sits
>> > outside of the linear region.
>> >
>> > Mostly intended for discussion, not tested at all.
>>
>> Thanks Ard, this looks like a much better approach to me. Mark -- does
>> the general idea work for you too?
>>
>> Will
>
> Yeah, much simpler. I like it in concept but am I missing something or is it
> adding memory to the system beyond the mem= limit?

Indeed. I think it is reasonable to require that if you pass both mem=
and initrd= *and* you need your memory limit to be honored strictly,
it is up to you to ensure that the initrd does not live in the memory
you are throwing away.

> But even that may not be
> a big deal. And I need to look at the KASLR work and understand the issues
> with it and mem= if any. I'm traveling right now and can't really try it out
> until tomorrow...
>

No worries. My estimation is that Will is not going to take this as a
fix anyway, so we have plenty of time to test and/or discuss

Thanks,
Ard.