Searched refs:vmcore (Results 1 – 9 of 9) sorted by relevance
190 struct vmcore *m = NULL; in __read_vmcore()411 struct vmcore *m; in mmap_vmcore()497 static struct vmcore* __init get_new_element(void) in get_new_element()499 return kzalloc(sizeof(struct vmcore), GFP_KERNEL); in get_new_element()506 struct vmcore *m; in get_vmcore_size()898 struct vmcore *new; in process_ptload_program_headers_elf64()941 struct vmcore *new; in process_ptload_program_headers_elf32()980 struct vmcore *m; in set_vmcore_list_offsets()1187 struct vmcore *m; in vmcore_cleanup()1189 m = list_entry(pos, struct vmcore, list); in vmcore_cleanup()
30 proc-$(CONFIG_PROC_VMCORE) += vmcore.o
40 bool "/proc/vmcore support"
15 - Unlike phyp dump, fadump exports the memory dump through /proc/vmcore19 interface while reading /proc/vmcore.76 -- User-space tools will read /proc/vmcore to obtain the contents143 Used by second /proc/vmcore147 Currently the dump will be copied from /proc/vmcore to a149 /proc/vmcore will be in ELF format. Hence the existing kdump196 be handled and vmcore will not be captured. This interface can be254 correct data before it gets exported through /proc/vmcore. The current
22 struct vmcore { struct
12 space as part of ELF note in /proc/vmcore file. This note
29 Since kernel version 3.12 also the /proc/vmcore file can also be used to access44 reads from /proc/vmcore or zcore/mem and writes the system dump to a SCSI disk.
51 /proc/vmcore. This exports the dump as an ELF-format file that you can161 2) Enable "/proc/vmcore support" under "Filesystems" -> "Pseudo filesystems".313 which means it is possible that the vmcore is not that precise as expected.388 headers. This is necessary because GDB currently cannot open vmcore files447 cp /proc/vmcore <dump-file>456 /proc/vmcore. Use the debug vmlinux built with -g and run the following
103 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore