lkml.org 
[lkml]   [2005]   [Apr]   [29]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateFri, 29 Apr 2005 10:37:29 +0530
FromVivek Goyal <>
SubjectRe: [PATCH] Kdump docs.
Hi Randy,

> +  A) First kernel:
> +   a) Enable "kexec system call" feature (in Processor type and features).
> +	CONFIG_KEXEC=y
> +   b) This kernel's physical load address should be the default value of
> +      0x100000 (0x100000, 1 MB) (in Processor type and features).
> +	CONFIG_PHYSICAL_START=0x100000
> +   c) Enable "sysfs file system support" (in Pseudo filesystems).
> +	CONFIG_SYSFS=y
> +   d) Boot into first kernel with the command line parameter "crashkernel=Y@X".
> +      Use appropriate values for X and Y. Y denotes how much memory to reserve
> +      for the second kernel, and X denotes at what physical address the reserved
> +      memory section starts. For example: "crashkernel=64M@16M".
> +
> +  B) Second kernel:
> +   a) Enable "kernel crash dumps" feature (in Processor type and features).
> +	CONFIG_CRASH_DUMP=y
> +   b) Specify a suitable value for "Physical address where the kernel is
> +      loaded" (in Processor type and features). Typically this value
> +      should be same as X (See option b) above, e.g., 16 MB or 0x1000000.

Should above line be as follows.
"should be same as X (See option d) above."

This will make clear what is X and what should be the new value of 
CONFIG_PHYSICAL_START. 

Thanks for testing out and providing a clearer documentation.

Thanks
Vivek

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-04-29 05:11    [W:0.319 / U:0.110 seconds]
©2003-2008 Jasper Spaans