From: Hariprasad Nellitheertha <hari@in.ibm.com>
To: ak@muc.de, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [RFC][x86_64] Introducing the memmap= kernel command line option
Date: Fri, 15 Apr 2005 11:43:55 +0530 [thread overview]
Message-ID: <425F5BA3.3050001@in.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
Hi Andi,
In order to port kdump to x86_64, we need to have the
memmap= kernel command line option available. This is so
that the dump-capture kernel can be booted with a custom
memory map.
The attached patch adds the memmap= functionality to the
x86_64 kernel. It is against 2.6.12-rc2-mm3. I have done
some amount of testing and it is working fine.
Could you kindly review this patch and let me know your
thoughts on it.
Thanks and Regards,
Hari
[-- Attachment #2: x8664-memmap-command-line-option.patch --]
[-- Type: text/plain, Size: 3449 bytes --]
This patch adds the 'memmap=' kernel command line option for the
x86_64 kernel.
Signed-off-by: Hariprasad Nellitheertha <hari@in.ibm.com>
---
linux-2.6.12-rc2-hari/Documentation/kernel-parameters.txt | 2 -
linux-2.6.12-rc2-hari/arch/x86_64/kernel/e820.c | 25 ++++++++++++++
linux-2.6.12-rc2-hari/arch/x86_64/kernel/setup.c | 3 +
linux-2.6.12-rc2-hari/include/asm-x86_64/e820.h | 2 +
4 files changed, 31 insertions(+), 1 deletion(-)
diff -puN arch/x86_64/kernel/e820.c~x8664-memmap-command-line-option arch/x86_64/kernel/e820.c
--- linux-2.6.12-rc2/arch/x86_64/kernel/e820.c~x8664-memmap-command-line-option 2005-04-15 10:15:04.000000000 +0530
+++ linux-2.6.12-rc2-hari/arch/x86_64/kernel/e820.c 2005-04-15 10:17:23.000000000 +0530
@@ -513,6 +513,31 @@ void __init parse_memopt(char *p, char *
end_user_pfn >>= PAGE_SHIFT;
}
+void __init parse_memmapopt(char *p, char **from)
+{
+ if (!memcmp(p, "exactmap", 8)) {
+ p += 8;
+ e820.nr_map = 0;
+ } else {
+ unsigned long long start_at, mem_size;
+
+ mem_size = memparse(p, from);
+ p = *from;
+ if (*p == '@') {
+ start_at = memparse(p+1, from);
+ add_memory_region(start_at, mem_size, E820_RAM);
+ } else if (*p == '#') {
+ start_at = memparse(p+1, from);
+ add_memory_region(start_at, mem_size, E820_ACPI);
+ } else if (*p == '$') {
+ start_at = memparse(p+1, from);
+ add_memory_region(start_at, mem_size, E820_RESERVED);
+ } else {
+ end_user_pfn = (mem_size >> PAGE_SHIFT);
+ }
+ }
+}
+
unsigned long pci_mem_start = 0xaeedbabe;
/*
diff -puN arch/x86_64/kernel/setup.c~x8664-memmap-command-line-option arch/x86_64/kernel/setup.c
--- linux-2.6.12-rc2/arch/x86_64/kernel/setup.c~x8664-memmap-command-line-option 2005-04-15 10:15:04.000000000 +0530
+++ linux-2.6.12-rc2-hari/arch/x86_64/kernel/setup.c 2005-04-15 10:15:04.000000000 +0530
@@ -349,6 +349,9 @@ static __init void parse_cmdline_early (
if (!memcmp(from, "mem=", 4))
parse_memopt(from+4, &from);
+ if (!memcmp(from, "memmap=", 7))
+ parse_memmapopt(from+7, &from);
+
#ifdef CONFIG_DISCONTIGMEM
if (!memcmp(from, "numa=", 5))
numa_setup(from+5);
diff -puN include/asm-x86_64/e820.h~x8664-memmap-command-line-option include/asm-x86_64/e820.h
--- linux-2.6.12-rc2/include/asm-x86_64/e820.h~x8664-memmap-command-line-option 2005-04-15 10:15:04.000000000 +0530
+++ linux-2.6.12-rc2-hari/include/asm-x86_64/e820.h 2005-04-15 10:15:04.000000000 +0530
@@ -54,6 +54,8 @@ extern void e820_setup_gap(void);
extern void __init parse_memopt(char *p, char **end);
+extern void __init parse_memmapopt(char *p, char **end);
+
extern struct e820map e820;
#endif/*!__ASSEMBLY__*/
diff -puN Documentation/kernel-parameters.txt~x8664-memmap-command-line-option Documentation/kernel-parameters.txt
--- linux-2.6.12-rc2/Documentation/kernel-parameters.txt~x8664-memmap-command-line-option 2005-04-15 10:19:37.000000000 +0530
+++ linux-2.6.12-rc2-hari/Documentation/kernel-parameters.txt 2005-04-15 10:19:56.000000000 +0530
@@ -794,7 +794,7 @@ running once the system is up.
mem=nopentium [BUGS=IA-32] Disable usage of 4MB pages for kernel
memory.
- memmap=exactmap [KNL,IA-32] Enable setting of an exact
+ memmap=exactmap [KNL,IA-32,X86-64] Enable setting of an exact
E820 memory map, as specified by the user.
Such memmap=exactmap lines can be constructed based on
BIOS output or other requirements. See the memmap=nn@ss
_
next reply other threads:[~2005-04-15 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 6:13 Hariprasad Nellitheertha [this message]
2005-04-15 17:30 ` [RFC][x86_64] Introducing the memmap= kernel command line option Andi Kleen
2005-04-18 12:47 ` Hariprasad Nellitheertha
2005-04-28 10:59 ` Hariprasad Nellitheertha
2005-04-28 11:00 ` [RFC][i386] Comma parsing for " Hariprasad Nellitheertha
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=425F5BA3.3050001@in.ibm.com \
--to=hari@in.ibm.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
/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.