clocksource_...ax_deferment(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… clocksource_...ax_deferment(9) β€” from the Kernel API Manual, bestie ✨

Okay so this is the whole entire page for clocksource_update_max_deferment, straight out of the Kernel API Manual (the (9) is giving kernel-doc energy, iykyk πŸŽ€). Buckle up, it's short but it matters.


🌸 NAME 🌸

clocksource_update_max_deferment β€” Updates the clocksource max_idle_ns & max_cycles

Like, that's literally the whole job. Not me being dramatic, that's just what it does πŸ’…


✨ SYNOPSIS ✨

void clocksource_update_max_deferment (struct clocksource *cs );

Returns nothing (void), takes one pointer, moves on with its life. Iconic minimalism honestly πŸ¦‹


🫢 ARGUMENTS 🫢

  • cs β€” Pointer to clocksource to be updated. That's it, that's the whole input. Hand it a clocksource and it goes to work ✨
Fr fr, it's just one parameter. No sneaky extra args hiding anywhere. We checked. πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Bestie the reading list is LONG, so let's get into it. This all lives in Kernel file ./kernel/time/clocksource.c, and here's the whole squad:

Twenty entries. Twenty!! We did not skip a single one, that's a promise πŸ«‘πŸ’– Read them all or don't, but they're all here and accounted for.


🧚 Little reminder that this page only tells you it updates the clocksource max_idle_ns & max_cycles via the cs pointer β€” nothing more is claimed here, so don't go inventing extra behaviour, mwah πŸ’œ

Okay that's a wrap, bestie β€” with love from ./kernel/time, dated October 2026, in the Kernel API Manual, under the title clocksource_...ax_deferment(9). Slay, go update some deferment βœ¨πŸ’…

πŸ“¦ where this page comes from