STRUCT SLOT_ADD_MEM_REQ(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 struct slot_add_mem_req(9) 🌸

okay so bestie, welcome to the Kernel API Manual β€” yes, the actual manual name, we're being official today πŸ’… β€” and today's main character is struct slot_add_mem_req. It's giving "small struct, big job" energy, ngl.


✨ NAME ✨

struct slot_add_mem_req β€” the SLOT_ADD_MEM request. that's it, that's the whole name, periodt. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the whole vibe, literally copy-pasted from the source of truth so you can't mess it up:

struct slot_add_mem_req {
    u64 slot_uid;
    u64 paddr;
    u64 size;
 };

three little u64s, all in a row, iconic behavior honestly πŸ”₯


πŸ’– Members πŸ’–

let's meet the cast, one by one 🫢

  • slot_uid β€” the slot's unique id, mapped to the slot you're adding that memory region to. it's the "which slot tho" field, iykyk.
  • paddr β€” the physical address of the memory region you're adding to the slot. not virtual, not vibes β€” physical πŸ’€
  • size β€” the memory size, in bytes, of the memory region going into the slot. bytes, bestie, always bytes.

πŸ‘‘ SEE ALSO πŸ‘‘

the friend group, the whole squad, the extended universe 🌈 β€” all of these are (9) man pages and all of these are real, don't @ me:

like, that's a lot of references and every single one is staying, no cap πŸ’œ


nerd note: this whole page lives under ./drivers/virt/nitro_enclaves, and it's dated October 2026. yes, the future. we're early. 🧚

and that's the page, bestie β€” go add that memory, slay, and remember: slot_uid, paddr, size, in that order. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from