imr_read(9)

💖 NAME 💖

okay so bestie, this is imr_read(9) from the Kernel API Manual, and it does exactly what the name says: it will read an IMR at a given index. iconic. 💅

✨ SYNOPSIS ✨

int imr_read (struct imr_device *idev , u32 imr_id , struct imr_regs
       *imr );

🎀 ARGUMENTS 🎀

• idev — pointer to the imr_device structure. literally the device context, bestie.
• imr_id — the IMR entry to read. this is the one you're asking for. 👑
• imr — the IMR structure representing address and access masks. that's the structure involved here, no cap.

🦋 DESCRIPTION 🦋

This one requires the caller to hold the imr mutex. like, that's the whole vibe check: you gotta have that mutex held before you call it. not optional, bestie. 🔒

🌸 RETURN 🌸

Returns 0 on success, or an error code passed from mbi_iosf on failure. so if it's not 0, the failure tea came straight from mbi_iosf. 😭

🌈 SEE ALSO 🌈

Kernel file ./arch/x86/platform/intel-quark/imr.c — that's the source file, bestie. go peek at these too:

• imr_is_enabled(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)

okay that's the whole page, periodt. 🫶 source/version tea: ./arch/x86/platform/intel-quark, dated October 2026 — imr_read(9) signing off, mwah. 💖✨