imr_is_enabled(9)

💖 imr_is_enabled(9) 💖

okay bestie, welcome to the Kernel API Manual page for imr_is_enabled(9) — this is your go-to vibe check for whether an IMR is enabled, and it is lowkey iconic 🫶✨

🌟 NAME 🌟

imr_is_enabled — true if an IMR is enabled, false otherwise. fr fr, that’s the whole name situation 💅

✨ SYNOPSIS ✨

int imr_is_enabled (struct imr_regs *imr );

🎀 ARGUMENTS 🎀

• imr — pointer to IMR descriptor. yes bestie, it’s a pointer to the descriptor, keep it cute 🎀

🦋 DESCRIPTION 🦋

okay so this function figures out if an IMR is enabled based on the address range and the read/write mask. no cap 🔍

An IMR that’s set with an address range set to zero and a read/write access mask set to all is considered to be disabled. An IMR in any other state — for example, set to zero but without read/write access all — is considered to be enabled. This definition of disabled is how firmware switches off an IMR, and it’s maintained in the kernel for consistency. periodt 💖

🌸 RETURN 🌸

• true if the IMR is enabled
• false if it’s disabled

🔥 SEE ALSO 🔥

• Kernel file: ./arch/x86/platform/intel-quark/imr.c
• 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_remove_range(9)
• imr_clear(9)
• imr_fixup_memmap(9)
• imr_init(9)

mwah 💋 this page is signed off from ./arch/x86/platform/intel-quark, dated October 2026 — go be iconic with your IMR checks, bestie 💅✨