Searched refs:vmcore (Results 1 – 16 of 16) sorted by relevance
21 of the /proc/vmcore interface. This interface exports the crashed system's24 is needed by /proc/vmcore. The tail part of the crashed systems memory which42 reads from /proc/vmcore or zcore/mem and writes the system dump to a SCSI disk.
301 struct vmcore *m = NULL; in __read_vmcore()554 struct vmcore *m; in mmap_vmcore()676 static struct vmcore* __init get_new_element(void) in get_new_element()678 return kzalloc(sizeof(struct vmcore), GFP_KERNEL); in get_new_element()685 struct vmcore *m; in get_vmcore_size()1087 struct vmcore *new; in process_ptload_program_headers_elf64()1130 struct vmcore *new; in process_ptload_program_headers_elf32()1169 struct vmcore *m; in set_vmcore_list_offsets()1572 struct vmcore *m; in vmcore_cleanup()1574 m = list_first_entry(&vmcore_list, struct vmcore, list); in vmcore_cleanup()
33 proc-$(CONFIG_PROC_VMCORE) += vmcore.o
42 bool "/proc/vmcore support"61 as ELF notes to /proc/vmcore. You can still disable device
23 struct vmcore { struct
8 the system is booted to capture the vmcore using FADump.
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore20 interface while reading /proc/vmcore.83 - User-space tools will read /proc/vmcore to obtain the contents194 Used by second /proc/vmcore206 Currently the dump will be copied from /proc/vmcore to a new file upon207 user intervention. The dump data available through /proc/vmcore will be268 be handled and vmcore will not be captured. This interface can be360 correct data before it gets exported through /proc/vmcore. The current
12 space as part of ELF note in /proc/vmcore file. This note
31 the system is booted to capture the vmcore using FADump.
52 /proc/vmcore. This exports the dump as an ELF-format file that you can171 2) Enable "/proc/vmcore support" under "Filesystems" -> "Pseudo filesystems"::191 CPU is enough for kdump kernel to dump vmcore on most of systems.466 headers. This is necessary because GDB currently cannot open vmcore files534 cp /proc/vmcore <dump-file>539 makedumpfile -l --message-level 1 -d 31 /proc/vmcore <dump-file>547 /proc/vmcore. Use the debug vmlinux built with -g and run the following
22 find the corresponding vmlinux in order to process vmcore.
9 Instead it's reading directly from ``/proc/kcore`` or vmcore and pretty prints
809 is useful to define the root cause of RCU stalls using a vmcore.
18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore
3308 append dump data to vmcore so you can collect driver
10132 F: fs/proc/vmcore.c10135 F: include/uapi/linux/vmcore.h
