From: "Zheng, Shaohui" <shaohui.zheng@intel.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"y-goto@jp.fujitsu.com" <y-goto@jp.fujitsu.com>,
Dave Hansen <haveblue@us.ibm.com>,
"x86@kernel.org" <x86@kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: [ RESEND PATCH v3] Memory-Hotplug: Fix the bug on interface /dev/mem for 64-bit kernel
Date: Tue, 12 Jan 2010 15:45:54 +0800 [thread overview]
Message-ID: <DA586906BA1FFC4384FCFD6429ECE860316C0133@shzsmsx502.ccr.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2845 bytes --]
Resend the v3 patch after reviewed by KAMEZAWA Hiroyuki. We still keep the
Old e820map, update variable max_pfn, max_low_pfn and high_memory only.
It is dependent on Fenguang's page_is_ram patch.
Memory-Hotplug: Fix the bug on interface /dev/mem for 64-bit kernel
The new added memory can not be access by interface /dev/mem, because we do not
update the variable high_memory, max_pfn and max_low_pfn.
Memory hotplug still has critical issues for 32-bit kernel, and it is more
important for 64-bit kernel, we fix it on 64-bit first. We add a function
update_end_of_memory_vars in file arch/x86/mm/init.c to update these variables.
CC: Andi Kleen <ak@linux.intel.com>
CC: Li Haicheng <haicheng.li@intel.com>
Reviewed-by: Wu Fengguang <fengguang.wu@intel.com>
Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Signed-off-by: Shaohui Zheng <shaohui.zheng@intel.com>
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index d406c52..b6a85cc 100644
--- a/arch/x86/mm/init.c
+++ b/arch/x86/mm/init.c
@@ -1,6 +1,7 @@
#include <linux/initrd.h>
#include <linux/ioport.h>
#include <linux/swap.h>
+#include <linux/bootmem.h>
#include <asm/cacheflush.h>
#include <asm/e820.h>
@@ -386,3 +387,24 @@ void free_initrd_mem(unsigned long start, unsigned long end)
free_init_pages("initrd memory", start, end);
}
#endif
+
+/**
+ * After memory hotplug, the variable max_pfn, max_low_pfn and high_memory will
+ * be affected, it will be updated in this function. Memory hotplug still has
+ * critical issues on 32-bit kennel, it was more important on 64-bit kernel,
+ * so we update the variables for 64-bit kernel first, fix me in future for
+ * 32-bit kenrel.
+ */
+void __meminit __attribute__((weak)) update_end_of_memory_vars(u64 start,
+ u64 size)
+{
+#ifdef CONFIG_X86_64
+ unsigned long start_pfn = start >> PAGE_SHIFT;
+ unsigned long end_pfn = PFN_UP(start + size);
+
+ if (end_pfn > max_pfn) {
+ max_low_pfn = max_pfn = end_pfn;
+ high_memory = (void *)__va(max_pfn * PAGE_SIZE - 1) + 1;
+ }
+#endif /* CONFIG_X86_64 */
+}
diff --git a/include/linux/bootmem.h b/include/linux/bootmem.h
index b10ec49..84533a5 100644
--- a/include/linux/bootmem.h
+++ b/include/linux/bootmem.h
@@ -13,6 +13,7 @@
extern unsigned long max_low_pfn;
extern unsigned long min_low_pfn;
+extern void update_end_of_memory_vars(u64 start, u64 size);
/*
* highest page
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 030ce8a..3e94b23 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -523,6 +523,9 @@ int __ref add_memory(int nid, u64 start, u64 size)
BUG_ON(ret);
}
+ /* update max_pfn, max_low_pfn and high_memory */
+ update_end_of_memory_vars(start, size);
+
goto out;
error:
Thanks & Regards,
Shaohui
[-- Attachment #2: memory-hotplug-fix-the-bug-on-interface-dev-mem-v3.patch --]
[-- Type: application/octet-stream, Size: 2529 bytes --]
Memory-Hotplug: Fix the bug on interface /dev/mem for 64-bit kernel
The new added memory can not be access by interface /dev/mem, because we do not
update the variable high_memory, max_pfn and max_low_pfn.
Memory hotplug still has critical issues for 32-bit kernel, and it is more
important for 64-bit kernel, we fix it on 64-bit first. We add a function
update_end_of_memory_vars in file arch/x86/mm/init.c to update these variables.
Signed-off-by: Shaohui Zheng <shaohui.zheng@intel.com>
CC: Andi Kleen <ak@linux.intel.com>
CC: Li Haicheng <haicheng.li@intel.com>
Reviewed-by: Wu Fengguang <fengguang.wu@intel.com>
Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index d406c52..b6a85cc 100644
--- a/arch/x86/mm/init.c
+++ b/arch/x86/mm/init.c
@@ -1,6 +1,7 @@
#include <linux/initrd.h>
#include <linux/ioport.h>
#include <linux/swap.h>
+#include <linux/bootmem.h>
#include <asm/cacheflush.h>
#include <asm/e820.h>
@@ -386,3 +387,24 @@ void free_initrd_mem(unsigned long start, unsigned long end)
free_init_pages("initrd memory", start, end);
}
#endif
+
+/**
+ * After memory hotplug, the variable max_pfn, max_low_pfn and high_memory will
+ * be affected, it will be updated in this function. Memory hotplug still has
+ * critical issues on 32-bit kennel, it was more important on 64-bit kernel,
+ * so we update the variables for 64-bit kernel first, fix me in future for
+ * 32-bit kenrel.
+ */
+void __meminit __attribute__((weak)) update_end_of_memory_vars(u64 start,
+ u64 size)
+{
+#ifdef CONFIG_X86_64
+ unsigned long start_pfn = start >> PAGE_SHIFT;
+ unsigned long end_pfn = PFN_UP(start + size);
+
+ if (end_pfn > max_pfn) {
+ max_low_pfn = max_pfn = end_pfn;
+ high_memory = (void *)__va(max_pfn * PAGE_SIZE - 1) + 1;
+ }
+#endif /* CONFIG_X86_64 */
+}
diff --git a/include/linux/bootmem.h b/include/linux/bootmem.h
index b10ec49..84533a5 100644
--- a/include/linux/bootmem.h
+++ b/include/linux/bootmem.h
@@ -13,6 +13,7 @@
extern unsigned long max_low_pfn;
extern unsigned long min_low_pfn;
+extern void update_end_of_memory_vars(u64 start, u64 size);
/*
* highest page
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 030ce8a..3e94b23 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -523,6 +523,9 @@ int __ref add_memory(int nid, u64 start, u64 size)
BUG_ON(ret);
}
+ /* update max_pfn, max_low_pfn and high_memory */
+ update_end_of_memory_vars(start, size);
+
goto out;
error:
next reply other threads:[~2010-01-12 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 7:45 Zheng, Shaohui [this message]
2010-01-12 8:04 ` KAMEZAWA Hiroyuki
2010-01-12 8:57 ` Zheng, Shaohui
2010-01-12 8:57 ` KAMEZAWA Hiroyuki
2010-01-12 9:05 ` Zheng, Shaohui
2010-01-12 13:17 ` Zheng, Shaohui
2010-01-14 13:24 ` Wu Fengguang
2010-01-14 14:08 ` Wu Fengguang
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=DA586906BA1FFC4384FCFD6429ECE860316C0133@shzsmsx502.ccr.corp.intel.com \
--to=shaohui.zheng@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=haveblue@us.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=x86@kernel.org \
--cc=y-goto@jp.fujitsu.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