[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32A86CA0@ORSMSX114.amr.corp.intel.com>
Date: Mon, 18 May 2015 17:36:07 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Xishi Qiu <qiuxishi@...wei.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Xiexiuqi <xiexiuqi@...wei.com>, Linux MM <linux-mm@...ck.org>
Subject: RE: [RFC 3/3] x86, mirror: x86 enabling - find mirrored memory
ranges and tell memblock
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists