summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorFrancesco Valla <francesco@valla.it>2026-07-03 17:10:21 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2026-07-10 16:56:07 +0200
commit8b29d0b45266619533b5bc3c99a65ef96d01814f (patch)
treebec720ff5db6538cd449e030b83e41ef09d6c1e8 /tools/perf/scripts/python/bin/stackcollapse-record
parent7b5b51b2b05cf2b49eaa3808b1c2953cfb8e1cae (diff)
driver core: add driver name to probe debug print
The initcall_debug command line option is a useful tool while debugging and optimizing the initialization of a new system, mainly because it allows to see probe failures and deferrals without recompiling the kernel (e.g., with CONFIG_DEBUG_DRIVER). However, matching a device with the driver it is being probed with can become difficult, since some devices use names that are not explicit, at least at a first sight (e.g.: '1-0:1.0' or '1-0060'). Add the driver name alongside the device name, to allow for an immediate match between the two. Suggested-by: Tim Bird <tim.bird@sony.com> Signed-off-by: Francesco Valla <francesco@valla.it> Acked-by: Danilo Krummrich <dakr@kernel.org> Link: https://patch.msgid.link/20260703-probe_driver-v2-1-b6060559f33b@valla.it Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions