[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130805150127.GC19631@mtj.dyndns.org>
Date: Mon, 5 Aug 2013 11:01:27 -0400
From: Tejun Heo <tj@...nel.org>
To: Santosh Shilimkar <santosh.shilimkar@...com>
Cc: Yinghai Lu <yinghai@...nel.org>,
Russell King - ARM Linux <linux@....linux.org.uk>,
linux-arm-kernel@...ts.infradead.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Nicolas Pitre <nicolas.pitre@...aro.org>,
Ingo Molnar <mingo@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
"David S. Miller" <davem@...emloft.net>,
"sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>,
Sam Ravnborg <sam@...nborg.org>, linux-arch@...r.kernel.org
Subject: Re: [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM
Hello,
On Fri, Aug 02, 2013 at 05:06:02PM -0400, Santosh Shilimkar wrote:
> Looking at the situation, how about proceeding with patch updating
> the bootmem API signatures to use phys_addr_t which can unblock me
> to get my machine working.
I'm not sure about that. No matter how you play it, it'll end up
duplicating memblock interface.
> Introduction of new API, conversions of core kernel code and then
What new API are we talking about? Wasn't the plan to convert core
kernel code to use memblock and let bootmem emulate bootmem API?
There's no new API.
> arches moving away from bootmem is going to take significant time
And arches moving away from bootmem doesn't have to happen now.
> anyways. I will continue my effort to get ARM port moved to no-bootmem
> and get that merged.
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