From: Dave Hansen <dave.hansen@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Taku Izumi <izumi.taku@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
tony.luck@intel.com, mel@csn.ul.ie, akpm@linux-foundation.org,
Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@kernel.org>,
zhongjiang@huawei.com
Subject: Re: [PATCH][RFC] mm: Introduce kernelcore=reliable option
Date: Fri, 9 Oct 2015 08:08:40 -0700 [thread overview]
Message-ID: <5617D878.5060903@intel.com> (raw)
In-Reply-To: <5617989E.9070700@huawei.com>
On 10/09/2015 03:36 AM, Xishi Qiu wrote:
> I mean the mirrored region can not at the middle or end of the zone,
> BIOS should report the memory like this,
>
> e.g.
> BIOS
> node0: 0-4G mirrored, 4-8G mirrored, 8-16G non-mirrored
> node1: 16-24G mirrored, 24-32G non-mirrored
>
> OS
> node0: DMA DMA32 are both mirrored, NORMAL(4-8G), MOVABLE(8-16G)
> node1: NORMAL(16-24G), MOVABLE(24-32G)
I understand if the mirrored regions are always at the start of the zone
today, but is that somehow guaranteed going forward on all future hardware?
I think it's important to at least consider what we would do if DMA32
turned out to be non-reliable.
--
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: Dave Hansen <dave.hansen@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Taku Izumi <izumi.taku@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
tony.luck@intel.com, mel@csn.ul.ie, akpm@linux-foundation.org,
Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@kernel.org>,
zhongjiang@huawei.com
Subject: Re: [PATCH][RFC] mm: Introduce kernelcore=reliable option
Date: Fri, 9 Oct 2015 08:08:40 -0700 [thread overview]
Message-ID: <5617D878.5060903@intel.com> (raw)
In-Reply-To: <5617989E.9070700@huawei.com>
On 10/09/2015 03:36 AM, Xishi Qiu wrote:
> I mean the mirrored region can not at the middle or end of the zone,
> BIOS should report the memory like this,
>
> e.g.
> BIOS
> node0: 0-4G mirrored, 4-8G mirrored, 8-16G non-mirrored
> node1: 16-24G mirrored, 24-32G non-mirrored
>
> OS
> node0: DMA DMA32 are both mirrored, NORMAL(4-8G), MOVABLE(8-16G)
> node1: NORMAL(16-24G), MOVABLE(24-32G)
I understand if the mirrored regions are always at the start of the zone
today, but is that somehow guaranteed going forward on all future hardware?
I think it's important to at least consider what we would do if DMA32
turned out to be non-reliable.
next prev parent reply other threads:[~2015-10-09 15:08 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 [this message]
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
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=5617D878.5060903@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--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.