Perf tool LTO support
Subsystems (2)
Ian Rogers
reviewercover Perf tool LTO support
Add a build flag, LTO=1, so that perf is built with the -flto flag. Address some build errors this configuration throws up.
For me on my Debian derived OS, "CC=clang CXX=clang++ LD=ld.lld" works fine. With GCC LTO this fails with:
``` lto-wrapper: warning: using serial compilation of 50 LTRANS jobs lto-wrapper: note: see the ‘-flto’ option documentation for more information /usr/bin/ld: /tmp/ccK8kXAu.ltrans10.ltrans.o:(.data.rel.ro+0x28): undefined reference to `memset_orig' /usr/bin/ld: /tmp/ccK8kXAu.ltrans10.ltrans.o:(.data.rel.ro+0x40): undefined reference to `__memset' /usr/bin/ld: /tmp/ccK8kXAu.ltrans10.ltrans.o:(.data.rel+0x28): undefined reference to `memcpy_orig' /usr/bin/ld: /tmp/ccK8kXAu.ltrans10.ltrans.o:(.data.rel+0x40): undefined reference to `__memcpy' /usr/bin/ld: /tmp/ccK8kXAu.ltrans44.ltrans.o: in function `test__arch_unwind_sample': /home/irogers/kernel.org/tools/perf/arch/x86/tests/dwarf-unwind.c:72: undefined reference to `perf_regs_load' collect2: error: ld returned 1 exit status ```
The issue is that we build multiple .o files in a directory and then link them into a .o with "ld -r" (cmd_ld_multi). This early link step appears to trigger GCC to remove the .S file definition of the symbol and break the later link step (the perf-in.o shows perf_regs_load, for example, going from the text section to being undefined at the link step which doesn't happen with clang or without LTO). It is possible to work around this by taking the final perf link command and adding the .o files generated from .S back into it, namely:arch/x86/tests/regs_load.obench/mem-memset-x86-64-asm.obench/mem-memcpy-x86-64-asm.o
A quick performance check and the performance improvements from LTO are noticeable:
Non-LTO
``` $ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 202.216 usec (+- 0.160 usec) Average num. events: 51.000 (+- 0.000) Average time per event 3.965 usec Average data synthesis took: 230.875 usec (+- 0.285 usec) Average num. events: 271.000 (+- 0.000) Average time per event 0.852 usec ```
LTO
``` $ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 104.530 usec (+- 0.074 usec) Average num. events: 51.000 (+- 0.000) Average time per event 2.050 usec Average data synthesis took: 112.660 usec (+- 0.114 usec) Average num. events: 273.000 (+- 0.000) Average time per event 0.413 usec ```
Ian Rogers (4):
perf stat: Avoid uninitialized use of perf_stat_config perf parse-events: Avoid use uninitialized warning perf test: Avoid weak symbol for arch_tests perf build: Add LTO build option
tools/perf/Makefile.config | 5 +++++ tools/perf/tests/builtin-test.c | 11 ++++++++++- tools/perf/tests/stat.c | 2 +- tools/perf/util/parse-events.c | 2 +- tools/perf/util/stat.c | 2 +- 5 files changed, 18 insertions(+), 4 deletions(-)
Signature · 1 line
2.41.0.487.g6d72f3e995-goog
Ian Rogers
reviewerPATCH 1/4 perf stat: Avoid uninitialized use of perf_stat_config
perf_event__read_stat_config will assign values based on number of tags and tag values. Initialize the structs to zero before they are assigned so that no uninitialized values can be seen.
This potential error was reported by GCC with LTO enabled.
--- tools/perf/tests/stat.c | 2 +- tools/perf/util/stat.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
tools/perf/tests/stat.c +1 -1
@@ -27,7 +27,7 @@ static int process_stat_config_event(struct perf_tool *tool __maybe_unused, struct machine *machine __maybe_unused) {struct perf_record_stat_config *config = &event->stat_config; -struct perf_stat_config stat_config; +struct perf_stat_config stat_config = {};#define HAS (term, val) \ has_term(config, PERF_STAT_CONFIG_TERM__##term, val)
tools/perf/util/stat.c +1 -1
@@ -729,7 +729,7 @@ size_t perf_event__fprintf_stat_round(union perf_event *event, FILE *fp)size_t perf_event__fprintf_stat_config (union perf_event *event,FILE *fp) { -struct perf_stat_config sc; +struct perf_stat_config sc = {};size_t ret;perf_event__read_stat_config (&sc, &event->stat_config);
Signature · 1 line
2.41.0.487.g6d72f3e995-goog
Re: [PATCH v1 1/4] perf stat: Avoid uninitialized use of perf_stat_config
Quoted 18 lines · Ian Rogers
perf_event__read_stat_configwill assign values based on number of tags and tag values. Initialize the structs to zero before they are assigned so that no uninitialized values can be seen.This potential error was reported by GCC with LTO enabled.
Signed-off-by Ian Rogers <[email protected]>--- tools/perf/tests/stat.c | 2 +- tools/perf/util/stat.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)tools/perf/tests/stat.c +0
-0
tools/perf/tests/stat.c static int process_stat_config_event(struct perf_tool *tool __maybe_unused, · line 30
Quoted 5 lines
tools/perf/tests/stat.c +1
-1@@ -27,7 +27,7 @@ static int process_stat_config_event(struct perf_tool *tool __maybe_unused, struct machine *machine __maybe_unused) {struct perf_record_stat_config *config = &event->stat_config; -struct perf_stat_config stat_config; +struct perf_stat_config stat_config = {};
^ how did this code ever work?
1. stat_config is not initialized
2. perf_event__read_stat_config maybe assigns to &stat_config->__val
3. process_stat_config_event() tests other members of stat_config
I hope I've missed something obvious.
Quoted 19 lines
tools/perf/tests/stat.c +0
-0#define HAS (term, val) \ has_term(config, PERF_STAT_CONFIG_TERM__##term, val)tools/perf/util/stat.c +1
-2@@ -729,7 +729,7 @@ size_t perf_event__fprintf_stat_round(union perf_event *event, FILE *fp)size_t perf_event__fprintf_stat_config (union perf_event *event,FILE *fp) { -struct perf_stat_config sc; +struct perf_stat_config sc = {};size_t ret;perf_event__read_stat_config (&sc, &event->stat_config); --2.41.0.487.g6d72f3e995-goog
Signature · 2 lines
Thanks, ~Nick Desaulniers
Ian Rogers
reviewerPATCH 2/4 perf parse-events: Avoid use uninitialized warning
In reply to Ian RogersWith GCC LTO a potential use uninitialized is spotted:
```
In function ‘parse_events_config_bpf’,
inlined from ‘parse_events_load_bpf’ at util/parse-events.c:874:8:
util/parse-events.c:792:37: error: ‘error_pos’ may be used uninitialized [-Werror=maybe-uninitialized]
792 | idx = term->err_term + error_pos;
| ^
util/parse-events.c: In function ‘parse_events_load_bpf’:
util/parse-events.c:765:13: note: ‘error_pos’ was declared here
765 | int error_pos;
| ^
```So initialize at declaration.
--- tools/perf/util/parse-events.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/perf/util/parse-events.c +1 -1
@@ -762,7 +762,7 @@ parse_events_config_bpf(struct parse_events_state *parse_state, struct list_head *head_config) {struct parse_events_term *term; -int error_pos; +int error_pos =0 ;if (!head_config ||list_empty (head_config))return 0 ;
Signature · 1 line
2.41.0.487.g6d72f3e995-goog
Re: [PATCH v1 2/4] perf parse-events: Avoid use uninitialized warning
Quoted 13 lines · Ian Rogers
With GCC LTO a potential use uninitialized is spotted:
``` In function ‘parse_events_config_bpf’, inlined from ‘parse_events_load_bpf’ at util/parse-events.c:874:8: util/parse-events.c:792:37: error: ‘error_pos’ may be used uninitialized [-Werror=maybe-uninitialized] 792 | idx = term->err_term + error_pos; | ^ util/parse-events.c: In function ‘parse_events_load_bpf’: util/parse-events.c:765:13: note: ‘error_pos’ was declared here 765 | int error_pos; | ^ ```
Quoted 1 line
So initialize at declaration.
This common pattern in C is error prone (conditional assignment in the callee; callers maybe forget to initialize, then unconditionally use the value). Clang's static analyzer can spot these, but isn't run for tools/ AFAIK.
Quoted 22 lines
Signed-off-by Ian Rogers <[email protected]>--- tools/perf/util/parse-events.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)tools/perf/util/parse-events.c +1
-2@@ -762,7 +762,7 @@ parse_events_config_bpf(struct parse_events_state *parse_state, struct list_head *head_config) {struct parse_events_term *term; -int error_pos; +int error_pos =0 ;if (!head_config ||list_empty (head_config))return 0 ; --2.41.0.487.g6d72f3e995-goog
Signature · 2 lines
Thanks, ~Nick Desaulniers
Ian Rogers
reviewerPATCH 3/4 perf test: Avoid weak symbol for arch_tests
In reply to Ian RogersGCC LTO will complain that the array length varies for the arch_tests weak symbol. Use extern/static and architecture determining #if to workaround this problem.
--- tools/perf/tests/builtin-test.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)
tools/perf/tests/builtin-test.c +10 -1
@@ -33,9 +33,18 @@static bool dont_fork;const char *dso_to_test; -struct test_suite *__weak arch_tests[] = { +/* +* List of architecture specific tests. Not a weak symbol as the array length is +* dependent on the initialization, as such GCC with LTO complains of +* conflicting definitions with a weak symbol. +*/ +#if defined(__i386__) || defined(__x86_64__) || defined(__aarch64__) || defined(__powerpc64__) +extern struct test_suite *arch_tests[]; +#else +static struct test_suite *arch_tests[] = {NULL , }; +#endif static struct test_suite *generic_tests[] = { &suite__vmlinux_matches_kallsyms,
Signature · 1 line
2.41.0.487.g6d72f3e995-goog
Ian Rogers
reviewerPATCH 4/4 perf build: Add LTO build option
In reply to Ian RogersAdd an LTO build option, that sets the appropriate CFLAGS and CXXFLAGS values.
--- tools/perf/Makefile.config | 5 +++++ 1 file changed, 5 insertions(+)
tools/perf/Makefile.config +5 -0
@@ -256,6 +256,11 @@ ifdef PARSER_DEBUG $(call detected_var,PARSER_DEBUG_FLEX) endif +ifdef LTO + CORE_CFLAGS += -flto + CXXFLAGS += -flto +endif + # Try different combinations to accommodate systems that only have # python[2][3]-config in weird combinations in the following order of # priority from lowest to highest:
Signature · 1 line
2.41.0.487.g6d72f3e995-goog
Quoted 3 lines · Ian Rogers
Add a build flag, LTO=1, so that perf is built with the -flto flag. Address some build errors this configuration throws up.
Hi Ian,
Thanks for the performance numbers. Any sense of what the build time numbers might look like for building perf with LTO?
Does -flto=thin in clang's case make a meaningful difference of -flto? I'd recommend that over "full LTO" -flto when the performance difference of the result isn't too meaningful. ThinLTO should be faster to build, but I don't know that I've ever built perf, so IDK what to expect.
Signature · 2 lines
Thanks, ~Nick Desaulniers
Ian Rogers
reviewerQuoted 10 lines · Nick Desaulniers
Quoted 3 lines · Ian Rogers
Add a build flag, LTO=1, so that perf is built with the -flto flag. Address some build errors this configuration throws up.
Hi Ian,
Thanks for the performance numbers. Any sense of what the build time numbers might look like for building perf with LTO?
Quoted 5 lines
Does
-flto=thinin clang's case make a meaningful difference of-flto? I'd recommend that over "full LTO"-fltowhen the performance difference of the result isn't too meaningful. ThinLTO should be faster to build, but I don't know that I've ever built perf, so IDK what to expect.
Hi Nick,
I'm not sure how much the perf build will benefit from LTO to say whether thin is good enough or not. Things like "perf record" are designed to spend the majority of their time blocking on a poll system call. We have benchmarks at least :-)
I grabbed some clang build times in an unscientific way on my loaded laptop:
no LTO
real 0m48.846s user 3m11.452s sys 0m29.598s
-flto=thin
real 0m55.910s user 4m2.342s sys 0m30.120s
real 0m50.330s user 3m36.986s sys 0m28.519s
-flto
real 1m12.002s user 3m27.676s sys 0m30.305s
real 1m5.187s user 3m19.348s sys 0m29.031s
So perhaps thin LTO increases total build time by 10%, whilst full LTO increases it by 50%.
Gathering some clang performance numbers:
no LTO
$ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 178.694 usec (+- 0.171 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.436 usec Average data synthesis took: 194.545 usec (+- 0.088 usec) Average num. events: 277.000 (+- 0.000) Average time per event 0.702 usec # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 175.381 usec (+- 0.105 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.373 usec Average data synthesis took: 188.980 usec (+- 0.071 usec) Average num. events: 278.000 (+- 0.000) Average time per event 0.680 usec
-flto=thin
$ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 183.122 usec (+- 0.082 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.522 usec Average data synthesis took: 196.468 usec (+- 0.102 usec) Average num. events: 277.000 (+- 0.000) Average time per event 0.709 usec # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 177.684 usec (+- 0.094 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.417 usec Average data synthesis took: 190.079 usec (+- 0.077 usec) Average num. events: 275.000 (+- 0.000) Average time per event 0.691 usec
-flto
$ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 112.599 usec (+- 0.040 usec) Average num. events: 52.000 (+- 0.000) Average time per event 2.165 usec Average data synthesis took: 119.012 usec (+- 0.070 usec) Average num. events: 278.000 (+- 0.000) Average time per event 0.428 usec # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 107.606 usec (+- 0.147 usec) Average num. events: 52.000 (+- 0.000) Average time per event 2.069 usec Average data synthesis took: 114.633 usec (+- 0.159 usec) Average num. events: 279.000 (+- 0.000) Average time per event 0.411 usec
The performance win from thin LTO doesn't look to be there. Full LTO appears to be reducing event synthesis time down to 60% of what it was. The clang numbers are looking better than the GCC ones. I think from this it makes sense to use -flto.
Thanks,
Ian
Quoted 3 lines
--
Thanks,
~Nick Desaulniers
Quoted 119 lines · Ian Rogers
Quoted 10 lines · Nick Desaulniers
Quoted 3 lines · Ian Rogers
Add a build flag, LTO=1, so that perf is built with the -flto flag. Address some build errors this configuration throws up.
Hi Ian,
Thanks for the performance numbers. Any sense of what the build time numbers might look like for building perf with LTO?Quoted 5 lines
Does
-flto=thinin clang's case make a meaningful difference of-flto? I'd recommend that over "full LTO"-fltowhen the performance difference of the result isn't too meaningful. ThinLTO should be faster to build, but I don't know that I've ever built perf, so IDK what to expect.Hi Nick,
I'm not sure how much the perf build will benefit from LTO to say whether thin is good enough or not. Things like "perf record" are designed to spend the majority of their time blocking on a poll system call. We have benchmarks at least :-)
I grabbed some clang build times in an unscientific way on my loaded laptop:
no LTO
real 0m48.846s user 3m11.452s sys 0m29.598s-flto=thin
real 0m55.910s user 4m2.342s sys 0m30.120sreal 0m50.330s user 3m36.986s sys 0m28.519s-flto
real 1m12.002s user 3m27.676s sys 0m30.305sreal 1m5.187s user 3m19.348s sys 0m29.031sSo perhaps thin LTO increases total build time by 10%, whilst full LTO increases it by 50%.
Gathering some clang performance numbers:
no LTO
$ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 178.694 usec (+- 0.171 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.436 usec Average data synthesis took: 194.545 usec (+- 0.088 usec) Average num. events: 277.000 (+- 0.000) Average time per event 0.702 usec # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 175.381 usec (+- 0.105 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.373 usec Average data synthesis took: 188.980 usec (+- 0.071 usec) Average num. events: 278.000 (+- 0.000) Average time per event 0.680 usec-flto=thin
$ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 183.122 usec (+- 0.082 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.522 usec Average data synthesis took: 196.468 usec (+- 0.102 usec) Average num. events: 277.000 (+- 0.000) Average time per event 0.709 usec # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 177.684 usec (+- 0.094 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.417 usec Average data synthesis took: 190.079 usec (+- 0.077 usec) Average num. events: 275.000 (+- 0.000) Average time per event 0.691 usec-flto
$ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 112.599 usec (+- 0.040 usec) Average num. events: 52.000 (+- 0.000) Average time per event 2.165 usec Average data synthesis took: 119.012 usec (+- 0.070 usec) Average num. events: 278.000 (+- 0.000) Average time per event 0.428 usec # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 107.606 usec (+- 0.147 usec) Average num. events: 52.000 (+- 0.000) Average time per event 2.069 usec Average data synthesis took: 114.633 usec (+- 0.159 usec) Average num. events: 279.000 (+- 0.000) Average time per event 0.411 usec
Quoted 4 lines
The performance win from thin LTO doesn't look to be there. Full LTO appears to be reducing event synthesis time down to 60% of what it was. The clang numbers are looking better than the GCC ones. I think from this it makes sense to use -flto.
Without any context, I'm not really sure what numbers are good vs. bad ("is larger better?"). More so I was curious if thinLTO perhaps got most of the win without significant performance regressions. If not, oh well, and if the slower full LTO has numbers that make sense to other reviewers, well then *Chuck Norris thumbs up*. Thanks for the stats.
Quoted 7 lines
Thanks,
IanQuoted 3 lines
--
Thanks,
~Nick Desaulniers
Signature · 2 lines
Thanks, ~Nick Desaulniers
Ian Rogers
reviewerQuoted 121 lines · Nick Desaulniers
Quoted 119 lines · Ian Rogers
Quoted 10 lines · Nick Desaulniers
Quoted 3 lines · Ian Rogers
Add a build flag, LTO=1, so that perf is built with the -flto flag. Address some build errors this configuration throws up.
Hi Ian,
Thanks for the performance numbers. Any sense of what the build time numbers might look like for building perf with LTO?Quoted 5 lines
Does
-flto=thinin clang's case make a meaningful difference of-flto? I'd recommend that over "full LTO"-fltowhen the performance difference of the result isn't too meaningful. ThinLTO should be faster to build, but I don't know that I've ever built perf, so IDK what to expect.Hi Nick,
I'm not sure how much the perf build will benefit from LTO to say whether thin is good enough or not. Things like "perf record" are designed to spend the majority of their time blocking on a poll system call. We have benchmarks at least :-)
I grabbed some clang build times in an unscientific way on my loaded laptop:
no LTO
real 0m48.846s user 3m11.452s sys 0m29.598s-flto=thin
real 0m55.910s user 4m2.342s sys 0m30.120sreal 0m50.330s user 3m36.986s sys 0m28.519s-flto
real 1m12.002s user 3m27.676s sys 0m30.305sreal 1m5.187s user 3m19.348s sys 0m29.031sSo perhaps thin LTO increases total build time by 10%, whilst full LTO increases it by 50%.
Gathering some clang performance numbers:
no LTO
$ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 178.694 usec (+- 0.171 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.436 usec Average data synthesis took: 194.545 usec (+- 0.088 usec) Average num. events: 277.000 (+- 0.000) Average time per event 0.702 usec # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 175.381 usec (+- 0.105 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.373 usec Average data synthesis took: 188.980 usec (+- 0.071 usec) Average num. events: 278.000 (+- 0.000) Average time per event 0.680 usec-flto=thin
$ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 183.122 usec (+- 0.082 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.522 usec Average data synthesis took: 196.468 usec (+- 0.102 usec) Average num. events: 277.000 (+- 0.000) Average time per event 0.709 usec # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 177.684 usec (+- 0.094 usec) Average num. events: 52.000 (+- 0.000) Average time per event 3.417 usec Average data synthesis took: 190.079 usec (+- 0.077 usec) Average num. events: 275.000 (+- 0.000) Average time per event 0.691 usec-flto
$ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 112.599 usec (+- 0.040 usec) Average num. events: 52.000 (+- 0.000) Average time per event 2.165 usec Average data synthesis took: 119.012 usec (+- 0.070 usec) Average num. events: 278.000 (+- 0.000) Average time per event 0.428 usec # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 107.606 usec (+- 0.147 usec) Average num. events: 52.000 (+- 0.000) Average time per event 2.069 usec Average data synthesis took: 114.633 usec (+- 0.159 usec) Average num. events: 279.000 (+- 0.000) Average time per event 0.411 usec
Quoted 11 lines
Quoted 4 lines
The performance win from thin LTO doesn't look to be there. Full LTO appears to be reducing event synthesis time down to 60% of what it was. The clang numbers are looking better than the GCC ones. I think from this it makes sense to use -flto.
Without any context, I'm not really sure what numbers are good vs. bad ("is larger better?"). More so I was curious if thinLTO perhaps got most of the win without significant performance regressions. If not, oh well, and if the slower full LTO has numbers that make sense to other reviewers, well then *Chuck Norris thumbs up*. Thanks for the stats.
I can at least explain the stats. When perf starts it has to "synthesize" the state-of-the machine, it generates fake events to describe the mmaps in each process by reading /proc. This is done most typically so a virtual address can be turned into a filename and line number. Generally this is done for the text part of a binary but it may also be done for the data. Large systems may take a long time to synthesize all the state for, hence the benchmark.
The result I normally look at above is the "Average time per event", so without LTO or with thin LTO each event is taking approx. 180 microseconds to create. With full LTO the time taken per event is 110 microseconds, which could be a noticeable start-up time win.
Thanks,
Ian
Quoted 13 lines
Quoted 7 lines
Thanks,
IanQuoted 3 lines
--
Thanks,
~Nick Desaulniers--
Thanks,
~Nick Desaulniers
Arnaldo Carvalho de Melo
maintainerEm Mon, Jul 24, 2023 at 01:12:43PM -0700, Ian Rogers escreveu:
Quoted 48 lines
Add a build flag, LTO=1, so that perf is built with the -flto flag. Address some build errors this configuration throws up.
For me on my Debian derived OS, "CC=clang CXX=clang++ LD=ld.lld" works fine. With GCC LTO this fails with:
``` lto-wrapper: warning: using serial compilation of 50 LTRANS jobs lto-wrapper: note: see the ‘-flto’ option documentation for more information /usr/bin/ld: /tmp/ccK8kXAu.ltrans10.ltrans.o:(.data.rel.ro+0x28): undefined reference to `memset_orig' /usr/bin/ld: /tmp/ccK8kXAu.ltrans10.ltrans.o:(.data.rel.ro+0x40): undefined reference to `__memset' /usr/bin/ld: /tmp/ccK8kXAu.ltrans10.ltrans.o:(.data.rel+0x28): undefined reference to `memcpy_orig' /usr/bin/ld: /tmp/ccK8kXAu.ltrans10.ltrans.o:(.data.rel+0x40): undefined reference to `__memcpy' /usr/bin/ld: /tmp/ccK8kXAu.ltrans44.ltrans.o: in function `test__arch_unwind_sample': /home/irogers/kernel.org/tools/perf/arch/x86/tests/dwarf-unwind.c:72: undefined reference to `perf_regs_load' collect2: error: ld returned 1 exit status ```The issue is that we build multiple .o files in a directory and then link them into a .o with "ld -r" (
cmd_ld_multi). This early link step appears to trigger GCC to remove the .S file definition of the symbol and break the later link step (the perf-in.o showsperf_regs_load, for example, going from the text section to being undefined at the link step which doesn't happen with clang or without LTO). It is possible to work around this by taking the final perf link command and adding the .o files generated from .S back into it, namely:arch/x86/tests/regs_load.obench/mem-memset-x86-64-asm.obench/mem-memcpy-x86-64-asm.oA quick performance check and the performance improvements from LTO are noticeable:
Non-LTO
``` $ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 202.216 usec (+- 0.160 usec) Average num. events: 51.000 (+- 0.000) Average time per event 3.965 usec Average data synthesis took: 230.875 usec (+- 0.285 usec) Average num. events: 271.000 (+- 0.000) Average time per event 0.852 usec ```LTO
```
Quoted 10 lines
$ perf bench internals synthesize # Running 'internals/synthesize' benchmark: Computing performance of single threaded perf event synthesis by synthesizing events on the perf process itself: Average synthesis took: 104.530 usec (+- 0.074 usec) Average num. events: 51.000 (+- 0.000) Average time per event 2.050 usec Average data synthesis took: 112.660 usec (+- 0.114 usec) Average num. events: 273.000 (+- 0.000) Average time per event 0.413 usec
Cool stuff! Applied locally, test building now on the container suite.
- Arnaldo
Quoted 18 lines
```
Ian Rogers (4):
perf stat: Avoid uninitialized use ofperf_stat_configperf parse-events: Avoid use uninitialized warning perf test: Avoid weak symbol forarch_testsperf build: Add LTO build optiontools/perf/Makefile.config | 5 +++++ tools/perf/tests/builtin-test.c | 11 ++++++++++- tools/perf/tests/stat.c | 2 +- tools/perf/util/parse-events.c | 2 +- tools/perf/util/stat.c | 2 +- 5 files changed, 18 insertions(+), 4 deletions(-)Signature · 1 line
2.41.0.487.g6d72f3e995-goog
Signature · 1 line
- Arnaldo