[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131013184212.GA18075@htj.dyndns.org>
Date: Sun, 13 Oct 2013 14:42:12 -0400
From: Tejun Heo <tj@...nel.org>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Santosh Shilimkar <santosh.shilimkar@...com>,
grygorii.strashko@...com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
yinghai@...nel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC 06/23] mm/memblock: Add memblock early memory allocation
apis
On Sun, Oct 13, 2013 at 07:00:59PM +0100, Russell King - ARM Linux wrote:
> On Sun, Oct 13, 2013 at 01:56:48PM -0400, Tejun Heo wrote:
> > Hello,
> >
> > On Sat, Oct 12, 2013 at 05:58:49PM -0400, Santosh Shilimkar wrote:
> > > Introduce memblock early memory allocation APIs which allow to support
> > > LPAE extension on 32 bits archs. More over, this is the next step
> >
> > LPAE isn't something people outside arm circle would understand.
> > Let's stick to highmem.
>
> LPAE != highmem. Two totally different things, unless you believe
> system memory always starts at physical address zero, which is very
> far from the case on the majority of ARM platforms.
>
> So replacing LPAE with "highmem" is pure misrepresentation and is
> inaccurate. PAE might be a better term, and is also the x86 term
> for this.
Ah, right, forgot about the base address. Let's please spell out the
requirements then. Briefly explaining both aspects (non-zero base
addr & highmem) and why the existing bootmem based interfaced can't
serve them would be helpful to later readers.
Thanks.
--
tejun
--
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