The NetBSD Project

CVS log for src/share/man/man9/heartbeat.9

[BACK] Up to [cvs.NetBSD.org] / src / share / man / man9

Request diff between arbitrary revisions


Default branch: MAIN


Revision 1.5 / (download) - annotate - [select for diffs], Fri Jul 7 15:56:31 2023 UTC (7 months, 3 weeks ago) by uwe
Branch: MAIN
CVS Tags: HEAD
Changes since 1.4: +4 -3 lines
Diff to previous 1.4 (colored)

heartbeat(9): markup fixes

Use .Cd for options.  Don't use the usual <space><tab>, which is
superfluous in the man page.  Paragraph break after the config section
of synopsis, before the C API section.

Revision 1.4 / (download) - annotate - [select for diffs], Fri Jul 7 13:19:30 2023 UTC (7 months, 3 weeks ago) by riastradh
Branch: MAIN
Changes since 1.3: +2 -2 lines
Diff to previous 1.3 (colored)

heartbeat(9): Fix grammaro in man page.

Revision 1.3 / (download) - annotate - [select for diffs], Fri Jul 7 13:15:00 2023 UTC (7 months, 3 weeks ago) by wiz
Branch: MAIN
Changes since 1.2: +4 -2 lines
Diff to previous 1.2 (colored)

Replace main(9) reference with code location

Revision 1.2 / (download) - annotate - [select for diffs], Fri Jul 7 12:59:45 2023 UTC (7 months, 3 weeks ago) by wiz
Branch: MAIN
Changes since 1.1: +3 -3 lines
Diff to previous 1.1 (colored)

Sort SEE ALSO

Revision 1.1 / (download) - annotate - [select for diffs], Fri Jul 7 12:34:49 2023 UTC (7 months, 3 weeks ago) by riastradh
Branch: MAIN

heartbeat(9): New mechanism to check progress of kernel.

This uses hard interrupts to check progress of low-priority soft
interrupts, and one CPU to check progress of another CPU.

If no progress has been made after a configurable number of seconds
(kern.heartbeat.max_period, default 15), then the system panics --
preferably on the CPU that is stuck so we get a stack trace in dmesg
of where it was stuck, but if the stuckness was detected by another
CPU and the stuck CPU doesn't acknowledge the request to panic within
one second, the detecting CPU panics instead.

This doesn't supplant hardware watchdog timers.  It is possible for
hard interrupts to be stuck on all CPUs for some reason too; in that
case heartbeat(9) has no opportunity to complete.

Downside: heartbeat(9) relies on hardclock to run at a reasonably
consistent rate, which might cause trouble for the glorious tickless
future.  However, it could be adapted to take a parameter for an
approximate number of units that have elapsed since the last call on
the current CPU, rather than treating that as a constant 1.

XXX kernel revbump -- changes struct cpu_info layout

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.




CVSweb <webmaster@jp.NetBSD.org>