From: "Luck, Tony" <tony.luck@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Xiexiuqi <xiexiuqi@huawei.com>, Linux MM <linux-mm@kvack.org>
Subject: RE: [RFC 3/3] x86, mirror: x86 enabling - find mirrored memory ranges and tell memblock
Date: Mon, 18 May 2015 17:36:07 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32A86CA0@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <55599E2F.4060800@huawei.com>
On 2015/2/4 6:40, Tony Luck wrote:
>> Can't post this part yet because it uses things in an upcoming[*] ACPI, UEFI, or some
>> other four-letter-ending-in-I standard. So just imagine a call someplace early
>> in startup that reads information about mirrored address ranges and does:
>>
> Does the upcoming[*] ACPI will add a new flag in SRAT tables? just like memory hotplug.
>
> #define ACPI_SRAT_MEM_HOT_PLUGGABLE (1<<1) /* 01: Memory region is hot pluggable */
> +#define ACPI_SRAT_MEM_MIRROR (1<<3) /* 03: Memory region is mirrored */
The choice for this was UEFI - new attribute bit in the GetMemoryMap() return value.
UEFI 2.5 has been published with this change and I posted a newer patch 10 days ago:
https://lkml.org/lkml/2015/5/8/521
-Tony
--
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>
next prev parent reply other threads:[~2015-05-18 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1423259664.git.tony.luck@intel.com>
2015-02-06 22:28 ` [RFC 0/3] Mirrored memory support for boot time allocations Tony Luck
[not found] ` <7bdbb1a569d487b3a772fbb7b66b9498d6cee551.1423259664.git.tony.luck@intel.com>
[not found] ` <55599E2F.4060800@huawei.com>
2015-05-18 17:36 ` Luck, Tony [this message]
[not found] ` <55599BAA.20204@huawei.com>
2015-05-18 8:23 ` Xishi Qiu
2015-05-18 17:42 ` Luck, Tony
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=3908561D78D1C84285E8C5FCA982C28F32A86CA0@ORSMSX114.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiuxishi@huawei.com \
--cc=xiexiuqi@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