rproc_handle_carveout(9)

📦 version 7.3.1, in nixpkgs unstable

💅 rproc_handle_carveout(9) — the Kernel API Manual glow-up 🎀

okay so bestie, we're in the Kernel API Manual and today's main character is rproc_handle_carveout(9). yes that's the whole title. slay. let's get into it ✨

✨ NAME ✨

rproc_handle_carveout — handle phys contig memory allocation requests 💖

like, it handles the requests for physically contiguous memory allocation. that's the vibe check and it passed.

🦋 SYNOPSIS 🦋

int rproc_handle_carveout (struct rproc *rproc , void *ptr , int offset
, int avail );

🌸 ARGUMENTS 🌸

  • rproc — the rproc handle, your main character struct 🫶
  • ptr — the resource entry, aka the thing we're actually looking at
  • offset — offset of the resource entry, so we know where we are in the lineup
  • avail — size of available data (for image validation), lowkey the safety net 👑

🔥 DESCRIPTION 🔥

so this function will handle firmware requests for allocation of physically contiguous memory regions. literally that's the job. no cap 💅

these request entries should come first in the firmware's resource table, bestie, and I mean first — because other firmware entries might request placing other data objects inside these memory regions (e.g. data/code segments, trace resource entries, ...). it's giving "get in line, everyone else waits." 🎀

allocating memory this way helps utilizing the reserved physical memory (e.g. CMA) more efficiently, and it also minimizes the number of TLB entries needed to map it (in case rproc is using an IOMMU). and reducing the TLB pressure is important — it may have a substantial impact on performance. that's not just a vibe, that's fr fr the truth ⭐

ngl the ordering thing matters: carveout entries go up front or the other entries can't nest inside them. don't be the person who puts them last 🙈

🌈 RETURN 🌈

0 on success, or an appropriate error code otherwise. iconic either way 💀

👑 SEE ALSO 👑

kernel file ./drivers/remoteproc/remoteproc_core.c and honestly the whole friend group:

okay that's the whole page, mwah 💋 this one lives in ./drivers/remoteproc and it's dated October 2026 — rproc_handle_carveout(9), forever and always 🧚💜

📦 where this page comes from