[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1439758168-29427-1-git-send-email-msalter@redhat.com>
Date: Sun, 16 Aug 2015 16:49:25 -0400
From: Mark Salter <msalter@...hat.com>
To: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>, x86@...nel.org
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Mark Rutland <mark.rutland@....com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mm@...ck.org, linux-arch@...r.kernel.org,
Mark Salter <msalter@...hat.com>
Subject: [PATCH V3 0/3] mm: Add generic copy from early unmapped RAM
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 and x86 share it in their
respective initrd relocation code.
Changes from V2:
* Fixed sparse warning in copy_from_early_mem()
* Removed unneeded MAX_MAP_CHUNK from x86 setup.c
* Moved #ifdef outside arm64 relocate_initrd() definition.
Changes from V1:
* Change cover letter subject to highlight the added generic code
* Add patch for x86 to use common copy_from_early_mem()
Mark Salter (3):
mm: add utility for early copy from unmapped ram
arm64: support initrd outside kernel linear map
x86: use generic early mem copy
arch/arm64/kernel/setup.c | 59 +++++++++++++++++++++++++++++++++++++
arch/x86/kernel/setup.c | 22 +-------------
include/asm-generic/early_ioremap.h | 6 ++++
mm/early_ioremap.c | 22 ++++++++++++++
4 files changed, 88 insertions(+), 21 deletions(-)
--
2.4.3
--
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