[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20151008094055.GC32532@n2100.arm.linux.org.uk>
Date: Thu, 8 Oct 2015 10:40:55 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: yalin wang <yalin.wang2010@...il.com>
Cc: Christoffer Dall <christoffer.dall@...aro.org>,
Mark Rutland <mark.rutland@....com>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Catalin Marinas <Catalin.Marinas@....com>,
"x86@...nel.org" <x86@...nel.org>,
Will Deacon <Will.Deacon@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Mark Salter <msalter@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH V4 2/3] arm64: support initrd outside kernel linear map
On Thu, Oct 08, 2015 at 05:18:14PM +0800, yalin wang wrote:
> is it also possible to implement it on ARM platforms?
> ARM64 platform don’t have HIGH_MEM zone .
> but ARM platform have .
> i remember boot loader must put init rd into low memory region,
> so if some boot loader put init rd into HIGH men zone
> we can also relocate it to low men region ?
> then boot loader don’t need care about this ,
> and since vmalloc= boot option will change HIGH mem region size,
> if we can relocate init rd , boot loader don’t need care about init rd load address,
> when change vmalloc= boot options .
I'd be more inclined to say yes if the kernel wasn't buggering around
passing virtual addresses (initrd_start) of the initrd image around,
but instead used a physical address. initrd_start must be a lowmem
address.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
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