rdtgroup_mon..._in_progress(9)

💅 rdtgroup_monitor_in_progress(9) — the kernel API manual, but make it make sense

okay so bestie, welcome to the kernel API manual page for rdtgroup_monitor_in_progress — that's section 9, the kernel-API girlies section 🎀 this one lives in ./fs/resctrl land and it's lowkey a one-trick pony, but she serves her purpose flawlessly. periodt.

---

✨ NAME ✨

rdtgroup_monitor_in_progress — literally just tests whether monitoring is in progress 🕵️‍♀️✨

---

🌸 SYNOPSIS 🌸

int rdtgroup_monitor_in_progress (struct rdtgroup *rdtgrp );

that's it. that's the whole vibe check. 🦋

---

💖 ARGUMENTS 💖

• rdtgrp — the resource group being queried 🎀 this is the group you're asking about, bestie, so make sure it's the right one before you go poking at it, iykyk.

---

🔥 RETURN 🔥

it hands you back 1 if monitor groups have been created for this resource group, and 0 otherwise 🌈 simple as that, no cap.

so like — 1 = yes queen, monitoring's happening 💅 and 0 = nope, nothing going on here 🙈

---

👑 SEE ALSO 👑

fr fr go read these too, they're all in the kernel file ./fs/resctrl/pseudo_lock.c and they're all iconic in their own way:

• pseudo_lock_minor_get(9)
• pseudo_lock_minor_release(9)
• region_find_by_minor(9)
• struct pseudo_lock_pm_req(9)
• pseudo_lock_cstates_constrain(9)
• pseudo_lock_region_clear(9)
• pseudo_lock_region_init(9)
• pseudo_lock_init(9)
• pseudo_lock_region_alloc(9)
• pseudo_lock_free(9)
• rdtgroup_locksetup_user_restrict(9)
• rdtgroup_locksetup_user_restore(9)
• rdtgroup_locksetup_enter(9)
• rdtgroup_locksetup_exit(9)
• rdtgroup_cbm_overlaps_pseudo_locked(9)
• rdtgroup_pseudo_locked_in_hierarchy(9)
• pseudo_lock_measure_cycles(9)
• rdtgroup_pseudo_lock_create(9)
• rdtgroup_pseudo_lock_remove(9)

---

🫶 reminder to my favorite reader: this page lives at ./fs/resctrl, and it's dated October 2026 — so yes, we're being documented by future girlies 💜 and the kernel API manual section is rdtgroup_mon..._in_progress(9), which is a whole mouthful but we love her anyway. mwah 💋✨