From: Mark Salter <msalter@redhat.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: "Arnd Bergmann <arnd@arndb.de>--cc=Ard Biesheuvel"
<ard.biesheuvel@linaro.org>, Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, Mark Salter <msalter@redhat.com>
Subject: [PATCH 0/2] arm64: support initrd outside of mapped RAM
Date: Tue, 28 Jul 2015 10:32:39 -0400 [thread overview]
Message-ID: <1438093961-15536-1-git-send-email-msalter@redhat.com> (raw)
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.
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(+)
--
2.4.3
WARNING: multiple messages have this Message-ID (diff)
From: msalter@redhat.com (Mark Salter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: support initrd outside of mapped RAM
Date: Tue, 28 Jul 2015 10:32:39 -0400 [thread overview]
Message-ID: <1438093961-15536-1-git-send-email-msalter@redhat.com> (raw)
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.
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(+)
--
2.4.3
WARNING: multiple messages have this Message-ID (diff)
From: Mark Salter <msalter@redhat.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: "Arnd Bergmann <arnd@arndb.de>--cc=Ard Biesheuvel"
<ard.biesheuvel@linaro.org>, Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, Mark Salter <msalter@redhat.com>
Subject: [PATCH 0/2] arm64: support initrd outside of mapped RAM
Date: Tue, 28 Jul 2015 10:32:39 -0400 [thread overview]
Message-ID: <1438093961-15536-1-git-send-email-msalter@redhat.com> (raw)
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.
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(+)
--
2.4.3
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2015-07-28 14:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 14:32 Mark Salter [this message]
2015-07-28 14:32 ` [PATCH 0/2] arm64: support initrd outside of mapped RAM Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:32 ` [PATCH 1/2] mm: add utility for early copy from unmapped ram Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:32 ` [PATCH 2/2] arm64: support initrd outside kernel linear map Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:32 ` Mark Salter
2015-07-28 14:59 ` [PATCH 0/2] arm64: support initrd outside of mapped RAM Mark Rutland
2015-07-28 14:59 ` Mark Rutland
2015-07-28 14:59 ` Mark Rutland
2015-07-28 15:07 ` Mark Salter
2015-07-28 15:07 ` Mark Salter
2015-07-28 15:07 ` Mark Salter
2015-07-28 15:14 ` Mark Rutland
2015-07-28 15:14 ` Mark Rutland
2015-07-28 15:14 ` Mark Rutland
2015-07-29 9:20 ` Jon Medhurst (Tixy)
2015-07-29 9:20 ` Jon Medhurst (Tixy)
2015-07-29 9:20 ` Jon Medhurst (Tixy)
2015-07-29 9:25 ` Mark Rutland
2015-07-29 9:25 ` Mark Rutland
2015-07-29 9:25 ` Mark Rutland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1438093961-15536-1-git-send-email-msalter@redhat.com \
--to=msalter@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.