watchdog_hardlockup_start(9)

👑 watchdog_hardlockup_start — start the watchdog after reconfiguration 🐶✨

🌸 NAME 🌸

watchdog_hardlockup_start — Start the watchdog after reconfiguration.

Okay so welcome to the watchdog_hardlockup_start(9) page in the Kernel API Manual, bestie 🫶. This is the manual-name moment and we are seated 💅.

✨ SYNOPSIS ✨

void watchdog_hardlockup_start (void );

🎀 ARGUMENTS 🎀

• void — no arguments. Not one. Not even a lil guy. Literally none 💀✨.

🦋 DESCRIPTION 🦋

This one is the counterpart to watchdog_hardlockup_stop — it’s giving “start the watchdog after reconfiguration” energy, no cap 🔥.

The following variables have been updated in update_variables and contain the currently valid configuration:

• watchdog_enabled
• watchdog_thresh
• watchdog_cpumask

So yeah, those are the three variables in the currently valid config lineup, periodt 💖.

🌈 SEE ALSO 🌈

• Kernel file ./kernel/watchdog.c
• watchdog_hardlockup_stop(9)
• lockup_detector_update_enable(9)
• touch_softlockup_watchdog_sched(9)
• lockup_detector_soft_poweroff(9)

That’s the whole page, bestie 🎀. Source/version ./kernel, dated October 2026, and the page is watchdog_hardlockup_start(9) — iconic, mwah 💋✨.