From: Matt Fleming <matt@codeblueprint.co.uk>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Hansen, Dave" <dave.hansen@intel.com>,
Xishi Qiu <qiuxishi@huawei.com>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Taku Izumi <izumi.taku@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"mel@csn.ul.ie" <mel@csn.ul.ie>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@kernel.org>,
"zhongjiang@huawei.com" <zhongjiang@huawei.com>
Subject: Re: [PATCH][RFC] mm: Introduce kernelcore=reliable option
Date: Mon, 12 Oct 2015 11:32:35 +0100 [thread overview]
Message-ID: <20151012103235.GB2579@codeblueprint.co.uk> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F32B523DB@ORSMSX114.amr.corp.intel.com>
On Fri, 09 Oct, at 06:51:34PM, Luck, Tony wrote:
>
> Current hardware can map one mirrored region from each memory controller.
> We have two memory controllers per socket. So on a 4-socket machine we will
> usually have 8 separate mirrored ranges. Two per NUMA node (assuming
> cluster on die is not enabled).
>
> Practically I think it is safe to assume that any sane configuration will always
> choose to mirror the <4GB range:
>
> 1) It's a trivial percentage of total memory on a system that supports mirror
> (2GB[1] out of my, essentially minimal, 512GB[2] machine). So 0.4% ... why would
> you not mirror it?
> 2) It contains a bunch of things that you are likely to want mirrored. Currently
> our boot loaders put the kernel there (don't they??). All sorts of BIOS space that
> might be accessed at any time by SMI is there.
Yeah, the bootloader and kernel image will most likely be in < 4GB
region. That's not a hard requirement, and there's certainly support
for loading things at higher addresses, but this low region is
currently still preferred (see CONFIG_PHYSICAL_START).
--
Matt Fleming, Intel Open Source Technology Center
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@codeblueprint.co.uk>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Hansen, Dave" <dave.hansen@intel.com>,
Xishi Qiu <qiuxishi@huawei.com>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Taku Izumi <izumi.taku@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"mel@csn.ul.ie" <mel@csn.ul.ie>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@kernel.org>,
"zhongjiang@huawei.com" <zhongjiang@huawei.com>
Subject: Re: [PATCH][RFC] mm: Introduce kernelcore=reliable option
Date: Mon, 12 Oct 2015 11:32:35 +0100 [thread overview]
Message-ID: <20151012103235.GB2579@codeblueprint.co.uk> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F32B523DB@ORSMSX114.amr.corp.intel.com>
On Fri, 09 Oct, at 06:51:34PM, Luck, Tony wrote:
>
> Current hardware can map one mirrored region from each memory controller.
> We have two memory controllers per socket. So on a 4-socket machine we will
> usually have 8 separate mirrored ranges. Two per NUMA node (assuming
> cluster on die is not enabled).
>
> Practically I think it is safe to assume that any sane configuration will always
> choose to mirror the <4GB range:
>
> 1) It's a trivial percentage of total memory on a system that supports mirror
> (2GB[1] out of my, essentially minimal, 512GB[2] machine). So 0.4% ... why would
> you not mirror it?
> 2) It contains a bunch of things that you are likely to want mirrored. Currently
> our boot loaders put the kernel there (don't they??). All sorts of BIOS space that
> might be accessed at any time by SMI is there.
Yeah, the bootloader and kernel image will most likely be in < 4GB
region. That's not a hard requirement, and there's certainly support
for loading things at higher addresses, but this low region is
currently still preferred (see CONFIG_PHYSICAL_START).
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-10-12 10:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 14:56 [PATCH][RFC] mm: Introduce kernelcore=reliable option Taku Izumi
2015-10-09 14:56 ` Taku Izumi
2015-10-09 6:46 ` Xishi Qiu
2015-10-09 6:46 ` Xishi Qiu
2015-10-09 9:24 ` Kamezawa Hiroyuki
2015-10-09 9:24 ` Kamezawa Hiroyuki
2015-10-09 10:36 ` Xishi Qiu
2015-10-09 10:36 ` Xishi Qiu
2015-10-09 15:08 ` Dave Hansen
2015-10-09 15:08 ` Dave Hansen
2015-10-09 18:51 ` Luck, Tony
2015-10-09 18:51 ` Luck, Tony
2015-10-12 10:32 ` Matt Fleming [this message]
2015-10-12 10:32 ` Matt Fleming
2015-10-10 2:01 ` Xishi Qiu
2015-10-10 2:01 ` Xishi Qiu
2015-10-12 18:43 ` Luck, Tony
2015-10-12 18:43 ` Luck, Tony
2015-10-13 9:51 ` Kamezawa Hiroyuki
2015-10-13 9:51 ` Kamezawa Hiroyuki
2015-10-09 21:43 ` Luck, Tony
2015-10-09 21:43 ` Luck, Tony
2015-10-14 1:19 ` Izumi, Taku
2015-10-14 1:19 ` Izumi, Taku
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=20151012103235.GB2579@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=qiuxishi@huawei.com \
--cc=tony.luck@intel.com \
--cc=zhongjiang@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.