Changes in flamegraph-report

bbfd5594756011167b8f8de9a00e0c946afda1e6 - Merge drm/drm-next into drm-intel-gt-next

Wed, 28 May 2025 09:20:17 +0200

Merge drm/drm-next into drm-intel-gt-nextNeed to pull in a67221b5eb8d ("drm/i915/dp: Return min bpc supported by source instead of 0")in order to fix build breakage on GCC 9.4.0 (from Ubuntu 20.04).Signed-off-by: Joonas Lahtinen List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

db5302ae571beec635c1a96e7f72926a4e65195e - Merge drm/drm-next into drm-intel-next

Fri, 16 May 2025 09:22:36 +0200

Merge drm/drm-next into drm-intel-nextBackmerge to sync with v6.15-rc, xe, and specifically async flip changesin drm-misc.Signed-off-by: Jani Nikula List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

4f9786035f9e519db41375818e1d0b5f20da2f10 - Merge branch 'next' into for-linus

Mon, 02 Jun 2025 06:41:07 +0200

Merge branch 'next' into for-linusPrepare input updates for 6.16 merge window. List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

d51b9d81f7883f526b26e3ab903e646274aebeb1 - Merge tag 'v6.15-rc6' into next

Fri, 16 May 2025 01:20:39 +0200

Merge tag 'v6.15-rc6' into nextSync up with mainline to bring in xpad controller changes. List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

844e31bbaef7c8a6ff2c0fbac45c0c85b5484482 - Merge remote-tracking branch 'drm-misc/drm-misc-next' into msm-next

Tue, 29 Apr 2025 22:42:29 +0200

Merge remote-tracking branch 'drm-misc/drm-misc-next' into msm-nextMerge drm-misc-next to get commit Fixes: fec450ca15af ("drm/display:hdmi: provide central data authority for ACR params").Signed-off-by: Rob Clark List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

3ab7ae8e07f888f223027f0ef84d33e43919ad55 - Merge drm/drm-next into drm-xe-next

Thu, 24 Apr 2025 13:34:55 +0200

Merge drm/drm-next into drm-xe-nextBackmerge to bring in linux 6.15-rc.Signed-off-by: Thomas Hellström List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

1afba39f9305fe4061a4e70baa6ebab9d41459da - Merge drm/drm-next into drm-misc-next

Mon, 07 Apr 2025 13:47:40 +0200

Merge drm/drm-next into drm-misc-nextBackmerging to get v6.15-rc1 into drm-misc-next. Also fixes abuild issue when enabling CONFIG_DRM_SCHED_KUNIT_TEST.Signed-off-by: Thomas Zimmermann List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

9f13acb2406a3aed90c6738b3a2f1c0e43118cbd - Merge tag 'v6.15-rc1' into x86/cpu, to refresh the branch with upstream changes

Fri, 11 Apr 2025 11:13:27 +0200

Merge tag 'v6.15-rc1' into x86/cpu, to refresh the branch with upstream changesSigned-off-by: Ingo Molnar List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

6ce0fdaae043803bb324d915ce0fe43316bf1e81 - Merge tag 'v6.15-rc1' into x86/asm, to refresh the branch

Wed, 09 Apr 2025 21:39:43 +0200

Merge tag 'v6.15-rc1' into x86/asm, to refresh the branchSigned-off-by: Ingo Molnar List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

1260ed77798502de9c98020040d2995008de10cc - Merge drm/drm-fixes into drm-misc-fixes

Tue, 08 Apr 2025 10:15:47 +0200

Merge drm/drm-fixes into drm-misc-fixesBackmerging to get updates from v6.15-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

802f0d58d52e8e34e08718479475ccdff0caffa0 - Merge tag 'perf-tools-for-v6.15-2025-03-27' of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools

Mon, 31 Mar 2025 17:52:33 +0200

Merge tag 'perf-tools-for-v6.15-2025-03-27' of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-toolsPull perf tools updates from Namhyung Kim: "perf record: - Introduce latency profiling using scheduler information. The latency profiling is to show impacts on wall-time rather than cpu-time. By tracking context switches, it can weight samples and find which part of the code contributed more to the execution latency. The value (period) of the sample is weighted by dividing it by the number of parallel execution at the moment. The parallelism is tracked in perf report with sched-switch records. This will reduce the portion that are run in parallel and in turn increase the portion of serial executions. For now, it's limited to profile processes, IOW system-wide profiling is not supported. You can add --latency option to enable this. $ perf record --latency -- make -C tools/perf I've run the above command for perf build which adds -j option to make with the number of CPUs in the system internally. Normally it'd show something like below: $ perf report -F overhead,comm ... # # Overhead Command # ........ ............... # 78.97% cc1 6.54% python3 4.21% shellcheck 3.28% ld 1.80% as 1.37% cc1plus 0.80% sh 0.62% clang 0.56% gcc 0.44% perl 0.39% make ... The cc1 takes around 80% of the overhead as it's the actual compiler. However it runs in parallel so its contribution to latency may be less than that. Now, perf report will show both overhead and latency (if --latency was given at record time) like below: $ perf report -s comm ... # # Overhead Latency Command # ........ ........ ............... # 78.97% 48.66% cc1 6.54% 25.68% python3 4.21% 0.39% shellcheck 3.28% 13.70% ld 1.80% 2.56% as 1.37% 3.08% cc1plus 0.80% 0.98% sh 0.62% 0.61% clang 0.56% 0.33% gcc 0.44% 1.71% perl 0.39% 0.83% make ... You can see latency of cc1 goes down to around 50% and python3 and ld contribute a lot more than their overhead. You can use --latency option in perf report to get the same result but ordered by latency. $ perf report --latency -s comm perf report: - As a side effect of the latency profiling work, it adds a new output field 'latency' and a sort key 'parallelism'. The below is a result from my system with 64 CPUs. The build was well-parallelized but contained some serial portions. $ perf report -s parallelism ... # # Overhead Latency Parallelism # ........ ........ ........... # 16.95% 1.54% 62 13.38% 1.24% 61 12.50% 70.47% 1 11.81% 1.06% 63 7.59% 0.71% 60 4.33% 12.20% 2 3.41% 0.33% 59 2.05% 0.18% 64 1.75% 1.09% 9 1.64% 1.85% 5 ... - Support Feodra mini-debuginfo which is a LZMA compressed symbol table inside ".gnu_debugdata" ELF section. perf annotate: - Add --code-with-type option to enable data-type profiling with the usual annotate output. Instead of focusing on data structure, it shows code annotation together with data type it accesses in case the instruction refers to a memory location (and it was able to resolve the target data type). Currently it only works with --stdio. $ perf annotate --stdio --code-with-type ... Percent | Source code & Disassembly of vmlinux for cpu/mem-loads,ldlat=30/pp (18 samples, percent: local period) ---------------------------------------------------------------------------------------------------------------------- : 0 0xffffffff81050610 <__fdget>: 0.00 : ffffffff81050610: callq 0xffffffff81c01b80 <__fentry__> # data-type: (stack operation) 0.00 : ffffffff81050615: pushq %rbp # data-type: (stack operation) 0.00 : ffffffff81050616: movq %rsp, %rbp 0.00 : ffffffff81050619: pushq %r15 # data-type: (stack operation) 0.00 : ffffffff8105061b: pushq %r14 # data-type: (stack operation) 0.00 : ffffffff8105061d: pushq %rbx # data-type: (stack operation) 0.00 : ffffffff8105061e: subq $0x10, %rsp 0.00 : ffffffff81050622: movl %edi, %ebx 0.00 : ffffffff81050624: movq %gs:0x7efc4814(%rip), %rax # 0x14e40 # data-type: struct task_struct* +0 0.00 : ffffffff8105062c: movq 0x8d0(%rax), %r14 # data-type: struct task_struct +0x8d0 (files) 0.00 : ffffffff81050633: movl (%r14), %eax # data-type: struct files_struct +0 (count.counter) 0.00 : ffffffff81050636: cmpl $0x1, %eax 0.00 : ffffffff81050639: je 0xffffffff810506a9 <__fdget+0x99> 0.00 : ffffffff8105063b: movq 0x20(%r14), %rcx # data-type: struct files_struct +0x20 (fdt) 0.00 : ffffffff8105063f: movl (%rcx), %eax # data-type: struct fdtable +0 (max_fds) 0.00 : ffffffff81050641: cmpl %ebx, %eax 0.00 : ffffffff81050643: jbe 0xffffffff810506ef <__fdget+0xdf> 0.00 : ffffffff81050649: movl %ebx, %r15d 5.56 : ffffffff8105064c: movq 0x8(%rcx), %rdx # data-type: struct fdtable +0x8 (fd) ... The "# data-type:" part was added with this change. The first few entries are not very interesting. But later you can it accesses a couple of fields in the task_struct, files_struct and fdtable. perf trace: - Support syscall tracing for different ABI. For example it can trace system calls for 32-bit applications on 64-bit kernel transparently. - Add --summary-mode=total option to show global syscall summary. The default is 'thread' to show per-thread syscall summary. Python support: - Add more interfaces to 'perf' module to parse events, and config, enable or disable the event list properly so that it can implement basic functionalities purely in Python. There is an example code for these new interfaces in python/tracepoint.py. - Add mypy and pylint support to enable build time checking. Fix some code based on the findings from these tools. Internals: - Introduce io_dir__readdir() API to make directory traveral (usually for proc or sysfs) efficient with less memory footprint. JSON vendor events: - Add events and metrics for ARM Neoverse N3 and V3 - Update events and metrics on various Intel CPUs - Add/update events for a number of SiFive processors"* tag 'perf-tools-for-v6.15-2025-03-27' of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools: (229 commits) perf bpf-filter: Fix a parsing error with comma perf report: Fix a memory leak for perf_env on AMD perf trace: Fix wrong size to bpf_map__update_elem call perf tools: annotate asm_pure_loop.S perf python: Fix setup.py mypy errors perf test: Address attr.py mypy error perf build: Add pylint build tests perf build: Add mypy build tests perf build: Rename TEST_LOGS to SHELL_TEST_LOGS tools/build: Don't pass test log files to linker perf bench sched pipe: fix enforced blocking reads in worker_thread perf tools: Fix is_compat_mode build break in ppc64 perf build: filter all combinations of -flto for libperl perf vendor events arm64 AmpereOneX: Fix frontend_bound calculation perf vendor events arm64: AmpereOne/AmpereOneX: Mark LD_RETIRED impacted by errata perf trace: Fix evlist memory leak perf trace: Fix BTF memory leak perf trace: Make syscall table stable perf syscalltbl: Mask off ABI type for MIPS system calls perf build: Remove Makefile.syscalls ... List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

29bab85418efd329c1a984fc9b885b6709481b27 - perf script: Fix hangup in offline flamegraph report

Wed, 19 Feb 2025 01:05:58 +0100

perf script: Fix hangup in offline flamegraph reportA recent change in the flamegraph script fixed an issue with live modebut it created another for offline mode. It needs to pass "-" to -ioption to read from stdin in the live mode. Actually there's a logicto pass the option in the perf script code, but the script was writtenwith "-- $@" which prevented the option to go to the perf script. Sothe previous commit added the hard-coded "-i -" to the report command.But it's a problem for the offline mode which expects input from a fileand now it's stuck on reading from stdin. Let's remove the "-i - --"part and let it pass the options properly to perf script.Closes: https://lore.kernel.org/linux-perf-users/c41e4b04-e1fd-45ab-80b0-ec2ac6e94310@linux.ibm.comFixes: 23e0a63c6dd3f69c ("perf script: force stdin for flamegraph in live mode")Reported-by: Thomas Richter Tested-by: Thomas Richter Cc: Anubhav Shelat Signed-off-by: Namhyung Kim List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

23e0a63c6dd3f69cb7ee18411e5f6857cca55b30 - perf script: force stdin for flamegraph in live mode

Fri, 31 Jan 2025 15:57:05 +0100

perf script: force stdin for flamegraph in live modeCurrently, running "perf script flamegraph -a -F 99 sleep 1" shouldproduce flamegraph.html containing the flamegraph. Howevever, it gives asegmentation fault.This is caused because the flamegraph.py script issupposed to take as input the output of "perf record", which should bein stdin. This would require passing "-i -" to flamegraph.py. However,the "flamegraph-report" script causes "perf script" command to take the"-i -" option instead of flamegraph.py, which causes no problem for"perf script", but causes a seg fault since flamegraph.py has no inputfile. To fix this I added the "-i -" option directly to theflamegraph-report script to ensure flamegraph.py gets input from stdin.Signed-off-by: Anubhav Shelat Tested-by: Michael Petlan Link: https://lore.kernel.org/r/20250131145704.3164542-2-ashelat@redhat.comSigned-off-by: Namhyung Kim List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

4b4193256c8d3bc3a5397b5cd9494c2ad386317d - Merge branch 'next' into for-linus

Tue, 15 Dec 2020 01:27:23 +0100

Merge branch 'next' into for-linusPrepare input updates for 5.11 merge window. List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

05909cd9a0c8811731b38697af13075e8954314f - Merge tag 'v5.9' into next

Wed, 18 Nov 2020 03:13:23 +0100

Merge tag 'v5.9' into nextSync up with mainline to bring in the latest DTS files. List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

ead5d1f4d877e92c051e1a1ade623d0d30e71619 - Merge branch 'master' into for-next

Tue, 01 Sep 2020 14:19:48 +0200

Merge branch 'master' into for-nextSync with Linus' branch in order to be able to apply fixupsof more recent patches. List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

3b5d1afd1f13bcab85eaa28223ad396694f929e3 - Merge branch 'for-next' into for-linus

Mon, 03 Aug 2020 08:10:08 +0200

Merge branch 'for-next' into for-linus List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

98817a84ff1c755c347ac633ff017a623a631fad - Merge tag 'irqchip-fixes-5.8-1' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgent

Tue, 30 Jun 2020 12:07:51 +0200

Merge tag 'irqchip-fixes-5.8-1' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgentPull irqchip fixes from Marc Zyngier: - Fix atomicity of affinity update in the GIC driver - Don't sleep in atomic when waiting for a GICv4.1 RD to respond - Fix a couple of typos in user-visible messages List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

77346a704c913268a2dad68d59523fd85dc74088 - Merge tag 'v5.8-rc3' into arm/qcom

Tue, 30 Jun 2020 11:32:02 +0200

Merge tag 'v5.8-rc3' into arm/qcomLinux 5.8-rc3 List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report

60e9eabf41fa916d2ef68c5bf929197975917578 - Backmerge remote-tracking branch 'drm/drm-next' into drm-misc-next

Mon, 29 Jun 2020 12:15:51 +0200

Backmerge remote-tracking branch 'drm/drm-next' into drm-misc-nextSome conflicts with ttm_bo->offset removal, but drm-misc-next needs updating to v5.8.Signed-off-by: Maarten Lankhorst List of files: /linux/tools/perf/scripts/python/bin/flamegraph-report