| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 27 Dec 2010 23:34:52 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Shaohui Zheng <shaohui.zheng@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>
cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
haicheng.li@...ux.intel.com, lethal@...ux-sh.org,
Andi Kleen <ak@...ux.intel.com>, dave@...ux.vnet.ibm.com,
Greg Kroah-Hartman <gregkh@...e.de>,
Haicheng Li <haicheng.li@...el.com>
Subject: [patch] mm: add node hotplug emulation
Add an interface to allow new nodes to be added when performing memory
hot-add. This provides a convenient interface to test memory hotplug
notifier callbacks and surrounding hotplug code when new nodes are
onlined without actually having a machine with such hotpluggable SRAT
entries.
This adds a new debugfs interface at /sys/kernel/debug/hotplug/add_node
that behaves in a similar way to the memory hot-add "probe" interface.
Its format is size@...rt, where "size" is the size of the new node to be
added and "start" is the physical address of the new memory.
The new node id is a currently offline, but possible, node. The bit must
be set in node_possible_map so that nr_node_ids is sized appropriately.
For emulation on x86, for example, it would be possible to set aside
memory for hotplugged nodes (say, anything above 2G) and to add an
additional four nodes as being possible on boot with
mem=2G numa=possible=4
and then creating a new 128M node at runtime:
# echo 128M@...0000000 > /sys/kernel/debug/hotplug/add_node
On node 1 totalpages: 0
init_memory_mapping: 0000000080000000-0000000088000000
0080000000 - 0088000000 page 2M
Once the new node has been added, its memory can be onlined. If this
memory represents memory section 16, for example:
# echo online > /sys/devices/system/memory/memory16/state
Built 2 zonelists in Node order, mobility grouping on. Total pages: 514846
Policy zone: Normal
[ The memory section(s) mapped to a particular node are visible via
/sys/devices/system/node/node1, in this example. ]
The new node is now hotplugged and ready for testing.
Signed-off-by: David Rientjes <rientjes@...gle.com>
---
Documentation/memory-hotplug.txt | 24 +++++++++++++
mm/memory_hotplug.c | 69 ++++++++++++++++++++++++++++++++++++++
2 files changed, 93 insertions(+), 0 deletions(-)
diff --git a/Documentation/memory-hotplug.txt b/Documentation/memory-hotplug.txt
--- a/Documentation/memory-hotplug.txt
+++ b/Documentation/memory-hotplug.txt
@@ -18,6 +18,7 @@ be changed often.
4. Physical memory hot-add phase
4.1 Hardware(Firmware) Support
4.2 Notify memory hot-add event by hand
+ 4.3 Node hotplug emulation
5. Logical Memory hot-add phase
5.1. State of memory
5.2. How to online memory
@@ -215,6 +216,29 @@ current implementation). You'll have to online memory by yourself.
Please see "How to online memory" in this text.
+4.3 Node hotplug emulation
+------------
+With debugfs, it is possible to test node hotplug by assigning the newly
+added memory to a new node id when using a different interface with a similar
+behavior to "probe" described in section 4.2. If a node id is possible
+(there are bits in /sys/devices/system/memory/possible that are not online),
+then it may be used to emulate a newly added node as the result of memory
+hotplug by using the debugfs "add_node" interface.
+
+The add_node interface is located at "hotplug/add_node" at the debugfs mount
+point.
+
+You can create a new node of a specified size starting at the physical
+address of new memory by
+
+% echo size@...rt_address_of_new_memory > /sys/kernel/debug/hotplug/add_node
+
+Where "size" can be represented in megabytes or gigabytes (for example,
+"128M" or "1G"). The minumum size is that of a memory section.
+
+Once the new node has been added, it is possible to online the memory by
+toggling the "state" of its memory section(s) as described in section 5.1.
+
------------------------------
5. Logical Memory hot-add phase
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -927,3 +927,72 @@ int remove_memory(u64 start, u64 size)
}
#endif /* CONFIG_MEMORY_HOTREMOVE */
EXPORT_SYMBOL_GPL(remove_memory);
+
+#ifdef CONFIG_DEBUG_FS
+#include <linux/debugfs.h>
+
+static struct dentry *hotplug_debug_root;
+
+static ssize_t add_node_store(struct file *file, const char __user *buf,
+ size_t count, loff_t *ppos)
+{
+ NODEMASK_ALLOC(nodemask_t, mask, GFP_KERNEL);
+ u64 start, size;
+ char buffer[128];
+ char *p;
+ int nid;
+ int ret;
+
+ if (!mask)
+ return -ENOMEM;
+ memset(buffer, 0, sizeof(buffer));
+ if (count > sizeof(buffer) - 1) {
+ ret = -EINVAL;
+ goto out;
+ }
+ if (copy_from_user(buffer, buf, count)) {
+ ret = -EFAULT;
+ goto out;
+ }
+
+ ret = -EINVAL;
+ size = memparse(buffer, &p);
+ if (size < ((u64)PAGES_PER_SECTION << PAGE_SHIFT))
+ goto out;
+ if (*p != '@')
+ goto out;
+ if (strict_strtoull(p + 1, 0, &start) < 0)
+ goto out;
+
+ ret = -ENOMEM;
+ nodes_andnot(*mask, node_possible_map, node_online_map);
+ nid = first_node(*mask);
+ if (nid == MAX_NUMNODES)
+ goto out;
+
+ ret = add_memory(nid, start, size);
+out:
+ NODEMASK_FREE(mask);
+ return ret ? ret : count;
+}
+
+static const struct file_operations add_node_file_ops = {
+ .write = add_node_store,
+ .llseek = generic_file_llseek,
+};
+
+static int __init hotplug_debug_init(void)
+{
+ hotplug_debug_root = debugfs_create_dir("hotplug", NULL);
+ if (!hotplug_debug_root)
+ return -ENOMEM;
+
+ if (!debugfs_create_file("add_node", S_IWUSR, hotplug_debug_root,
+ NULL, &add_node_file_ops))
+ return -ENOMEM;
+
+ return 0;
+}
+
+module_init(hotplug_debug_init);
+#endif /* CONFIG_DEBUG_FS */
--
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