ne_sanity_c...s_mem_region(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ne_sanity_check_phys_mem_region πŸ’–

okay so welcome to the Kernel API Manual, bestie β€” this is the page for ne_sanity_c...s_mem_region(9) (yes, the header title is literally doing that truncated thing), and the actual function is ne_sanity_check_phys_mem_region. It’s giving β€œtiny but important sanity check” energy, and we’re gonna cover every single detail. 🫢

🌸 NAME 🌸

ne_sanity_check_phys_mem_region β€” sanity check the start address and the size of a physical memory region. Literally checking the start address and size of a physical memory region, no cap.

✨ SYNOPSIS ✨

int ne_sanity_check_phys_mem_region (u64 phys_mem_region_paddr , u64
phys_mem_region_size );

πŸŽ€ ARGUMENTS πŸŽ€

  • phys_mem_region_paddr β€” physical start address of the region to be sanity checked. The literal start paddr, bestie.
  • phys_mem_region_size β€” length of the region to be sanity checked. The size, the amount, the whole region length.

πŸ¦‹ CONTEXT πŸ¦‹

Process context. This function is called with the ne_enclave mutex held β€” so yeah, mutex held, that’s the vibe. πŸ’…

πŸ”₯ RETURN πŸ”₯

  • 0 on success. Slay.
  • Negative return value on failure. A negative number means it did not pass the vibe check.

πŸ‘‘ SEE ALSO πŸ‘‘

Go read these next, iykyk:


that’s the whole page, bestie πŸ’– source/version: ./drivers/virt/nitro_enclaves, dated October 2026, hanging out in the Kernel API Manual under ne_sanity_c...s_mem_region(9). mwah 🫢✨

πŸ“¦ where this page comes from