Re: [PATCH 2/4] doc: watchdog: Clarify hardlockup detection timing

[Petr Mladek]

On Thu 2026-02-12 14:12:11, Mayank Rungta via B4 Relay wrote:
> From: Mayank Rungta <mrungta@xxxxxxxxxx>
> 
> The current documentation implies that a hardlockup is strictly defined
> as looping for "more than 10 seconds." However, the detection mechanism
> is periodic (based on `watchdog_thresh`), meaning detection time varies
> significantly depending on when the lockup occurs relative to the NMI
> perf event.
> 
> Update the definition to remove the strict "more than 10 seconds"
> constraint in the introduction and defer details to the Implementation
> section.
> 
> Additionally, add a "Detection Overhead" section illustrating the
> Best Case (~6s) and Worst Case (~20s) detection scenarios to provide
> administrators with a clearer understanding of the watchdog's
> latency.
> 
> Signed-off-by: Mayank Rungta <mrungta@xxxxxxxxxx>

Great addition:

Reviewed-by: Petr Mladek <pmladek@xxxxxxxx>

Best Regards,
Petr