rproc_coredump_add_segment(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– rproc_coredump_add_segment β€” the Kernel API Manual, section 9, bestie πŸ’–

Okay so this is a Linux kernel API page from the Kernel API Manual, section 9, and it's literally about telling the remoteproc subsystem "hey, this chunk of device memory? put it in the coredump, mkay?" πŸŽ€


✨ NAME ✨

rproc_coredump_add_segment β€” add segment of device memory to coredump


🌸 SYNOPSIS 🌸

int rproc_coredump_add_segment (struct rproc *rproc , dma_addr_t da ,
       size_t size );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • rproc β€” handle of a remote processor πŸ‘‘ (this is your main character, the remote proc itself)
  • da β€” device address πŸ’… (the address, on the device side, of the memory you're talking about)
  • size β€” size of segment πŸ“ (how big that chunk is, obviously)

✨ DESCRIPTION ✨

So basically, this function adds device memory to the list of segments that are gonna be included in a coredump for the remoteproc. That's it. That's the whole vibe. 🫢

You're building up the roster of memory regions, and each call to this adds one more segment to the squad. When the coredump happens, everything you registered is along for the ride. πŸ’œ


🌈 RETURN 🌈

  • 0 on success ⭐ β€” slay, it worked
  • negative errno on error 😭 β€” something went wrong, and the error code is negative, as errno codes are

πŸ”₯ SEE ALSO πŸ”₯

Go read those too, bestie, they're all part of the same coredump friend group πŸ’–


ngl the whole coredump pipeline is lowkey iconic β€” this function is just one little piece of it, but every segment counts 🧚

Mwah πŸ’‹ β€” this page came from ./drivers/remoteproc, dated October 2026, and it's the rproc_coredump_add_segment(9) page from the Kernel API Manual. Periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from