From: Tony Luck <tony.luck@gmail.com>
To: "Izumi, Taku" <izumi.taku@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"qiuxishi@huawei.com" <qiuxishi@huawei.com>,
"Kamezawa, Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"mel@csn.ul.ie" <mel@csn.ul.ie>,
"dave.hansen@intel.com" <dave.hansen@intel.com>,
"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>
Subject: Re: [PATCH v2 0/2] mm: Introduce kernelcore=reliable option
Date: Tue, 8 Dec 2015 08:11:06 -0800 [thread overview]
Message-ID: <CA+8MBbJuYwT+PWu_Amy7RWxmNvuvG++Bn9ZL3kfbkz_rByqUKg@mail.gmail.com> (raw)
In-Reply-To: <E86EADE93E2D054CBCD4E708C38D364A54298EAE@G01JPEXMBYT01>
On Tue, Dec 8, 2015 at 12:07 AM, Izumi, Taku <izumi.taku@jp.fujitsu.com> wrote:
> Which do you think is beter ?
> - change into kernelcore="mirrored"
> - keep kernelcore="reliable" and minmal printk fix
UEFI came up with the "reliable" wording (as a more generic term ...
as Andrew said
it could cover differences in ECC modes, or some alternate memory
technology that
has lower error rates).
But I personally like "mirror" more ... it matches current
implementation. Of course
I'll look silly if some future system does something other than mirror.
-Tony
next prev parent reply other threads:[~2015-12-08 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 15:03 [PATCH v2 0/2] mm: Introduce kernelcore=reliable option Taku Izumi
2015-11-27 15:04 ` [PATCH v2 1/2] mm: Calculate zone_start_pfn at zone_spanned_pages_in_node() Taku Izumi
2015-11-27 15:04 ` [PATCH v2 2/2] mm: Introduce kernelcore=reliable option Taku Izumi
2015-12-09 2:25 ` Xishi Qiu
2015-12-09 2:40 ` Xishi Qiu
2015-12-09 3:10 ` Izumi, Taku
2015-12-08 0:25 ` [PATCH v2 0/2] " Tony Luck
2015-12-08 0:31 ` Andrew Morton
2015-12-08 8:07 ` Izumi, Taku
2015-12-08 16:11 ` Tony Luck [this message]
2015-12-08 23:53 ` 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=CA+8MBbJuYwT+PWu_Amy7RWxmNvuvG++Bn9ZL3kfbkz_rByqUKg@mail.gmail.com \
--to=tony.luck@gmail.com \
--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=matt@codeblueprint.co.uk \
--cc=mel@csn.ul.ie \
--cc=qiuxishi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).