guest_force_mtrr_state(9)

okay so bestie, this is the guest_force_mtrr_state(9) page from the Kernel API Manual ✨ it’s literally all about setting static MTRR state for a guest, and it has major “you get one shot” energy 💅

💖 NAME 💖

guest_force_mtrr_state — set static MTRR state for a guest 🎀 that’s the whole vibe. no cap.

🌸 SYNOPSIS 🌸

void guest_force_mtrr_state (struct mtrr_var_range *var , unsigned int
       num_var , mtrr_type def_type );

🦋 ARGUMENTS 🦋

• var — the MTRR variable range array to use 💖
• num_var — length of the var array
• def_type — default caching type

✨ DESCRIPTION ✨

so guest_force_mtrr_state is how you set MTRR state via different means — e.g. with data obtained from a hypervisor 🧚 it is allowed only for special cases when you’re running virtualized.

it must be called from the x86_init.hyper.init_platform hook. not a suggestion, bestie — that’s the rule 🫶

😭 one call only! this function can be called only once, and the MTRR state can’t be changed afterwards. to ensure that stays true, X86_FEATURE_MTRR is cleared 💀

🔥 SEE ALSO 🔥

• kernel file ./arch/x86/kernel/cpu/mtrr/generic.c
• mtrr_type_lookup(9)
• set_fixed_range(9)
• generic_get_free_region(9)
• set_fixed_ranges(9)
• set_mtrr_state(9)
• generic_set_mtrr(9)

okay that’s the whole page, bestie! source/version: ./arch/x86/kernel/cpu/mtrr; date: October 2026; page: guest_force_mtrr_state(9) — slay and stay iconic 💅✨👑🌈