rdtgroup_pseudo_lock_remove(9)

💅 rdtgroup_pseudo_lock_remove(9) — like, the Kernel API Manual entry you've been waiting for 🎀

okay bestie, gather round, because this one is a whole little function and it's genuinely kind of iconic in a "yes i do exactly one thing" way. no cap. ✨

---

✨ NAME ✨

rdtgroup_pseudo_lock_remove — Remove a pseudo-locked region 🫶

---

🌸 SYNOPSIS 🌸

void rdtgroup_pseudo_lock_remove (struct rdtgroup *rdtgrp );

that's it. that's the whole signature. it returns void and it does not play about. 💀

---

🦋 ARGUMENTS 🦋

• rdtgrp — the resource group to which the pseudo-locked region belongs. like, the actual group that owns the thing, ok? that's the one you hand over. 💖

---

👑 DESCRIPTION 👑

okay so here's the vibe: you can kick off the removal of a pseudo-locked region in literally two ways, and both of them are "the resource group is going away":

• the resource group gets removed from user space via a "rmdir" from userspace, or
• the resctrl filesystem gets unmounted. 🧚

and here's the part that's giving asymmetry — on removal, the resource group does not go back to pseudo-locksetup mode before it is removed. nope. it is removed directly, no little detour back through setup mode, no goodbye lap. 😭

so there's this asymmetry with the creation path, and it's lowkey the whole personality of this function: the struct pseudo_lock_region is removed here, while it was not created in rdtgroup_pseudo_lock_create. so the create side didn't make it, but the remove side absolutely does delete it. the way that this is just how it works and we all accept it 💅✨

fr fr bestie, keep that asymmetry in mind — it's not a bug you should "fix" in your head, it's just the documented shape of things. 🙈

---

⭐ RETURN ⭐

void

(no return value. it gives nothing and that's the point. queen behaviour.) 👑

---

🌈 SEE ALSO 🌈

the kernel file is ./fs/resctrl/pseudo_lock.c and honestly the whole girliepop extended universe is here, so let's go, in order:

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

iykyk, that's the whole friend group 🫶💜

---

aaaand we're done!! this page lives in ./fs/resctrl, it's dated October 2026, and it's literally titled rdtgroup_pseudo_lock_remove(9) — slay, go read the others now, mwah 💋💖🎀