hardlockup_d...djust_period(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… hardlockup_detector_perf_adjust_period πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes we're in the kernel docs now, put your hair up, we're doing Real Systems Programming ✨ This one's about hardlockup_detector_perf_adjust_period, and honestly? Iconic name, tiny job, huge lore.


✨ NAME ✨

hardlockup_detector_perf_adjust_period β€” literally just adjusting the event period because the current cpu frequency changed πŸ¦‹

Like no cap, that's the whole vibe. CPU frequency goes brrr differently than before, so the period needs a lil tune-up. Lowkey elegant.


🌸 SYNOPSIS 🌸

void hardlockup_detector_perf_adjust_period (u64 period );

That's it. That's the whole signature. A void return (nothing comes back out 😌) and one u64 coming in. Copy it exactly, don't get creative, period has a space before the paren and we respect the original, periodt πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • period β€” ngl this is the target period that's gonna be set. That's the whole job description bestie, it's giving "one argument, zero drama" 🫢

πŸ”₯ SEE ALSO πŸ”₯

bestie the cross-references are chef's kiss, go read these next, they're all in the kernel file ./kernel/watchdog_perf.c πŸ’–

πŸ’€ friendly reminder that the "see also" section is not decorative. these are your girls. go say hi.

and that's the page, bestie!! 🌈⭐

this lil masterpiece lives in ./kernel, and it's stamped October 2026 β€” so like, future-dated documentation, main character energy fr fr πŸ§šβ€β™€οΈπŸ’œ bookmark it, cite it, adjust those periods responsibly πŸ˜­πŸ‘‘

(also hardlockup_d...djust_period(9) is how the header/footer abbreviate the name β€” the terminal was too narrow to hold all that greatness πŸ’…)

πŸ“¦ where this page comes from