memblock_mark_hotplug(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– memblock_mark_hotplug πŸ’–

okay bestie, welcome to the memblock_mark_hotplug(9) page β€” that's a section 9 kernel API manual entry, so get comfy because we're in kernel-nerd territory and honestly? it's giving main character energy 🌈


✨ NAME ✨

memblock_mark_hotplug β€” marks hotpluggable memory with the flag MEMBLOCK_HOTPLUG. that's it, that's the whole job, and she does it slayfully πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int __init_memblock memblock_mark_hotplug (phys_addr_t base ,
phys_addr_t size );

look at her. int return, __init_memblock, takes a base and a size. iconic signature, no notes ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • base β€” the base phys addr of the region πŸ’– so like, where the region starts, physically
  • size β€” the size of the region 🌸 how much of it there is, starting from base

⭐ RETURN ⭐

  • 0 on success 🫢 (we love a zero)
  • -errno on failure 😭 (classic kernel move β€” negative errno, no cap)

πŸ”₯ SEE ALSO πŸ”₯

okay this list is LONG and she ate, so buckle up bestie, we're going through the whole squad πŸ‘‘


and that's the whole page, bestie πŸ§šπŸ’œ tysm for reading, mwah β€” this one came from ./mm and it's dated October 2026, so like, future-core of it all β­πŸ¦‹ see u in the next manpage, iykyk πŸ’€πŸŽ€

πŸ“¦ where this page comes from