imr_check_params(9)

💅 NAME 💅

okay so this is imr_check_params(9) from the Kernel API Manual, and it's literally the vibe check for a passed address range: it checks IMR alignment and that the size is non-zero. Bestie, that's the whole assignment. 🫶

✨ SYNOPSIS ✨

int imr_check_params (phys_addr_t base , size_t size );

🎀 ARGUMENTS 🎀

• base — the base address of the intended IMR, typed as phys_addr_t. This is the address part of the range being checked. 📍
• size — the size of the intended IMR, typed as size_t. It is supposed to be non-zero, bestie. 📏

🌸 RETURN 🌸

• 0 — the range is valid, no cap. ✅
• -EINVAL — the base or size is unaligned. 🚩

So yes: zero on a valid range, and -EINVAL on an unaligned base/size. That's the whole mood. 💅

🦋 SEE ALSO 🦋

• Kernel file ./arch/x86/platform/intel-quark/imr.c
• imr_is_enabled(9)
• imr_read(9)
• imr_write(9)
• imr_dbgfs_state_show(9)
• imr_debugfs_register(9)
• imr_raw_size(9)
• imr_address_overlap(9)
• imr_add_range(9)
• __imr_remove_range(9)
• imr_remove_range(9)
• imr_clear(9)
• imr_fixup_memmap(9)
• imr_init(9)

cute sign-off: this page's source/version is ./arch/x86/platform/intel-quark, dated October 2026, and the manual page is imr_check_params(9). byeee 👋💜