resctrl_arch_pseudo_lock_fn(9)

✨ resctrl_arch_pseudo_lock_fn ✨

okay so this is a page from the Kernel API Manual bestie, and it's all about resctrl_arch_pseudo_lock_fn — like, the whole entire vibe is "load kernel memory into cache" and honestly? iconic behavior. 💅

---

🌸 NAME 🌸

resctrl_arch_pseudo_lock_fn — load kernel memory into cache, no cap 🧚

---

🦋 SYNOPSIS 🦋

int resctrl_arch_pseudo_lock_fn (void *_plr );

---

🎀 ARGUMENTS 🎀

• _plr — the pseudo-lock region descriptor. yes bestie, this is THE descriptor, the main character of the whole operation 👑

---

💖 DESCRIPTION 💖

okay so listen. this is the core pseudo-locking flow, like the actual heart of it. 🫶

First we ensure that the kernel memory cannot be found in the cache. literally cannot be found. it's giving hide and seek but make it silicon. 🙈

Then — and this is the part where we're all holding our breath — while taking care that there will be as little interference as possible, the memory to be loaded is accessed while the core is running with class of service set to the bitmask of the pseudo-locked region. yes, that whole sentence, we said it, it's real, it matters. 💀 After this is complete, no future CAT allocations will be allowed to overlap with this bitmask. periodt. that boundary is CLOSED. 🚫

Local register variables are utilized to ensure that the memory region to be locked is the only memory access made during the critical locking loop. like, the only one. the critical locking loop said "no distractions" and honestly same tbh. ✨

---

💜 RETURN 💜

• 0 — Waiter on waitqueue will be woken on completion. so like, congrats, somebody's waking up 🎉

---

🌈 SEE ALSO 🌈

• Kernel file ./arch/x86/kernel/cpu/resctrl/pseudo_lock.c
• resctrl_arch_get_prefetch_disable_bits(9)
• resctrl_arch_measure_cycles_lat_fn(9)

go read those too, iykyk 💖

---

and that's the whole page bestie!! this lil masterpiece lives under ./arch/x86/kernel/cpu/resctrl, dated October 2026, and it's brought to you by the Kernel API Manual — slay, goodbye, mwah 🩷🔥👑