imr_remove_range(9)

💅 imr_remove_range 💅

okay so bestie, quick vibe check: this page is imr_remove_range(9) from the Kernel API Manual, and it's literally the "yeet an Isolated Memory Region by its address" function. Let's get into it 🎀

---

✨ NAME ✨

imr_remove_range — delete an Isolated Memory Region by address 🗑️

---

🦋 SYNOPSIS 🦋

int imr_remove_range (phys_addr_t base , size_t size );

---

🌸 ARGUMENTS 🌸

• base — the physical base address of the region, and heads up, it has to be aligned to 1 KiB. no cap, alignment is the whole vibe here 🔥
• size — the physical size of the region in bytes, also aligned to 1 KiB. yes bestie, also 1 KiB. they match, it's giving coordinated 💅

---

👑 DESCRIPTION 👑

So what does this icon actually do? It lets you delete an IMR by an address range, specified by base and size respectively. Like:

imr_remove_range(base, size); — deletes the IMR from base to base+size.

that's it, that's the whole main character moment 🫶 literally just: give it a start, give it a length, region goes bye ✨

---

⭐ RETURN ⭐

• -EINVAL — on an invalid range, or an out of range id 😭 (yes, the original says "out or range id", we're keeping the energy)
• -ENODEV — if reg is valid but no IMR exists, or if it's locked 🔒
• 0 — on success, slay 💖

---

🧚 SEE ALSO 🧚

Kernel file ./arch/x86/platform/intel-quark/imr.c — and honestly the whole friend group:

• imr_is_enabled(9)
• imr_read(9)
• imr_write(9)
• imr_dbgfs_state_show(9)
• imr_debugfs_register(9)
• imr_check_params(9)
• imr_raw_size(9)
• imr_address_overlap(9)
• imr_add_range(9)
• __imr_remove_range(9)
• imr_clear(9)
• imr_fixup_memmap(9)
• imr_init(9)

---

ok that's the whole page bestie, go forth and remove some ranges responsibly 💜

and that's a wrap 🌈 this whole thing lives at ./arch/x86/platform/intel-quark, dated October 2026 — mwah, bye 🍓