aboutsummaryrefslogtreecommitdiffstats
path: root/include/linux/memory_hotplug.h
diff options
context:
space:
mode:
authorJuergen Gross <jgross@suse.com>2019-02-14 05:42:39 -0500
committerJuergen Gross <jgross@suse.com>2019-02-18 00:50:34 -0500
commit357b4da50a62e2fd70eacee21cdbd22d4c7a7b60 (patch)
tree67ddf0b7850cf8fa134d97cf00ba7647bf627591 /include/linux/memory_hotplug.h
parent068e79f4a9d613f4327cb4062a1e49c0eaca7149 (diff)
x86: respect memory size limiting via mem= parameter
When limiting memory size via kernel parameter "mem=" this should be respected even in case of memory made accessible via a PCI card. Today this kind of memory won't be made usable in initial memory setup as the memory won't be visible in E820 map, but it might be added when adding PCI devices due to corresponding ACPI table entries. Not respecting "mem=" can be corrected by adding a global max_mem_size variable set by parse_memopt() which will result in rejecting adding memory areas resulting in a memory size above the allowed limit. Signed-off-by: Juergen Gross <jgross@suse.com> Acked-by: Ingo Molnar <mingo@kernel.org> Reviewed-by: William Kucharski <william.kucharski@oracle.com> Signed-off-by: Juergen Gross <jgross@suse.com>
Diffstat (limited to 'include/linux/memory_hotplug.h')
-rw-r--r--include/linux/memory_hotplug.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index 368267c1b71b..cfd12078172a 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -100,6 +100,8 @@ extern void __online_page_free(struct page *page);
100 100
101extern int try_online_node(int nid); 101extern int try_online_node(int nid);
102 102
103extern u64 max_mem_size;
104
103extern bool memhp_auto_online; 105extern bool memhp_auto_online;
104/* If movable_node boot option specified */ 106/* If movable_node boot option specified */
105extern bool movable_node_enabled; 107extern bool movable_node_enabled;