diff options
author | Daniel Bristot de Oliveira <[email protected]> | 2022-12-09 23:05:52 +0100 |
---|---|---|
committer | Steven Rostedt (Google) <[email protected]> | 2022-12-10 13:36:05 -0500 |
commit | 1603dda47714cebe8a29b2154407da7a929d13f4 (patch) | |
tree | 53dfc39b702ca5f2682b7b197481ee618d00a8d2 /lib/mpi/mpi-sub-ui.c | |
parent | 0e162c6f1c8f7f502b3978f5a37ed6fa2e4d21f9 (diff) |
tracing/osnoise: Add PANIC_ON_STOP option
Often the latency observed in a CPU is not caused by the work being done
in the CPU itself, but by work done on another CPU that causes the
hardware to stall all CPUs. In this case, it is interesting to know
what is happening on ALL CPUs, and the best way to do this is via
crash dump analysis.
Add the PANIC_ON_STOP option to osnoise/timerlat tracers. The default
behavior is having this option off. When enabled by the user, the system
will panic after hitting a stop tracing condition.
This option was motivated by a real scenario that Juri Lelli and I
were debugging.
Link: https://lkml.kernel.org/r/249ce4287c6725543e6db845a6e0df621dc67db5.1670623111.git.bristot@kernel.org
Cc: Juri Lelli <[email protected]>
Cc: Clark Williams <[email protected]>
Cc: Bagas Sanjaya <[email protected]>
Cc: Daniel Bristot de Oliveira <[email protected]>
Cc: Masami Hiramatsu <[email protected]>
Cc: Jonathan Corbet <[email protected]>
Signed-off-by: Daniel Bristot de Oliveira <[email protected]>
Signed-off-by: Steven Rostedt (Google) <[email protected]>
Diffstat (limited to 'lib/mpi/mpi-sub-ui.c')
0 files changed, 0 insertions, 0 deletions