[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150728145906.GE15213@leverpostej>
Date: Tue, 28 Jul 2015 15:59:06 +0100
From: Mark Rutland <mark.rutland@....com>
To: Mark Salter <msalter@...hat.com>
Cc: Catalin Marinas <Catalin.Marinas@....com>,
Will Deacon <Will.Deacon@....com>,
Arnd Bergmann <arnd@...db.de>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>
Subject: Re: [PATCH 0/2] arm64: support initrd outside of mapped RAM
Hi Mark,
As a heads-up, it looks like you missed a space when sending this; Arnd
and Ard got merged into:
"Arnd Bergmann <arnd@...db.de>--cc=Ard Biesheuvel" <ard.biesheuvel@...aro.org>
I've corrected that for this reply.
On Tue, Jul 28, 2015 at 03:32:39PM +0100, Mark Salter wrote:
> When booting an arm64 kernel w/initrd using UEFI/grub, use of mem= will likely
> cut off part or all of the initrd. This leaves it outside the kernel linear
> map which leads to failure when unpacking. The x86 code has a similar need to
> relocate an initrd outside of mapped memory in some cases.
>
> The current x86 code uses early_memremap() to copy the original initrd from
> unmapped to mapped RAM. This patchset creates a generic copy_from_early_mem()
> utility based on that x86 code and has arm64 use it to relocate the initrd
> if necessary.
This sounds like a sane idea to me.
> Mark Salter (2):
> mm: add utility for early copy from unmapped ram
> arm64: support initrd outside kernel linear map
>
> arch/arm64/kernel/setup.c | 55 +++++++++++++++++++++++++++++++++++++
> include/asm-generic/early_ioremap.h | 6 ++++
> mm/early_ioremap.c | 22 +++++++++++++++
> 3 files changed, 83 insertions(+)
Any reason for not moving x86 over to the new generic version?
Mark.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists