From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Rutland Subject: Re: [PATCH 0/2] arm64: support initrd outside of mapped RAM Date: Wed, 29 Jul 2015 10:25:37 +0100 Message-ID: <20150729092536.GI15213@leverpostej> References: <1438093961-15536-1-git-send-email-msalter@redhat.com> <1438161638.3129.4.camel@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from foss.arm.com ([217.140.101.70]:35222 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752366AbbG2J0H (ORCPT ); Wed, 29 Jul 2015 05:26:07 -0400 Content-Disposition: inline In-Reply-To: <1438161638.3129.4.camel@linaro.org> Sender: linux-arch-owner@vger.kernel.org List-ID: To: "Jon Medhurst (Tixy)" Cc: "msalter@redhat.com" , Catalin Marinas , Will Deacon , "linux-arch@vger.kernel.org" , "Arnd Bergmann --cc=Ard Biesheuvel" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "linux-arm-kernel@lists.infradead.org" On Wed, Jul 29, 2015 at 10:20:38AM +0100, Jon Medhurst (Tixy) wrote: > On Tue, 2015-07-28 at 10:32 -0400, 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. > > Have we got a similar issue for the device-tree blob? Commit 61bd93ce801bb6df ("arm64: use fixmap region for permanent FDT mapping") [1] solved that for the DTB in v4.2-rc1. Mark. [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=61bd93ce801bb6df36eda257a9d2d16c02863cdd