rproc_cored...stom_segment(9)

📦 version 7.3.1, in nixpkgs unstable

💅 rproc_coredump_add_custom_segment(9)

okay so bestie, welcome to the Kernel API Manual ✨ this one is a whole function, it lives in the kernel, and it's about teaching the remote processor coredump machinery where your extra memory lives. it's giving "plumbing but make it cute" 🫶

🌸 NAME 🌸

rproc_coredump_add_custom_segment — add custom coredump segment 💖

like. literally. it adds a custom coredump segment. that's the whole vibe.

🎀 SYNOPSIS 🎀

int rproc_coredump_add_custom_segment (struct rproc *rproc , dma_addr_t
da , size_t size , void (*dumpfn)(struct rproc *rproc, struct
rproc_dump_segment *segment, void *dest, size_t offset, size_t size) ,
void *priv );

five things go in. one int comes out. slay. ✨

🦋 ARGUMENTS 🦋

  • rproc — handle of a remote processor 💫 (yes, the handle, the actual one, the whole remote processor)
  • da — device address 🏠 (where the segment lives on the device side, iykyk)
  • size — size of segment 📏 (how big it is, in the usual size-y units)
  • dumpfn — custom dump function called for each segment during coredump 🔥 signature is void (*dumpfn)(struct rproc *rproc, struct rproc_dump_segment *segment, void *dest, size_t offset, size_t size) — copy it exactly, no cap
  • priv — private data 🙈 (your little bag of secrets, handed straight back to you)

🌈 DESCRIPTION 🌈

okay so here's the tea ☕ — this function adds device memory to the list of segments that get included in the coredump. and it doesn't just dump it there like a random; it associates that segment with the custom dump function you passed in (dumpfn), and with your private data (priv) too. the way it hooks them all up together?? obsessed. 💅

so: device memory → the coredump segment list → your dumpfn → your priv. iconic behavior, honestly.

⭐ RETURN ⭐

  • 0 on success 🎉 (yay)
  • negative errno on error 😭 (not yay, check your errno)

👑 SEE ALSO 👑

the whole friend group fr fr 🫶

💀 reminder that the return is 0 for success and negative errno for error — do not get it twisted, check it every time, periodt.

and that's the page!! 🎀 it's from ./drivers/remoteproc, dated October 2026, and the manual name is Kernel API Manual in case you forgot already — mwah, go dump some coredumps 💜🧚‍♀️

📦 where this page comes from