aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/s390/zfcpdump.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/s390/zfcpdump.txt')
-rw-r--r--Documentation/s390/zfcpdump.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/s390/zfcpdump.txt b/Documentation/s390/zfcpdump.txt
index cf45d27c4608..1cae248c3b77 100644
--- a/Documentation/s390/zfcpdump.txt
+++ b/Documentation/s390/zfcpdump.txt
@@ -21,7 +21,7 @@ standalone dump format. It can be used in the same way as e.g. /dev/mem. The
21dump format defines a 4K header followed by plain uncompressed memory. The 21dump format defines a 4K header followed by plain uncompressed memory. The
22register sets are stored in the prefix pages of the respective cpus. To build a 22register sets are stored in the prefix pages of the respective cpus. To build a
23dump enabled kernel with the zcore driver, the kernel config option 23dump enabled kernel with the zcore driver, the kernel config option
24CONFIG_ZFCPDUMP has to be set. When reading from "zcore/mem", the part of 24CONFIG_CRASH_DUMP has to be set. When reading from "zcore/mem", the part of
25memory, which has been saved by hardware is read by the driver via the SCLP 25memory, which has been saved by hardware is read by the driver via the SCLP
26hardware interface. The second part is just copied from the non overwritten real 26hardware interface. The second part is just copied from the non overwritten real
27memory. 27memory.
@@ -32,7 +32,7 @@ SCSI disk.
32 32
33To build a zfcpdump kernel use the following settings in your kernel 33To build a zfcpdump kernel use the following settings in your kernel
34configuration: 34configuration:
35 * CONFIG_ZFCPDUMP=y 35 * CONFIG_CRASH_DUMP=y
36 * Enable ZFCP driver 36 * Enable ZFCP driver
37 * Enable SCSI driver 37 * Enable SCSI driver
38 * Enable ext2 and ext3 filesystems 38 * Enable ext2 and ext3 filesystems