rdtgroup_cb...seudo_locked(9)

🌸 NAME 🌸

Okay bestie, welcome to the rdtgroup_cb...seudo_locked(9) page from the Kernel API Manual — we're doing kernel API lore today and it's lowkey iconic ✨💅

rdtgroup_cbm_overlaps_pseudo_locked — Test if CBM or portion is pseudo-locked. That's the whole name, no cap 🎀

---

✨ SYNOPSIS ✨

Look at this signature, bestie:

bool rdtgroup_cbm_overlaps_pseudo_locked (struct rdt_ctrl_domain *d ,
unsigned long cbm );

---

🫶 ARGUMENTS 🫶

Here's the cast of characters:

• d — RDT domain. The domain in question, periodt.
• cbm — CBM to test. Literally the bitmask under the vibe check.

---

💖 DESCRIPTION 💖

K so d represents a cache instance, and cbm is a capacity bitmask that is considered for it. The quest: determine if cbm overlaps with any existing pseudo-locked region on d. ✨

Important little detail, fr fr: cbm is unsigned long, even if only 32 bits are used, to make the bitmap functions work correctly. That's not me being extra; that's literally the reason 💅

---

🦋 RETURN 🦋

true if cbm overlaps with pseudo-locked region on d, false otherwise. Periodt. 💖

---

👑 SEE ALSO 👑

The kernel file is ./fs/resctrl/pseudo_lock.c, and here's the whole SEE ALSO squad, no one left behind:

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

---

That's the page, bestie! Source/version: ./fs/resctrl; date: October 2026; page title: rdtgroup_cb...seudo_locked(9). Mwah 💋🎀