-
Notifications
You must be signed in to change notification settings - Fork 23
Comparison with Other Tools
Petr Tesarik edited this page Nov 29, 2024
·
2 revisions
It would be great if other tools could use this library instead of their own parsing. However, libkdumpfile
lacks some features to make it possible.
Missing for crash
parity:
- alpha
- ia64
- loongarch64
- mips
- mips64
- powerpc
- ppc64
- s390
Missing for makedumpfile
parity:
- ia64
- loongarch64
- mips64
- powerpc
- ppc64
- s390
- sparc64
Missing for crash
parity:
- libvirt QEMU VM
- QEMU VM
- ramdump
- xc_core
- xc_save
Missing for makedumpfile
parity: NOTHING \o/
Makedumpfile currently requires some low-level information parsed from the vmcore ELF headers:
-
get_elf_info()
- differentiate between ELF64 and ELF32
- not available, but is it really needed?
- get number of LOAD segments
- AFAICS only used to iterate over all of RAM
- can be done with the
memory.pagemap
attribute?
- find ELF notes
- all information hopefully stored in attributes?
- find maximum physical address
- see the
max_pfn
attribute
- see the
- differentiate between ELF64 and ELF32
-
get_pt_load()
- used to iterate over all of RAM
- also used to set up physical base on x86_64
- probably not needed if makedumpfile does not have to deal with virtual-to-physical address translation