clocksource_touch_watchdog(9)
π clocksource_touch_watchdog(9) β from the Kernel API Manual, bestie π
okay so real talk, this one is a tiny little page from the Kernel API Manual and it's honestly giving "small but mighty" β¨ so let's get into it π
πΈ NAME πΈ
clocksource_touch_watchdog β literally just updates the watchdog, that's the whole gig π«Ά
β¨ SYNOPSIS β¨
void clocksource_touch_watchdog (void );
likeβ¦ it takes nothing and returns nothing, no cap π
π¦ ARGUMENTS π¦
voidβ no arguments. zero. nada. the void is voiding π
π DESCRIPTION π
okay so here's the vibe: you call this bad boy to update the watchdog after exception contexts such as kgdb, so the watchdog doesn't incorrectly trip π like, we are NOT letting it trip by accident, that's not the energy we're bringing today π
β οΈ heads up bestie: this might fail when the kernel was stopped in code which holds watchdog_lock. so likeβ¦ it's a whole thing, don't come for me, that's just how it is π
π SEE ALSO π
omg the friend group is LARGE and honestly iconic π the kernel file is ./kernel/time/clocksource.c and then we got all these besties:
clocks_calc_mult_shift(9)clocksource_mark_unstable(9)clocksource_suspend_select(9)clocksource_start_suspend_timing(9)clocksource_stop_suspend_timing(9)clocksource_suspend(9)clocksource_resume(9)clocksource_max_adjustment(9)clocks_calc_max_nsecs(9)clocksource_update_max_deferment(9)clocksource_select(9)__clocksource_update_freq_scale(9)__clocksource_register_scale(9)clocksource_unregister(9)current_clocksource_show(9)current_clocksource_store(9)unbind_clocksource_store(9)available_clocksource_show(9)boot_override_clocksource(9)boot_override_clock(9)
and that's the whole page, periodt π
clocksource_touch_watchdog(9)</p>, living under ./kernel/time, dated October 2026, from the Kernel API Manual β slay, go touch that watchdog bestie, 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