memblock_isolate_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… memblock_isolate_range(9) πŸ’…

okay bestie, welcome to the Kernel API Manual page for memblock_isolate_range(9) β€” manual name folded in right here, no boring header-line copy-paste energy. This one is about carving a range out of a memblock type so the regions don’t cross the edges. Slay. 🧚

🌸 NAME 🌸

memblock_isolate_range β€” isolate given range into disjoint memblocks.

✨ SYNOPSIS ✨

the signature, verbatim, no edits, no cap:

int __init_memblock memblock_isolate_range (struct memblock_type *type ,
       phys_addr_t base , phys_addr_t size , int *start_rgn , int *end_rgn );

πŸŽ€ ARGUMENTS πŸŽ€

  • type β€” memblock type to isolate range for.
  • base β€” base of range to isolate.
  • size β€” size of range to isolate.
  • start_rgn β€” out parameter for the start of isolated region.
  • end_rgn β€” out parameter for the end of isolated region.

πŸ¦‹ DESCRIPTION πŸ¦‹

Walk type and ensure that regions don’t cross the boundaries defined by [base, base + size). Crossing regions are split at the boundaries, which may create at most two more regions.

The index of the first region inside the range is returned in *start_rgn, and the index of the first region after the range is returned in *end_rgn. periodt πŸ’…

πŸ”₯ RETURN πŸ”₯

0 on success, -errno on failure. that’s the whole vibe check.

πŸ‘‘ SEE ALSO πŸ‘‘

the whole squad, in order, iykyk:


xoxo, source/version bestie: ./mm, dated October 2026 β€” bye bestie! πŸŽ€πŸ’–

πŸ“¦ where this page comes from