From: Xishi Qiu <qiuxishi@huawei.com>
To: Tony Luck <tony.luck@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@vger.kernel.org>,
Xiexiuqi <xiexiuqi@huawei.com>
Subject: Re: [RFC 3/3] x86, mirror: x86 enabling - find mirrored memory ranges and tell memblock
Date: Mon, 18 May 2015 16:09:19 +0800 [thread overview]
Message-ID: <55599E2F.4060800@huawei.com> (raw)
In-Reply-To: <7bdbb1a569d487b3a772fbb7b66b9498d6cee551.1423259664.git.tony.luck@intel.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:
>
Hi Tony,
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 */
acpi_numa_memory_affinity_init()
...
hotpluggable = ma->flags & ACPI_SRAT_MEM_HOT_PLUGGABLE;
+ mirrorable = ma->flags & ACPI_SRAT_MEM_MIRROR;
...
+ if (mirrorable)
+ memblock_mark_mirror(start, size);
...
Thanks,
Xishi Qiu
> + for (...) {
> + start = ...;
> + size = ...;
> + if (it looks mirrored)
> + memblock_mark_mirror(start, size);
> + }
>
> Whole patch is pretty tiny:
>
> 3 files changed, 19 insertions(+)
>
> How much damage could I possibly do in just 19 lines?
>
> -Tony
>
> [*] very soon, I'm told
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2015-05-18 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 21:54 [RFC 0/3] Mirrored memory support for boot time allocations Tony Luck
2015-01-30 22:30 ` [RFC 1/3] mm/memblock: Add extra "flag" to memblock to allow selection of memory based on attribute Tony Luck
2015-02-03 22:38 ` [RFC 2/3] mm/memblock: Allocate boot time data structures from mirrored memory Tony Luck
2015-02-03 22:40 ` [RFC 3/3] x86, mirror: x86 enabling - find mirrored memory ranges and tell memblock Tony Luck
2015-05-18 8:09 ` Xishi Qiu [this message]
2015-05-18 17:36 ` Luck, Tony
2015-05-18 17:36 ` Luck, Tony
2015-02-06 22:28 ` [RFC 0/3] Mirrored memory support for boot time allocations Tony Luck
2015-02-06 22:28 ` Tony Luck
2015-05-18 7:58 ` Xishi Qiu
2015-05-18 8:23 ` Xishi Qiu
2015-05-18 8:23 ` Xishi Qiu
2015-05-18 17:42 ` Luck, Tony
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=55599E2F.4060800@huawei.com \
--to=qiuxishi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=tony.luck@intel.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 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.