From e982232d164b2d77cdf35b7652e0e25572165f51 Mon Sep 17 00:00:00 2001 From: Xishi Qiu Date: Mon, 25 Mar 2013 19:14:16 +0800 Subject: [PATCH] --- yaml --- r: 362845 b: refs/heads/master c: 797f6a684f28dbb00f9e9719315574e344fcbf53 h: refs/heads/master i: 362843: 864dbf99532606c6d8faa5f8b24962bf1aa161f1 v: v3 --- [refs] | 2 +- trunk/Documentation/kdump/kdump.txt | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index d693ee152c81..ef622db218c9 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 83d435dd6e24b17955f91480f633bb39f0a7c2b4 +refs/heads/master: 797f6a684f28dbb00f9e9719315574e344fcbf53 diff --git a/trunk/Documentation/kdump/kdump.txt b/trunk/Documentation/kdump/kdump.txt index 13f1aa09b938..9c7fd988e299 100644 --- a/trunk/Documentation/kdump/kdump.txt +++ b/trunk/Documentation/kdump/kdump.txt @@ -297,6 +297,7 @@ Boot into System Kernel On ia64, 256M@256M is a generous value that typically works. The region may be automatically placed on ia64, see the dump-capture kernel config option notes above. + If use sparse memory, the size should be rounded to GRANULE boundaries. On s390x, typically use "crashkernel=xxM". The value of xx is dependent on the memory consumption of the kdump system. In general this is not