[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50B41573.4020205@zytor.com>
Date: Mon, 26 Nov 2012 17:20:51 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Jiang Liu <jiang.liu@...wei.com>
CC: Tang Chen <tangchen@...fujitsu.com>,
wujianguo <wujianguo106@...il.com>, akpm@...ux-foundation.org,
rob@...dley.net, isimatu.yasuaki@...fujitsu.com,
laijs@...fujitsu.com, wency@...fujitsu.com, linfeng@...fujitsu.com,
yinghai@...nel.org, kosaki.motohiro@...fujitsu.com,
minchan.kim@...il.com, mgorman@...e.de, rientjes@...gle.com,
rusty@...tcorp.com.au, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-doc@...r.kernel.org,
wujianguo@...wei.com, qiuxishi@...wei.com,
Len Brown <lenb@...nel.org>
Subject: Re: [PATCH v2 5/5] page_alloc: Bootmem limit with movablecore_map
On 11/26/2012 05:12 PM, Jiang Liu wrote:
> Hi Peter,
>
> I have tried to reserved movable memory from bootmem allocator, but the
> ACPICA subsystem is initialized later than setting up movable zone.
> So still trying to figure out a way to setup/reserve movable zones
> according to information from static ACPI tables such as SRAT/MPST etc.
>
[Adding Len Brown]
Right, for the case of platform-configured memory. Len, I'm wondering
if there is any reasonable way we can get memory-map-related stuff out
of ACPI before we initialize the full ACPICA... we could of course write
an ad hoc static parser (these are just static tables, after all), but
I'm not sure if that fits into your overall view of how the subsystem
should work?
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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