* Andrew Morton <[EMAIL PROTECTED]> [2008-04-30 11:29]:
>
> I'm a bit surprised to see the code being updated but not the
> documentation. Were they out of sync before or are they out of sync after
> this patch or were they always in sync or what?
It was simply not specified. I propose the following patch to make it
clear:
----
[PATCH] Clarify inclusive/exclusive in crashkernel commandline in documentation
Reflect the changes from Michael Ellerman in crashkernel syntax that make the
end of the memory exclusive in the documentation. It was simply not specified
before.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
Documentation/kdump/kdump.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--- a/Documentation/kdump/kdump.txt
+++ b/Documentation/kdump/kdump.txt
@@ -245,6 +245,8 @@ The syntax is:
crashkernel=<range1>:<size1>[,<range2>:<size2>,[EMAIL PROTECTED]
range=start-[end]
+ 'start' is inclusive and 'end' is exclusive.
+
For example:
crashkernel=512M-2G:64M,2G-:128M
@@ -253,10 +255,11 @@ This would mean:
1) if the RAM is smaller than 512M, then don't reserve anything
(this is the "rescue" case)
- 2) if the RAM size is between 512M and 2G, then reserve 64M
+ 2) if the RAM size is between 512M and 2G (exclusive), then reserve 64M
3) if the RAM size is larger than 2G, then reserve 128M
+
Boot into System Kernel
=======================
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
