diff options
| author | Michael Ellerman <michael@ellerman.id.au> | 2008-05-01 04:34:49 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-05-01 08:04:00 -0700 |
| commit | be089d79c46f5efa77fbdf03c5e576e220bf143f (patch) | |
| tree | 4aee7d61812806d797b60fe6b8f4987dcc03c011 /crypto/lzo.c | |
| parent | c85d194bfd2e36c5254b8058c1f35cfce0dfa10a (diff) | |
| download | linux-be089d79c46f5efa77fbdf03c5e576e220bf143f.tar.bz2 | |
kexec: make extended crashkernel= syntax less confusing
The extended crashkernel syntax is a little confusing in the way it handles
ranges. eg:
crashkernel=512M-2G:64M,2G-:128M
Means if the machine has between 512M and 2G of memory the crash region should
be 64M, and if the machine has 2G of memory the region should be 64M. Only if
the machine has more than 2G memory will 128M be allocated.
Although that semantic is correct, it is somewhat baffling. Instead I propose
that the end of the range means the first address past the end of the range,
ie: 512M up to but not including 2G.
[bwalle@suse.de: clarify inclusive/exclusive in crashkernel commandline in documentation]
Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
Acked-by: Bernhard Walle <bwalle@suse.de>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Simon Horman <horms@verge.net.au>
Signed-off-by: Bernhard Walle <bwalle@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'crypto/lzo.c')
0 files changed, 0 insertions, 0 deletions