rdtgroup_ps...in_hierarchy(9)

okay bestie, this is rdtgroup_pseudo_locked_in_hierarchy(9) from the Kernel API Manual — and it's literally the vibe check for whether a cache hierarchy already has a pseudo-locked region in it 🦋💅

✨ NAME ✨

rdtgroup_pseudo_locked_in_hierarchy — Pseudo-locked region in cache hierarchy.

🌸 SYNOPSIS 🌸

bool rdtgroup_pseudo_locked_in_hierarchy (struct rdt_ctrl_domain *d );

🎀 ARGUMENTS 🎀

• d — RDT domain under test. That's the domain we're checking, bestie.

💖 DESCRIPTION 💖

Setting up a pseudo-locked region is not a solo mission: it affects all cache instances within the hierarchy of the region. So it's essential to know whether any pseudo-locked regions already exist within a cache hierarchy, because that's how we prevent any attempts to create new pseudo-locked regions in the same hierarchy. No cap, it's a whole hierarchy-wide situation 🫶

🔥 RETURN 🔥

Returns true if a pseudo-locked region exists in the hierarchy of d, or if it's not possible to test due to a memory allocation issue. Returns false otherwise. Periodt. 💅

🌈 SEE ALSO 🌈

Kernel file: ./fs/resctrl/pseudo_lock.c — go read it, bestie, iykyk 📖✨

• 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)
• pseudo_lock_measure_cycles(9)
• rdtgroup_pseudo_lock_create(9)
• rdtgroup_pseudo_lock_remove(9)

mwah 💋 — this page is from ./fs/resctrl, dated October 2026, and the header title is rdtgroup_ps...in_hierarchy(9). Bye bestie, slay those cache hierarchy checks 🧚💜