get_crash_memory_ranges(9)
π get_crash_memory_ranges(9) π
okay so bestie, welcome to this lil page from the Kernel API Manual β itβs giving kernel-core realness and Iβm obsessed. Letβs get into it β¨
β¨ NAME β¨
get_crash_memory_ranges β gets the crash memory ranges. The list includes the first/crashing kernelβs memory regions that would be exported via an elfcore. π
π SYNOPSIS π
int get_crash_memory_ranges (struct crash_mem **mem_ranges );
π«Ά ARGUMENTS π«Ά
mem_rangesβ the range list youβre adding the memory ranges to. Thatβs the whole assignment, bestie π«Ά
π DESCRIPTION π
fr fr, it returns 0 on success and a negative errno on error. No cap. π
π SEE ALSO π
Kernel file to check out: ./arch/powerpc/kexec/ranges.c
And the whole SEE ALSO friend group is:
get_max_nr_ranges(9)get_mem_rngs_size(9)__add_mem_range(9)__merge_memory_ranges(9)sort_memory_ranges(9)realloc_mem_ranges(9)add_mem_range(9)add_tce_mem_ranges(9)add_initrd_mem_range(9)add_htab_mem_range(9)add_kernel_mem_range(9)add_rtas_mem_range(9)add_opal_mem_range(9)add_reserved_mem_ranges(9)get_reserved_memory_ranges(9)get_exclude_memory_ranges(9)get_usable_memory_ranges(9)
okay thatβs the whole vibe β this page is from ./arch/powerpc/kexec and itβs dated October 2026. bye bestie, slay your kernel debugging π«Άπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms