resctrl_arch..._config_read(9)

🎀 resctrl_arch..._config_read(9) — from the Kernel API Manual 🎀

okay bestie, buckle up, because we're reading the config for an event and honestly? it's giving "small function, big responsibilities" ✨

---

🌸 NAME 🌸

resctrl_arch_mon_event_config_read — literally just reads the config for an event. that's it. that's the vibe 💅

---

💖 SYNOPSIS 💖

void resctrl_arch_mon_event_config_read (void *config_info );

(the space before the closing paren is canonical, do not come for it 🙈)

---

🦋 ARGUMENTS 🦋

• config_info — a struct resctrl_mon_config_info that's out here describing the resource, the domain, and the event. like a little trio. a friend group. the whole context, basically 🫶

---

✨ DESCRIPTION ✨

okay so here's the tea 🔥 — this function reads resource, domain, and eventid from config_info, then reads the hardware config value into config_info->mon_config. in and out. very main character energy 👑

and the way it gets called?? via IPI — an inter-processor interrupt, no cap — so it can reach a CPU that's a member of the specified domain. you can't just waltz up to any CPU, you have to summon the right one 😭 it's giving long-distance relationship with a specific core.

heads up bestie: the CPU you land on must be a member of the domain you specified. that's the whole plot. iykyk 💀

---

💜 SEE ALSO 💜

like, the entire friend group 🫶 — all of these live in the kernel file ./include/linux/resctrl.h:

• enum resctrl_conf_type(9)
• struct resctrl_staged_config(9)
• struct rdt_domain_hdr(9)
• struct rdt_ctrl_domain(9)
• struct mbm_cntr_cfg(9)
• struct rdt_l3_mon_domain(9)
• struct resctrl_cache(9)
• enum membw_throttle_mode(9)
• struct resctrl_membw(9)
• enum resctrl_schema_fmt(9)
• struct resctrl_mon(9)
• struct rdt_resource(9)
• struct resctrl_schema(9)
• resctrl_arch_sync_cpu_closid_rmid(9)
• resctrl_get_default_ctrl(9)
• resctrl_arch_mon_event_config_write(9)
• resctrl_arch_mbm_cntr_assign_enabled(9)
• resctrl_arch_mbm_cntr_assign_set(9)
• resctrl_arch_rmid_read(9)
• resctrl_arch_rmid_read_context_check(9)
• resctrl_find_domain(9)
• resctrl_arch_reset_rmid(9)
• resctrl_arch_reset_rmid_all(9)
• resctrl_arch_reset_all_ctrls(9)
• resctrl_arch_config_cntr(9)
• resctrl_arch_cntr_read(9)
• resctrl_arch_reset_cntr(9)
• resctrl_arch_io_alloc_enable(9)
• resctrl_arch_get_io_alloc_enabled(9)

(yes, resctrl_arch_mon_event_config_write is right there. she's the twin sister. read/write duo. iconic 🎀)

---

okay that's the whole page, bestie, you ate that 🍓💅

sign-off szn 🧚‍♀️: this little icon lives in ./include/linux, dated October 2026, and yes, the manual page itself literally calls itself resctrl_arch..._config_read(9) — the ellipsis is part of the name, she's mysterious like that 🌈💜