Commit ffa52d02 authored by Martin Schwidefsky's avatar Martin Schwidefsky

s390/zcore: remove /sys/kernel/debug/zcore/mem

New versions of the SCSI dumper use the /dev/vmcore interface instead
of zcore mem. Remove the outdated interface.
Acked-by: default avatarMichael Holzheu <holzheu@linux.vnet.ibm.com>
Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
parent bbfed511
...@@ -15,19 +15,15 @@ the s390-tools package) to make the device bootable. The operator of a Linux ...@@ -15,19 +15,15 @@ the s390-tools package) to make the device bootable. The operator of a Linux
system can then trigger a SCSI dump by booting the SCSI disk, where zfcpdump system can then trigger a SCSI dump by booting the SCSI disk, where zfcpdump
resides on. resides on.
The kernel part of zfcpdump is implemented as a debugfs file under "zcore/mem", The user space dump tool accesses the memory of the crashed system by means
which exports memory and registers of the crashed Linux in an s390 of the /proc/vmcore interface. This interface exports the crashed system's
standalone dump format. It can be used in the same way as e.g. /dev/mem. The memory and registers in ELF core dump format. To access the memory which has
dump format defines a 4K header followed by plain uncompressed memory. The been saved by the hardware SCLP requests will be created at the time the data
register sets are stored in the prefix pages of the respective CPUs. To build a is needed by /proc/vmcore. The tail part of the crashed systems memory which
dump enabled kernel with the zcore driver, the kernel config option has not been stashed by hardware can just be copied from real memory.
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 To build a dump enabled kernel the kernel config option CONFIG_CRASH_DUMP
hardware interface. The second part is just copied from the non overwritten real has to be set.
memory.
Since kernel version 3.12 also the /proc/vmcore file can also be used to access
the dump.
To get a valid zfcpdump kernel configuration use "make zfcpdump_defconfig". To get a valid zfcpdump kernel configuration use "make zfcpdump_defconfig".
......
...@@ -35,7 +35,6 @@ struct save_area { ...@@ -35,7 +35,6 @@ struct save_area {
struct save_area_ext { struct save_area_ext {
struct save_area sa; struct save_area sa;
__vector128 vx_regs[32]; __vector128 vx_regs[32];
u64 vx_sa_addr;
}; };
struct _lowcore { struct _lowcore {
......
...@@ -30,9 +30,7 @@ obj-$(CONFIG_S390_TAPE_3590) += tape_3590.o ...@@ -30,9 +30,7 @@ obj-$(CONFIG_S390_TAPE_3590) += tape_3590.o
obj-$(CONFIG_MONREADER) += monreader.o obj-$(CONFIG_MONREADER) += monreader.o
obj-$(CONFIG_MONWRITER) += monwriter.o obj-$(CONFIG_MONWRITER) += monwriter.o
obj-$(CONFIG_S390_VMUR) += vmur.o obj-$(CONFIG_S390_VMUR) += vmur.o
obj-$(CONFIG_CRASH_DUMP) += sclp_sdias.o zcore.o
zcore_mod-objs := sclp_sdias.o zcore.o
obj-$(CONFIG_CRASH_DUMP) += zcore_mod.o
hmcdrv-objs := hmcdrv_mod.o hmcdrv_dev.o hmcdrv_ftp.o hmcdrv_cache.o diag_ftp.o sclp_ftp.o hmcdrv-objs := hmcdrv_mod.o hmcdrv_dev.o hmcdrv_ftp.o hmcdrv_cache.o diag_ftp.o sclp_ftp.o
obj-$(CONFIG_HMC_DRV) += hmcdrv.o obj-$(CONFIG_HMC_DRV) += hmcdrv.o
This diff is collapsed.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment