clockevents_program_event(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ clockevents_program_event ✨

okay so bestie, welcome to the Kernel API Manual πŸ’– you're literally about to read the page for clockevents_program_event(9) and honestly? it's giving "small function, big responsibility." let's get into it πŸŽ€


🌸 NAME 🌸

clockevents_program_event β€” reprogram the clock event device, no cap ⏰


πŸ¦‹ SYNOPSIS πŸ¦‹

int clockevents_program_event (struct clock_event_device *dev , ktime_t
expires , bool force );

like… look at her. three args, one int return, main character energy fr fr πŸ’…


πŸ’œ ARGUMENTS πŸ’œ

  • dev β€” the device you're programming πŸ› οΈ this is the clock event device in question, she's the one getting the glow-up
  • expires β€” the absolute expiry time, and it's on the monotonic clock ⏱️ absolute, not relative, don't get it twisted
  • force β€” if expires can't actually be set, this bad boy tells the function to program the minimum delay instead πŸ™ˆ like, "we can't do your time, so here's the earliest we can do"

🌈 DESCRIPTION 🌈

so here's the vibe check: the function returns 0 on success ✨ and returns -ETIME when the event is in the past πŸ’€ yeah… if your expiry time already happened, that's a no from her. -ETIME, periodt.


πŸ‘‘ SEE ALSO πŸ‘‘

if you're obsessed (and you should be 🫢), go peek at the kernel file ./kernel/time/clockevents.c and also these iconic siblings:


okay that's the whole page, you ate that πŸ“

lowkey a cute little sign-off: this one lives in ./kernel/time and it's dated October 2026 β€” and the page itself is clockevents_program_event(9), iykyk πŸ’–βœ¨πŸŽ€
πŸ“¦ where this page comes from