pseudo_lock_init(9)

💖 pseudo_lock_init(9) 💖

okay so welcome to the Kernel API Manual, bestie — we're talking about pseudo_lock_init, and it's genuinely a little main-character moment in the resctrl pseudo-locking lore. 🦋

✨ NAME ✨

pseudo_lock_init — Initialize a pseudo-lock region 💅

🦋 SYNOPSIS 🦋

int pseudo_lock_init (struct rdtgroup *rdtgrp );

🫶 ARGUMENTS 🫶

• rdtgrp — the resource group to which the new pseudo-locked region will belong. Like, that's its home base, no cap. 🏡

🌸 DESCRIPTION 🌸

okay so real talk: a pseudo-locked region is associated with a resource group. When this association is created, the pseudo-locked region is initialized. But at this exact moment the details of the pseudo-locked region are not known yet — so the only things going down are allocation and establishing the association. That's the whole vibe: it's giving "we'll flesh out the deets later" energy, and honestly? valid. ✨

💀 RETURN 💀

• 0 on success 🎉
• <0 on failure 😭

Zero is the slay outcome; negative is the not-so-slay outcome. Periodt. 💅

👑 SEE ALSO 👑

Kernel file ./fs/resctrl/pseudo_lock.c is the home base, and the rest of the SEE ALSO crew is:

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

Bye bestie! This page is from the ./fs/resctrl source, dated October 2026, and it's all for pseudo_lock_init(9) 🫶✨💅