resctrl_arch...disable_bits(9)
okay bestie, welcome to resctrl_arch...disable_bits(9) from the Kernel API Manual β we're about to get into prefetch disable bits and pseudo-locking, and honestly it's giving very specific kernel energy π
β¨
π NAME π
resctrl_arch_get_prefetch_disable_bitsβ prefetch disable bits of supported platforms
π¦ SYNOPSIS π¦
u64 resctrl_arch_get_prefetch_disable_bits (void );
πΈ ARGUMENTS πΈ
voidβ no arguments, like literally none, zero, nada π«Ά
β¨ DESCRIPTION β¨
So this one captures the list of platforms that have been validated to support pseudo-locking. That validation includes testing to make sure pseudo-locked regions with low cache miss rates can be created under a variety of load conditions, and also that those pseudo-locked regions can maintain their low cache miss rates under a variety of load conditions for significant lengths of time. iconic testing behavior, no cap π₯
After a platform has been validated to support pseudo-locking, its hardware prefetch disable bits are included here as they are documented in the SDM. periodt.
When you add a platform here, also add support for its cache events to resctrl_arch_measure_l*_residency β don't leave your girl hanging π
π RETURN π
If the platform is supported: the bits to disable hardware prefetchers. If the platform is not supported: 0. that's the whole vibe check π
π SEE ALSO π
- Kernel file
./arch/x86/kernel/cpu/resctrl/pseudo_lock.c resctrl_arch_pseudo_lock_fn(9)resctrl_arch_measure_cycles_lat_fn(9)
byeee π
this little page lives in the ./arch/x86/kernel/cpu/resctrl source/version corner, dated October 2026, and it's the resctrl_arch...disable_bits(9) page β mwah ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms