STRUCT MINIDUMP_REGION(9)

💖 struct minidump_region(9) 💖

okay bestie, gather round, because this one's from the Kernel API Manual and it's literally the glow-up era of dump metadata 🎀 Say hi to struct minidump_region — she's the little struct that tells everyone which region is getting dumped. Main character energy, no cap.

---

✨ NAME ✨

struct minidump_region — Minidump region. That's it, that's the whole vibe. 🦋

---

🌸 SYNOPSIS 🌸

Here's the actual fit she's wearing, copy-pasted straight from the source so you know it's fr fr:

struct minidump_region {
    char name[MAX_REGION_NAME_LENGTH];
    __le32 seq_num;
    __le32 valid;
    __le64 address;
    __le64 size;
 };

the way she's got two __le32s and two __le64s... consistent queen 💅

---

🫶 Members 🫶

okay let's meet the cast, one field at a time:

• name — name of the region to be dumped. it's a lil char array that maxes out at MAX_REGION_NAME_LENGTH, so keep it cute and keep it short 🍓
• seq_num — the tiebreaker bestie!! you use this to tell apart regions that have the same name. two regions, one name? seq_num said "not on my watch" 😭
• valid — the vibe check. this entry gets dumped if it's set to 1. set it to 1 = she's going. anything else = she's not. iconic gatekeeping behavior fr 💀
• address — physical address of the region to be dumped. physical, bestie, not virtual 🧚
• size — size of the region. how much of her there is 💜

---

🔥 SEE ALSO 🔥

go read the kernel file ./drivers/remoteproc/qcom_common.c for the lore, and then go touch grass by reading all her friends too:

• struct minidump_subsystem(9)
• struct minidump_global_toc(9)
• qcom_add_glink_subdev(9)
• qcom_remove_glink_subdev(9)
• qcom_register_dump_segments(9)
• qcom_add_smd_subdev(9)
• qcom_remove_smd_subdev(9)
• qcom_register_ssr_notifier(9)
• qcom_unregister_ssr_notifier(9)
• qcom_add_ssr_subdev(9)
• qcom_remove_ssr_subdev(9)
• qcom_add_pdm_subdev(9)
• qcom_remove_pdm_subdev(9)

that's a whole friend group, and yes they all showed up to the group chat 🌈

---

lowkey reminder: keep those field names and types exactly as written up there. kernel structs don't do "close enough" 🙈

okay that's the page!! it lives in ./drivers/remoteproc, dated October 2026, and she answers to struct minidump_region(9) — go dump responsibly, bestie, ily, mwah 💅✨👑