aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorOleksandr Natalenko <[email protected]>2022-09-03 08:43:30 +0200
committerAndrew Morton <[email protected]>2022-11-18 13:55:06 -0800
commit8603b6f58637ce196d68f7749633ea81af196d66 (patch)
tree86f6062bfd7d9b75cfad2dab47468248c26166a1 /tools/perf/scripts/python/bin/stackcollapse-record
parent597d77d29c5cc50b52bbbbd48c49a0237481a9df (diff)
core_pattern: add CPU specifier
Statistically, in a large deployment regular segfaults may indicate a CPU issue. Currently, it is not possible to find out what CPU the segfault happened on. There are at least two attempts to improve segfault logging with this regard, but they do not help in case the logs rotate. Hence, lets make sure it is possible to permanently record a CPU the task ran on using a new core_pattern specifier. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Oleksandr Natalenko <[email protected]> Suggested-by: Renaud Métrich <[email protected]> Reviewed-by: Oleg Nesterov <[email protected]> Cc: Alexander Viro <[email protected]> Cc: "Eric W . Biederman" <[email protected]> Cc: Grzegorz Halat <[email protected]> Cc: "Guilherme G. Piccoli" <[email protected]> Cc: "Huang, Ying" <[email protected]> Cc: Jason A. Donenfeld <[email protected]> Cc: Joel Savitz <[email protected]> Cc: Jonathan Corbet <[email protected]> Cc: Kees Cook <[email protected]> Cc: Laurent Dufour <[email protected]> Cc: Luis Chamberlain <[email protected]> Cc: Rob Herring <[email protected]> Cc: Stephen Kitt <[email protected]> Cc: Will Deacon <[email protected]> Cc: Xiaoming Ni <[email protected]> Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions