path: root/Documentation/s390
diff options
authorMichael Holzheu <>2014-04-14 10:38:05 +0200
committerMartin Schwidefsky <>2014-05-20 08:58:43 +0200
commitbf28a5970de3a349ec05cea45ca5272404b6609f (patch)
treeba85463fb15d90612f5246e015d02643ca02e1f2 /Documentation/s390
parent71c40f7f8fe1d06ed1e1eafdcf56345eb8c17bf2 (diff)
s390/dump: Remove CONFIG_ZFCPDUMP
Currently there are two s390 kernel dump config options "CONFIG_ZFCPDUMP" and "CONFIG_CRASH_DUMP". In order to keep things simple and because the "CONFIG_ZFCPDUMP" option already has a dependency to "CONFIG_CRASH_DUMP" remove the CONFIG_ZFCPDUMP option. Signed-off-by: Michael Holzheu <> Reviewed-by: Eric Farman <> Signed-off-by: Martin Schwidefsky <>
Diffstat (limited to 'Documentation/s390')
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
dump format defines a 4K header followed by plain uncompressed memory. The
register sets are stored in the prefix pages of the respective cpus. To build a
dump enabled kernel with the zcore driver, the kernel config option
-CONFIG_ZFCPDUMP has to be set. When reading from "zcore/mem", the part of
+CONFIG_CRASH_DUMP has to be set. When reading from "zcore/mem", the part of
memory, which has been saved by hardware is read by the driver via the SCLP
hardware interface. The second part is just copied from the non overwritten real
@@ -32,7 +32,7 @@ SCSI disk.
To build a zfcpdump kernel use the following settings in your kernel
* Enable ZFCP driver
* Enable SCSI driver
* Enable ext2 and ext3 filesystems