diff options
author | Keir Fraser <keir.fraser@citrix.com> | 2010-04-26 12:12:12 +0100 |
---|---|---|
committer | Keir Fraser <keir.fraser@citrix.com> | 2010-04-26 12:12:12 +0100 |
commit | c1cfb1a358c12bdf1284f6bcf55407366efaf485 (patch) | |
tree | 6dedec1891e2f79822663ae6c8b881e938665b04 /xen/include/xen/kexec.h | |
parent | efaca454ab76878603ed9c2ce61b94e9bba0fe35 (diff) | |
download | xen-c1cfb1a358c12bdf1284f6bcf55407366efaf485.tar.gz xen-c1cfb1a358c12bdf1284f6bcf55407366efaf485.tar.bz2 xen-c1cfb1a358c12bdf1284f6bcf55407366efaf485.zip |
Support Linux's advanced crashkernel= syntax
Quoting the original Linux patch's description:
"This patch adds a extended crashkernel syntax that makes the value of
reserved system RAM dependent on the system RAM itself:
crashkernel=3D<range1>:<size1>[,<range2>:<size2>,...][@offset]
range=3Dstart-[end]
For example:
crashkernel=3D512M-2G:64M,2G-:128M
The motivation comes from distributors that configure their
crashkernel command line automatically with some configuration tool
(YaST, you know ;)). Of course that tool knows the value of System
RAM, but if the user removes RAM, then the system becomes unbootable
or at least unusable and error handling is very difficult."
For x86, other than Linux we pass the actual amount of RAM rather than
the highest page's address (to cope with sparse physical address
maps).
This still needs to be hooked up for ia64.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Diffstat (limited to 'xen/include/xen/kexec.h')
-rw-r--r-- | xen/include/xen/kexec.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/xen/include/xen/kexec.h b/xen/include/xen/kexec.h index d78510e639..fb1e6b59b1 100644 --- a/xen/include/xen/kexec.h +++ b/xen/include/xen/kexec.h @@ -12,6 +12,8 @@ typedef struct xen_kexec_reserve { extern xen_kexec_reserve_t kexec_crash_area; +void set_kexec_crash_area_size(u64 system_ram); + /* We have space for 4 images to support atomic update * of images. This is important for CRASH images since * a panic can happen at any time... |