linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Tang Chen <tangchen@cn.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"jiang.liu@huawei.com" <jiang.liu@huawei.com>,
	"wujianguo@huawei.com" <wujianguo@huawei.com>,
	"wency@cn.fujitsu.com" <wency@cn.fujitsu.com>,
	"laijs@cn.fujitsu.com" <laijs@cn.fujitsu.com>,
	"linfeng@cn.fujitsu.com" <linfeng@cn.fujitsu.com>,
	"yinghai@kernel.org" <yinghai@kernel.org>,
	"isimatu.yasuaki@jp.fujitsu.com" <isimatu.yasuaki@jp.fujitsu.com>,
	"rob@landley.net" <rob@landley.net>,
	"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
	"minchan.kim@gmail.com" <minchan.kim@gmail.com>,
	"mgorman@suse.de" <mgorman@suse.de>,
	"rientjes@google.com" <rientjes@google.com>,
	"guz.fnst@cn.fujitsu.com" <guz.fnst@cn.fujitsu.com>,
	"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
	"lliubbo@gmail.com" <lliubbo@gmail.com>,
	"jaegeuk.hanse@gmail.com" <jaegeuk.hanse@gmail.com>,
	"glommer@parallels.com" <glommer@parallels.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 3/3] acpi, memory-hotplug: Support getting hotplug info from SRAT.
Date: Tue, 29 Jan 2013 10:40:42 -0800	[thread overview]
Message-ID: <510817AA.4070800@zytor.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F1C9909DD@ORSMSX108.amr.corp.intel.com>

On 01/29/2013 10:38 AM, Luck, Tony wrote:
>>> Node 0 (or more specifically the node that contains memory<4GB) will be
>>> full of BIOS reserved holes in the memory map.
> 
>> One thing I'm not sure, is memory<4GB always on node 0 ?
>> On my box, it is on node 0.
> 
> I think in practice the <4GB memory will be on node 0 ... but it all depends
> on how Linux decides to number the nodes ... which in turn depends on the
> order of entries in various BIOS tables.  So it is theoretically possible that
> we'd end up with some system on which the low memory is on some other
> node. But it might require stranger than usual BIOS.
> 
> Summary: coding "node == 0" is almost 100% certain to be right - except
> on some pathological systems.  So code for node==0 and if we ever see
> a pathological machine - we can either point and laugh at the BIOS people
> that set that up - or possibly fix our code.
> 

We also probably need to weld down the memory that the kernel static
areas occupy and where we have allocated memory during boot time.  In
particular, memory that you want to be movable MUST NOT have boot-time
kernel allocations, and it becomes critical to enforce that, lest you
pull memory that you thought was safe and crash the system.

	-hpa


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2013-01-29 18:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25  9:42 [PATCH 0/3] Support SRAT for movablemem_map boot option Tang Chen
2013-01-25  9:42 ` [PATCH 1/3] acpi, memory-hotplug: Parse SRAT before memblock is ready Tang Chen
2013-01-25  9:42 ` [PATCH 2/3] acpi, memory-hotplug: Extend movablemem_map ranges to the end of node Tang Chen
2013-01-26  0:36   ` Andrew Morton
2013-01-28  1:53     ` Tang Chen
2013-01-25  9:42 ` [PATCH 3/3] acpi, memory-hotplug: Support getting hotplug info from SRAT Tang Chen
2013-01-26  0:40   ` Andrew Morton
2013-01-26  1:12   ` Andrew Morton
2013-01-26  1:29     ` H. Peter Anvin
2013-01-28  2:07       ` Tang Chen
2013-01-28 17:45         ` Luck, Tony
2013-01-29  6:43           ` Tang Chen
2013-01-29 18:38             ` Luck, Tony
2013-01-29 18:40               ` H. Peter Anvin [this message]
2013-01-28  9:15     ` Tang Chen
2013-02-04 23:26   ` Andrew Morton
2013-02-06  2:20     ` Tang Chen
2013-02-06 21:54       ` Andrew Morton
2013-02-07  6:22         ` Tang Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=510817AA.4070800@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=glommer@parallels.com \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=jaegeuk.hanse@gmail.com \
    --cc=jiang.liu@huawei.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linfeng@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@gmail.com \
    --cc=mgorman@suse.de \
    --cc=minchan.kim@gmail.com \
    --cc=rientjes@google.com \
    --cc=rob@landley.net \
    --cc=rusty@rustcorp.com.au \
    --cc=tangchen@cn.fujitsu.com \
    --cc=tony.luck@intel.com \
    --cc=wency@cn.fujitsu.com \
    --cc=wujianguo@huawei.com \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox