dprc_reset_container(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dprc_reset_container — the Kernel API Manual page, bestie edition

okay so this is dprc_reset_container(9) from the Kernel API Manual, and honestly? it's giving "cleanup era." it's the routine that tells a child container "hey girl, you're getting reset, wrap it up 🎀". let's get into it.

✨ NAME ✨

dprc_reset_container — Reset child container. that's it, that's the whole vibe.

🦋 SYNOPSIS 🦋

int dprc_reset_container (struct fsl_mc_io *mc_io , u32 cmd_flags , u16
token , int child_container_id , u32 options );

like yes, that's a lot of args, but we're gonna go through every single one, no cap 💜

🌸 ARGUMENTS 🌸

  • mc_io — Pointer to MC portal's I/O object. it's the portal's whole I/O situation, so to speak ✨
  • cmd_flags — Command flags; one or more of MC_CMD_FLAG_. yes, literally that constant, plural flags, pick your faves.
  • token — Token of DPRC object. gotta have the token, iykyk 🔑
  • child_container_id — ID of the container to reset. this is the main character of the whole call ngl 👑
  • options — 32 bit options, and there are exactly two moods:
    • 0 (no bits set) — all the objects inside the container are reset. The child containers are entered recursively and the objects reset. All the objects (including the child containers) are closed. full send, deep clean, everything gets closed out 🧹
    • bit 0 set — all the objects inside the container are reset. However the child containers are not entered recursively. This option is supported for API versions >= 6.5. In case a software context crashes or becomes non-responsive, the parent may wish to reset its resources container before the software context is restarted. so it's the "shallow clean, don't go digging into the children" option 🫶

💖 DESCRIPTION 💖

This routine informs all objects assigned to the child container that the container is being reset, so they may perform any cleanup operations that are needed. All objects handles that were owned by the child container shall be closed. everybody gets the memo, everybody does their little cleanup ritual, and every handle the child container owned gets closed. periodt. 💅

Note that such request may be submitted even if the child software context has not crashed, but the resulting object cleanup operations will not be aware of that.

🫣 lowkey important: you can fire this off even when the child software context hasn't crashed — the call won't stop you — but the cleanup operations that result won't know that's the situation. so it's not gonna magically be aware. just so you know, fr fr.

💀 RETURN 💀

(the original page has nothing listed here — yes, the section exists and yes it's empty, and we're keeping it that way, no notes 🙈)

🌈 SEE ALSO 🌈

Kernel file ./drivers/bus/fsl-mc/dprc.c, plus the whole friend group:

go read those too, they ate 🔥

and that's the page!! sign-off time: this one lives under ./drivers/bus/fsl-mc, dated October 2026, and it's dprc_reset_container(9) all the way through. mwah, go reset something responsibly 🍓💜

📦 where this page comes from