diff options
author | Brendan Jackman <jackmanb@google.com> | 2025-01-21 16:01:40 +0300 |
---|---|---|
committer | Shuah Khan <skhan@linuxfoundation.org> | 2025-02-19 00:28:01 +0300 |
commit | 43ebec94e1e8f6187c67bbe395b304a03ee63de5 (patch) | |
tree | e5ed537bd65e8207b5470c4fd19117350fdcdea0 /tools/perf/scripts/python/libxed.py | |
parent | e275f44e0a187b9d76830847976072f1c17b4b7b (diff) | |
download | linux-43ebec94e1e8f6187c67bbe395b304a03ee63de5.tar.xz |
kunit: tool: Build GDB scripts
Following a similar rationale as commit e4835f1da425f ("kunit: tool:
Build compile_commands.json"), make a common developer tool available by
default for KUnit users.
Compared to compile_commands.json, there is a little more work to be
done to build the GDB scripts. Is it enough to affect development cycle
duration? Unscientific evaluation:
rm -rf .kunit; time tools/testing/kunit/kunit.py build --kunitconfig ./lib/kunit/.kunitconfig --jobs 96
Without this patch it took 14.77s, with this patch it took 14.83. So,
although `make scripts_gdb` is pretty slow, presumably most of that is
just the overhead of running Kbuild at all, actually building the
scripts is approximately free.
Note also, to actually get the GDB scripts the user needs to enable
CONFIG_SCRIPTS_GDB, but building the scripts_gdb target without that is
still harmless.
Link: https://lore.kernel.org/r/20250121-kunit-gdb-v1-1-faedfd0653ef@google.com
Signed-off-by: Brendan Jackman <jackmanb@google.com>
Reviewed-by: David Gow <davidgow@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/libxed.py')
0 files changed, 0 insertions, 0 deletions