License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 15:07:57 +01:00
|
|
|
|
2019-01-29 11:11:04 +01:00
|
|
|
|
2019-08-29 15:56:40 -03:00
|
|
|
|
2019-08-30 11:11:01 -03:00
|
|
|
|
2010-05-21 12:48:39 +02:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2017-01-05 22:23:31 -08:00
|
|
|
|
2019-08-30 15:09:54 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:43 -07:00
|
|
|
|
2009-12-14 13:10:39 -02:00
|
|
|
|
perf tools: Add 'cgroup_id' sort order keyword
This patch introduces a cgroup identifier entry field in perf report to
identify or distinguish data of different cgroups. It uses the device
number and inode number of cgroup namespace, included in perf data with
the new PERF_RECORD_NAMESPACES event, as cgroup identifier.
With the assumption that each container is created with it's own cgroup
namespace, this allows assessment/analysis of multiple containers at
once.
A simple test for this would be to clone a few processes passing
SIGCHILD & CLONE_NEWCROUP flags to each of them, execute shell and run
different workloads on each of those contexts, while running perf
record command with --namespaces option.
Shown below is the output of perf report, sorted with cgroup identifier,
on perf.data generated with the above test scenario, clearly indicating
one context's considerable use of kernel memory in comparison with
others:
$ perf report -s cgroup_id,sample --stdio
#
# Total Lost Samples: 0
#
# Samples: 5K of event 'kmem:kmalloc'
# Event count (approx.): 5965
#
# Overhead cgroup id (dev/inode) Samples
# ........ ..................... ............
#
81.27% 3/0xeffffffb 4848
16.24% 3/0xf00000d0 969
1.16% 3/0xf00000ce 69
0.82% 3/0xf00000cf 49
0.50% 0/0x0 30
While this is a start, there is further scope of improving this. For
example, instead of cgroup namespace's device and inode numbers, dev
and inode numbers of some or all namespaces may be used to distinguish
which processes are running in a given container context.
Also, scripts to map device and inode info to containers sounds
plausible for better tracing of containers.
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Alexei Starovoitov <ast@fb.com>
Cc: Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>
Cc: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
Cc: Brendan Gregg <brendan.d.gregg@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Eric Biederman <ebiederm@xmission.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sargun Dhillon <sargun@sargun.me>
Cc: Steven Rostedt <rostedt@goodmis.org>
Link: http://lkml.kernel.org/r/148891933338.25309.756882900782042645.stgit@hbathini.in.ibm.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2017-03-08 02:12:13 +05:30
|
|
|
|
2020-03-25 21:45:32 +09:00
|
|
|
|
2009-12-14 13:10:39 -02:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
2014-10-10 15:49:21 -03:00
|
|
|
|
2013-01-22 18:09:33 +09:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
2017-04-17 16:30:49 -03:00
|
|
|
|
2019-01-28 00:03:34 +01:00
|
|
|
|
2017-04-19 21:34:35 -03:00
|
|
|
|
2019-11-07 15:47:14 +08:00
|
|
|
|
2014-12-22 13:44:10 +09:00
|
|
|
|
2017-04-18 10:46:11 -03:00
|
|
|
|
2009-12-16 14:31:49 -02:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
2017-04-19 18:51:14 -03:00
|
|
|
|
2019-08-30 11:54:00 -03:00
|
|
|
|
2019-08-29 16:18:59 -03:00
|
|
|
|
2019-03-11 07:44:54 -07:00
|
|
|
|
2019-07-04 11:32:27 -03:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-19 13:09:10 -02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-03-16 17:50:51 +09:00
|
|
|
|
|
|
|
|
|
2015-09-04 10:45:44 -04:00
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:17 +01:00
|
|
|
|
|
|
|
|
|
2011-10-19 13:09:10 -02:00
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
|
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
|
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
|
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-20 13:52:05 +09:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
|
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-20 13:52:05 +09:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
|
|
|
|
|
2019-11-07 15:47:13 +08:00
|
|
|
|
|
|
|
|
|
2013-04-01 20:35:19 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-17 17:17:38 +09:00
|
|
|
|
2013-04-01 20:35:19 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
|
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
|
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
2016-06-20 23:58:19 +02:00
|
|
|
|
2026-03-20 16:45:53 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
|
|
|
|
|
2023-03-20 14:22:35 -07:00
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
2012-12-27 18:11:42 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
2019-11-04 15:57:38 -03:00
|
|
|
|
|
|
|
|
|
2017-02-17 17:17:38 +09:00
|
|
|
|
2013-04-01 20:35:19 +09:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
|
|
|
|
|
2023-03-20 14:22:35 -07:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
perf report: Add "addr_from" and "addr_to" sort dimensions
With the existing symbol_from/symbol_to, branches captured in the same
function would be collapsed into a single function if the latencies
associated with the each branch (cycles) were all the same. That is the
case on Intel Broadwell, for instance. Since Intel Skylake, the latency
is captured by hardware and therefore is used to disambiguate branches.
Add addr_from/addr_to sort dimensions to sort branches based on their
addresses and not the function there are in. The output is still the
function name but the offset within the function is provided to uniquely
identify each branch. These new sort dimensions also help with annotate
because they create different entries in the histogram which, in turn,
generates proper branch annotations.
Here is an example using AMD's branch sampling:
$ perf record -a -b -c 1000037 -e cpu/branch-brs/ test_prg
$ perf report
Samples: 6M of event 'cpu/branch-brs/', Event count (approx.): 6901276
Overhead Command Source Shared Object Source Symbol Target Symbol Basic Block Cycle
99.65% test_prg test_prg [.] test_thread [.] test_thread -
0.02% test_prg [kernel.vmlinux] [k] asm_sysvec_apic_timer_interrupt [k] error_entry -
$ perf report -F overhead,comm,dso,addr_from,addr_to
Samples: 6M of event 'cpu/branch-brs/', Event count (approx.): 6901276
Overhead Command Shared Object Source Address Target Address
4.22% test_prg test_prg [.] test_thread+0x3c [.] test_thread+0x4
4.13% test_prg test_prg [.] test_thread+0x4 [.] test_thread+0x3a
4.09% test_prg test_prg [.] test_thread+0x3a [.] test_thread+0x6
4.08% test_prg test_prg [.] test_thread+0x2 [.] test_thread+0x3c
4.06% test_prg test_prg [.] test_thread+0x3e [.] test_thread+0x2
3.87% test_prg test_prg [.] test_thread+0x6 [.] test_thread+0x38
3.84% test_prg test_prg [.] test_thread [.] test_thread+0x3e
3.76% test_prg test_prg [.] test_thread+0x1e [.] test_thread
3.76% test_prg test_prg [.] test_thread+0x38 [.] test_thread+0x8
3.56% test_prg test_prg [.] test_thread+0x22 [.] test_thread+0x1e
3.54% test_prg test_prg [.] test_thread+0x8 [.] test_thread+0x36
3.47% test_prg test_prg [.] test_thread+0x1c [.] test_thread+0x22
3.45% test_prg test_prg [.] test_thread+0x36 [.] test_thread+0xa
3.28% test_prg test_prg [.] test_thread+0x24 [.] test_thread+0x1c
3.25% test_prg test_prg [.] test_thread+0xa [.] test_thread+0x34
3.24% test_prg test_prg [.] test_thread+0x1a [.] test_thread+0x24
3.20% test_prg test_prg [.] test_thread+0x34 [.] test_thread+0xc
3.04% test_prg test_prg [.] test_thread+0x26 [.] test_thread+0x1a
3.01% test_prg test_prg [.] test_thread+0xc [.] test_thread+0x32
2.98% test_prg test_prg [.] test_thread+0x18 [.] test_thread+0x26
2.94% test_prg test_prg [.] test_thread+0x32 [.] test_thread+0xe
2.76% test_prg test_prg [.] test_thread+0x28 [.] test_thread+0x18
2.73% test_prg test_prg [.] test_thread+0xe [.] test_thread+0x30
2.67% test_prg test_prg [.] test_thread+0x30 [.] test_thread+0x10
2.67% test_prg test_prg [.] test_thread+0x16 [.] test_thread+0x28
2.46% test_prg test_prg [.] test_thread+0x10 [.] test_thread+0x2e
2.44% test_prg test_prg [.] test_thread+0x2a [.] test_thread+0x16
2.38% test_prg test_prg [.] test_thread+0x14 [.] test_thread+0x2a
2.32% test_prg test_prg [.] test_thread+0x2e [.] test_thread+0x12
2.28% test_prg test_prg [.] test_thread+0x12 [.] test_thread+0x2c
2.16% test_prg test_prg [.] test_thread+0x2c [.] test_thread+0x14
0.02% test_prg [kernel.vmlinux] [k] asm_sysvec_apic_ti+0x5 [k] error_entry
Signed-off-by: Stephane Eranian <eranian@google.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Kim Phillips <kim.phillips@amd.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Song Liu <songliubraving@fb.com>
Link: http://lore.kernel.org/lkml/20220208211637.2221872-13-eranian@google.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2022-02-08 13:16:37 -08:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-11-04 15:57:38 -03:00
|
|
|
|
|
|
|
|
|
2017-02-17 17:17:38 +09:00
|
|
|
|
2013-04-01 20:35:19 +09:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
|
|
|
|
|
2023-03-20 14:22:35 -07:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
perf report: Add "addr_from" and "addr_to" sort dimensions
With the existing symbol_from/symbol_to, branches captured in the same
function would be collapsed into a single function if the latencies
associated with the each branch (cycles) were all the same. That is the
case on Intel Broadwell, for instance. Since Intel Skylake, the latency
is captured by hardware and therefore is used to disambiguate branches.
Add addr_from/addr_to sort dimensions to sort branches based on their
addresses and not the function there are in. The output is still the
function name but the offset within the function is provided to uniquely
identify each branch. These new sort dimensions also help with annotate
because they create different entries in the histogram which, in turn,
generates proper branch annotations.
Here is an example using AMD's branch sampling:
$ perf record -a -b -c 1000037 -e cpu/branch-brs/ test_prg
$ perf report
Samples: 6M of event 'cpu/branch-brs/', Event count (approx.): 6901276
Overhead Command Source Shared Object Source Symbol Target Symbol Basic Block Cycle
99.65% test_prg test_prg [.] test_thread [.] test_thread -
0.02% test_prg [kernel.vmlinux] [k] asm_sysvec_apic_timer_interrupt [k] error_entry -
$ perf report -F overhead,comm,dso,addr_from,addr_to
Samples: 6M of event 'cpu/branch-brs/', Event count (approx.): 6901276
Overhead Command Shared Object Source Address Target Address
4.22% test_prg test_prg [.] test_thread+0x3c [.] test_thread+0x4
4.13% test_prg test_prg [.] test_thread+0x4 [.] test_thread+0x3a
4.09% test_prg test_prg [.] test_thread+0x3a [.] test_thread+0x6
4.08% test_prg test_prg [.] test_thread+0x2 [.] test_thread+0x3c
4.06% test_prg test_prg [.] test_thread+0x3e [.] test_thread+0x2
3.87% test_prg test_prg [.] test_thread+0x6 [.] test_thread+0x38
3.84% test_prg test_prg [.] test_thread [.] test_thread+0x3e
3.76% test_prg test_prg [.] test_thread+0x1e [.] test_thread
3.76% test_prg test_prg [.] test_thread+0x38 [.] test_thread+0x8
3.56% test_prg test_prg [.] test_thread+0x22 [.] test_thread+0x1e
3.54% test_prg test_prg [.] test_thread+0x8 [.] test_thread+0x36
3.47% test_prg test_prg [.] test_thread+0x1c [.] test_thread+0x22
3.45% test_prg test_prg [.] test_thread+0x36 [.] test_thread+0xa
3.28% test_prg test_prg [.] test_thread+0x24 [.] test_thread+0x1c
3.25% test_prg test_prg [.] test_thread+0xa [.] test_thread+0x34
3.24% test_prg test_prg [.] test_thread+0x1a [.] test_thread+0x24
3.20% test_prg test_prg [.] test_thread+0x34 [.] test_thread+0xc
3.04% test_prg test_prg [.] test_thread+0x26 [.] test_thread+0x1a
3.01% test_prg test_prg [.] test_thread+0xc [.] test_thread+0x32
2.98% test_prg test_prg [.] test_thread+0x18 [.] test_thread+0x26
2.94% test_prg test_prg [.] test_thread+0x32 [.] test_thread+0xe
2.76% test_prg test_prg [.] test_thread+0x28 [.] test_thread+0x18
2.73% test_prg test_prg [.] test_thread+0xe [.] test_thread+0x30
2.67% test_prg test_prg [.] test_thread+0x30 [.] test_thread+0x10
2.67% test_prg test_prg [.] test_thread+0x16 [.] test_thread+0x28
2.46% test_prg test_prg [.] test_thread+0x10 [.] test_thread+0x2e
2.44% test_prg test_prg [.] test_thread+0x2a [.] test_thread+0x16
2.38% test_prg test_prg [.] test_thread+0x14 [.] test_thread+0x2a
2.32% test_prg test_prg [.] test_thread+0x2e [.] test_thread+0x12
2.28% test_prg test_prg [.] test_thread+0x12 [.] test_thread+0x2c
2.16% test_prg test_prg [.] test_thread+0x2c [.] test_thread+0x14
0.02% test_prg [kernel.vmlinux] [k] asm_sysvec_apic_ti+0x5 [k] error_entry
Signed-off-by: Stephane Eranian <eranian@google.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Kim Phillips <kim.phillips@amd.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Song Liu <songliubraving@fb.com>
Link: http://lore.kernel.org/lkml/20220208211637.2221872-13-eranian@google.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2022-02-08 13:16:37 -08:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
|
|
|
|
|
2016-05-20 13:15:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:44 -07:00
|
|
|
|
|
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-01 15:38:29 +02:00
|
|
|
|
|
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-20 12:56:33 +01:00
|
|
|
|
|
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
2015-10-05 20:06:08 +02:00
|
|
|
|
2024-05-07 11:35:44 -07:00
|
|
|
|
|
|
|
|
|
2015-10-05 20:06:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:44 -07:00
|
|
|
|
|
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-08-29 13:11:09 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-12-16 10:57:58 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-05 20:06:08 +02:00
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-25 21:45:32 +09:00
|
|
|
|
perf tools: Add 'cgroup_id' sort order keyword
This patch introduces a cgroup identifier entry field in perf report to
identify or distinguish data of different cgroups. It uses the device
number and inode number of cgroup namespace, included in perf data with
the new PERF_RECORD_NAMESPACES event, as cgroup identifier.
With the assumption that each container is created with it's own cgroup
namespace, this allows assessment/analysis of multiple containers at
once.
A simple test for this would be to clone a few processes passing
SIGCHILD & CLONE_NEWCROUP flags to each of them, execute shell and run
different workloads on each of those contexts, while running perf
record command with --namespaces option.
Shown below is the output of perf report, sorted with cgroup identifier,
on perf.data generated with the above test scenario, clearly indicating
one context's considerable use of kernel memory in comparison with
others:
$ perf report -s cgroup_id,sample --stdio
#
# Total Lost Samples: 0
#
# Samples: 5K of event 'kmem:kmalloc'
# Event count (approx.): 5965
#
# Overhead cgroup id (dev/inode) Samples
# ........ ..................... ............
#
81.27% 3/0xeffffffb 4848
16.24% 3/0xf00000d0 969
1.16% 3/0xf00000ce 69
0.82% 3/0xf00000cf 49
0.50% 0/0x0 30
While this is a start, there is further scope of improving this. For
example, instead of cgroup namespace's device and inode numbers, dev
and inode numbers of some or all namespaces may be used to distinguish
which processes are running in a given container context.
Also, scripts to map device and inode info to containers sounds
plausible for better tracing of containers.
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Alexei Starovoitov <ast@fb.com>
Cc: Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>
Cc: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
Cc: Brendan Gregg <brendan.d.gregg@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Eric Biederman <ebiederm@xmission.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sargun Dhillon <sargun@sargun.me>
Cc: Steven Rostedt <rostedt@goodmis.org>
Link: http://lkml.kernel.org/r/148891933338.25309.756882900782042645.stgit@hbathini.in.ibm.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2017-03-08 02:12:13 +05:30
|
|
|
|
2025-02-13 10:08:15 +01:00
|
|
|
|
2015-09-09 12:14:00 -03:00
|
|
|
|
2015-09-04 10:45:43 -04:00
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-07 16:54:58 +05:30
|
|
|
|
2013-01-24 16:10:35 +01:00
|
|
|
|
|
|
|
|
|
perf tools: Support data block and addr block
Two new data source fields, to indicate the block reasons of a load
instruction, are introduced on the Intel Sapphire Rapids server. The
fields can be used by the memory profiling.
Add a new sort function, SORT_MEM_BLOCKED, for the two fields.
For the previous platforms or the block reason is unknown, print "N/A"
for the block reason.
Add blocked as a default mem sort key for perf report and perf mem
report.
Committer testing:
So in machines without this capability we get a "N/A" filling the new "Blocked"
column:
$ perf mem record ls
arch certs CREDITS Documentation include ipc Kconfig lib MAINTAINERS mm samples security usr block
COPYING crypto drivers fs init Kbuild kernel LICENSES Makefile net README scripts sound tools
virt
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.008 MB perf.data (17 samples) ]
$
$ perf mem report --stdio
# To display the perf.data header info, please use --header/--header-only options.
#
# Total Lost Samples: 0
#
# Samples: 6 of event 'cpu/mem-loads,ldlat=30/Pu'
# Total weight : 1381
# Sort order : local_weight,mem,sym,dso,symbol_daddr,dso_daddr,snoop,tlb,locked,blocked
#
# Overhead Samples Local Weight Memory access Symbol Shared Object Data Symbol Data Object Snoop TLB access Locked Blocked
# ........ ....... ............ .................... ....................... ............. ...................... ............ ..... ............ ...... .......
#
32.87% 1 454 Local RAM or RAM hit [.] _dl_relocate_object ld-2.31.so [.] 0x00007fe91cef3078 libc-2.31.so Hit L1 or L2 hit No N/A
25.56% 1 353 LFB or LFB hit [.] strcmp ld-2.31.so [.] 0x00005586973855ca ls None L1 or L2 hit No N/A
22.59% 1 312 LFB or LFB hit [.] _dl_cache_libcmp ld-2.31.so [.] 0x00007fe91d0e3b18 ld.so.cache None L1 or L2 hit No N/A
8.47% 1 117 LFB or LFB hit [.] _dl_relocate_object ld-2.31.so [.] 0x00007fe91ceee570 libc-2.31.so None L1 or L2 hit No N/A
6.88% 1 95 LFB or LFB hit [.] _dl_relocate_object ld-2.31.so [.] 0x00007fe91ceed490 libc-2.31.so None L1 or L2 hit No N/A
3.62% 1 50 LFB or LFB hit [.] _dl_cache_libcmp ld-2.31.so [.] 0x00007fe91d0ebe60 ld.so.cache None L1 or L2 hit No N/A
# Samples: 11 of event 'cpu/mem-stores/Pu'
# Total weight : 11
# Sort order : local_weight,mem,sym,dso,symbol_daddr,dso_daddr,snoop,tlb,locked,blocked
#
# Overhead Samples Local Weight Memory access Symbol Shared Object Data Symbol Data Object Snoop TLB access Locked Blocked
# ........ ....... ............ ............. ....................... ............. ...................... ........... ..... .......... ...... .......
#
9.09% 1 0 L1 hit [.] __strcoll_l libc-2.31.so [.] 0x00007fffe5648fc8 [stack] N/A N/A N/A N/A
9.09% 1 0 L1 hit [.] _dl_lookup_symbol_x ld-2.31.so [.] 0x00007fffe56490b8 [stack] N/A N/A N/A N/A
9.09% 1 0 L1 hit [.] _dl_name_match_p ld-2.31.so [.] 0x00007fffe56487d8 [stack] N/A N/A N/A N/A
9.09% 1 0 L1 hit [.] _dl_start ld-2.31.so [.] start_time+0x0 ld-2.31.so N/A N/A N/A N/A
9.09% 1 0 L1 hit [.] _dl_sysdep_start ld-2.31.so [.] 0x00007fffe56494b8 [stack] N/A N/A N/A N/A
9.09% 1 0 L1 hit [.] do_lookup_x ld-2.31.so [.] 0x00007fffe5648ff8 [stack] N/A N/A N/A N/A
9.09% 1 0 L1 hit [.] do_lookup_x ld-2.31.so [.] 0x00007fffe5649064 [stack] N/A N/A N/A N/A
9.09% 1 0 L1 hit [.] do_lookup_x ld-2.31.so [.] 0x00007fffe5649130 [stack] N/A N/A N/A N/A
9.09% 1 0 L1 miss [.] _dl_start ld-2.31.so [.] _rtld_global+0xaf8 ld-2.31.so N/A N/A N/A N/A
9.09% 1 0 L1 miss [.] _dl_start ld-2.31.so [.] _rtld_global+0xc28 ld-2.31.so N/A N/A N/A N/A
9.09% 1 0 L1 miss [.] _dl_start ld-2.31.so [.] 0x00007fffe56495b8 [stack] N/A N/A N/A N/A
# (Tip: Show user configuration overrides: perf config --user --list)
$
Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: Jin Yao <yao.jin@linux.intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Link: http://lore.kernel.org/lkml/1612296553-21962-4-git-send-email-kan.liang@linux.intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2021-02-02 12:09:07 -08:00
|
|
|
|
2021-02-02 12:09:10 -08:00
|
|
|
|
|
|
|
|
|
2021-12-03 07:50:37 +05:30
|
|
|
|
|
|
|
|
|
2022-09-23 10:31:41 -07:00
|
|
|
|
2024-10-10 13:40:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-12-03 07:50:37 +05:30
|
|
|
|
2019-08-23 14:03:38 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-05 11:57:51 -08:00
|
|
|
|
2013-09-20 07:40:43 -07:00
|
|
|
|
2016-09-19 15:10:10 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-08-10 16:53:54 -03:00
|
|
|
|
2015-08-07 15:54:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-09-20 07:40:43 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-21 23:22:38 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-25 21:45:32 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-22 13:35:14 -08:00
|
|
|
|
2020-03-25 21:45:32 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-07-20 14:42:52 -03:00
|
|
|
|
|
|
|
|
|
2012-08-20 13:52:05 +09:00
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-08-20 13:52:05 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-14 14:25:37 +09:00
|
|
|
|
|
|
|
|
|
2010-04-19 13:32:50 +08:00
|
|
|
|
2010-05-09 13:02:23 -03:00
|
|
|
|
2010-04-19 13:32:50 +08:00
|
|
|
|
2014-01-14 14:25:37 +09:00
|
|
|
|
2010-04-19 13:32:50 +08:00
|
|
|
|
|
|
|
|
|
2014-01-14 14:25:37 +09:00
|
|
|
|
2010-04-19 13:32:50 +08:00
|
|
|
|
|
|
|
|
|
2014-01-14 14:25:37 +09:00
|
|
|
|
2010-04-19 13:32:50 +08:00
|
|
|
|
|
|
|
|
|
2014-01-14 14:25:37 +09:00
|
|
|
|
2010-04-19 13:32:50 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-11 07:44:54 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2012-10-04 21:49:43 +09:00
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2012-10-04 21:49:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-11 11:17:17 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-04 21:49:43 +09:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2012-10-04 21:49:43 +09:00
|
|
|
|
|
|
|
|
|
2014-01-14 14:25:37 +09:00
|
|
|
|
perf top: Reuse the 'report' hist_entry/hists classes
This actually fixes several problems we had in the old 'perf top':
1. Unresolved symbols not show, limitation that came from the old
"KernelTop" codebase, to solve it we would need to do changes
that would make sym_entry have most of the hist_entry fields.
2. It was using the number of samples, not the sum of sample->period.
And brings the --sort code that allows us to have all the views in
'perf report', for instance:
[root@emilia ~]# perf top --sort dso
PerfTop: 5903 irqs/sec kernel:77.5% exact: 0.0% [1000Hz cycles], (all, 8 CPUs)
------------------------------------------------------------------------------
31.59% libcrypto.so.1.0.0
21.55% [kernel]
18.57% libpython2.6.so.1.0
7.04% libc-2.12.so
6.99% _backend_agg.so
4.72% sshd
1.48% multiarray.so
1.39% libfreetype.so.6.3.22
1.37% perf
0.71% libgobject-2.0.so.0.2200.5
0.53% [tg3]
0.48% libglib-2.0.so.0.2200.5
0.44% libstdc++.so.6.0.13
0.40% libcairo.so.2.10800.8
0.38% libm-2.12.so
0.34% umath.so
0.30% libgdk-x11-2.0.so.0.1800.9
0.22% libpthread-2.12.so
0.20% libgtk-x11-2.0.so.0.1800.9
0.20% librt-2.12.so
0.15% _path.so
0.13% libpango-1.0.so.0.2800.1
0.11% libatlas.so.3.0
0.09% ft2font.so
0.09% libpangoft2-1.0.so.0.2800.1
0.08% libX11.so.6.3.0
0.07% [vdso]
0.06% cyclictest
^C
All the filter lists can be used as well: --dsos, --comms, --symbols,
etc.
The 'perf report' TUI is also reused, being possible to apply all the
zoom operations, do annotation, etc.
This change will allow multiple simplifications in the symbol system as
well, that will be detailed in upcoming changesets.
Cc: David Ahern <dsahern@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Link: http://lkml.kernel.org/n/tip-xzaaldxq7zhqrrxdxjifk1mh@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-10-05 19:16:15 -03:00
|
|
|
|
2014-01-14 14:25:37 +09:00
|
|
|
|
|
|
|
|
|
2024-04-11 11:17:17 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
perf top: Reuse the 'report' hist_entry/hists classes
This actually fixes several problems we had in the old 'perf top':
1. Unresolved symbols not show, limitation that came from the old
"KernelTop" codebase, to solve it we would need to do changes
that would make sym_entry have most of the hist_entry fields.
2. It was using the number of samples, not the sum of sample->period.
And brings the --sort code that allows us to have all the views in
'perf report', for instance:
[root@emilia ~]# perf top --sort dso
PerfTop: 5903 irqs/sec kernel:77.5% exact: 0.0% [1000Hz cycles], (all, 8 CPUs)
------------------------------------------------------------------------------
31.59% libcrypto.so.1.0.0
21.55% [kernel]
18.57% libpython2.6.so.1.0
7.04% libc-2.12.so
6.99% _backend_agg.so
4.72% sshd
1.48% multiarray.so
1.39% libfreetype.so.6.3.22
1.37% perf
0.71% libgobject-2.0.so.0.2200.5
0.53% [tg3]
0.48% libglib-2.0.so.0.2200.5
0.44% libstdc++.so.6.0.13
0.40% libcairo.so.2.10800.8
0.38% libm-2.12.so
0.34% umath.so
0.30% libgdk-x11-2.0.so.0.1800.9
0.22% libpthread-2.12.so
0.20% libgtk-x11-2.0.so.0.1800.9
0.20% librt-2.12.so
0.15% _path.so
0.13% libpango-1.0.so.0.2800.1
0.11% libatlas.so.3.0
0.09% ft2font.so
0.09% libpangoft2-1.0.so.0.2800.1
0.08% libX11.so.6.3.0
0.07% [vdso]
0.06% cyclictest
^C
All the filter lists can be used as well: --dsos, --comms, --symbols,
etc.
The 'perf report' TUI is also reused, being possible to apply all the
zoom operations, do annotation, etc.
This change will allow multiple simplifications in the symbol system as
well, that will be detailed in upcoming changesets.
Cc: David Ahern <dsahern@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Link: http://lkml.kernel.org/n/tip-xzaaldxq7zhqrrxdxjifk1mh@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-10-05 19:16:15 -03:00
|
|
|
|
|
|
|
|
|
2025-04-30 13:55:41 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-04-30 13:55:42 -07:00
|
|
|
|
|
|
|
|
|
2025-04-30 13:55:41 -07:00
|
|
|
|
2025-04-30 13:55:42 -07:00
|
|
|
|
2025-04-30 13:55:41 -07:00
|
|
|
|
perf hist: Hide unused mem stat columns
Some mem_stat types don't use all 8 columns. And there are cases only
samples in certain kinds of mem_stat types are available only. For that
case hide columns which has no samples.
The new output for the previous data would be:
$ perf mem report -F overhead,op,comm --stdio
...
# ------ Mem Op -------
# Overhead Load Store Other Command
# ........ ..................... ...............
#
44.85% 21.1% 30.7% 48.3% swapper
26.82% 98.8% 0.3% 0.9% netsli-prober
7.19% 51.7% 13.7% 34.6% perf
5.81% 89.7% 2.2% 8.1% qemu-system-ppc
4.77% 100.0% 0.0% 0.0% notifications_c
1.77% 95.9% 1.2% 3.0% MemoryReleaser
0.77% 71.6% 4.1% 24.3% DefaultEventMan
0.19% 66.7% 22.2% 11.1% gnome-shell
...
On Intel machines, the event is only for loads or stores so it'll have
only one column:
# Mem Op
# Overhead Load Command
# ........ ....... ...............
#
20.55% 100.0% swapper
17.13% 100.0% chrome
9.02% 100.0% data-loop.0
6.26% 100.0% pipewire-pulse
5.63% 100.0% threaded-ml
5.47% 100.0% GraphRunner
5.37% 100.0% AudioIP~allback
5.30% 100.0% Chrome_ChildIOT
3.17% 100.0% Isolated Web Co
...
Committer testing:
# grep "model name" -m1 /proc/cpuinfo
model name : AMD Ryzen 9 9950X3D 16-Core Processo
# perf mem report -F overhead,op,comm --stdio
# Total Lost Samples: 0
#
# Samples: 2K of event 'cycles:P'
# Total weight : 2637
# Sort order : local_weight,mem,sym,dso,symbol_daddr,dso_daddr,snoop,tlb,locked,blocked,local_ins_lat,local_p_stage_cyc
#
# ------ Mem Op -------
# Overhead Load Store Other Command
# ........ ..................... ...............
#
61.02% 14.4% 25.5% 60.1% swapper
5.61% 26.4% 13.5% 60.1% Isolated Web Co
5.50% 21.4% 29.7% 49.0% perf
4.74% 27.2% 15.2% 57.6% gnome-shell
4.63% 33.6% 11.5% 54.9% mdns_service
4.29% 28.3% 12.4% 59.3% ptyxis
2.16% 24.6% 19.3% 56.1% DOM Worker
0.99% 23.1% 34.6% 42.3% firefox
0.72% 26.3% 15.8% 57.9% IPC I/O Parent
0.61% 12.5% 12.5% 75.0% kworker/u130:20
0.61% 37.5% 18.8% 43.8% podman
0.57% 33.3% 6.7% 60.0% Timer
0.53% 14.3% 7.1% 78.6% KMS thread
0.49% 30.8% 7.7% 61.5% kworker/u130:3-
0.46% 41.7% 33.3% 25.0% IPDL Background
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Ian Rogers <irogers@google.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Kan Liang <kan.liang@linux.intel.com>
Cc: Leo Yan <leo.yan@arm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ravi Bangoria <ravi.bangoria@amd.com>
Link: https://lore.kernel.org/r/20250430205548.789750-9-namhyung@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2025-04-30 13:55:45 -07:00
|
|
|
|
2025-04-30 13:55:41 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:49 +09:00
|
|
|
|
|
|
|
|
|
perf top: Reuse the 'report' hist_entry/hists classes
This actually fixes several problems we had in the old 'perf top':
1. Unresolved symbols not show, limitation that came from the old
"KernelTop" codebase, to solve it we would need to do changes
that would make sym_entry have most of the hist_entry fields.
2. It was using the number of samples, not the sum of sample->period.
And brings the --sort code that allows us to have all the views in
'perf report', for instance:
[root@emilia ~]# perf top --sort dso
PerfTop: 5903 irqs/sec kernel:77.5% exact: 0.0% [1000Hz cycles], (all, 8 CPUs)
------------------------------------------------------------------------------
31.59% libcrypto.so.1.0.0
21.55% [kernel]
18.57% libpython2.6.so.1.0
7.04% libc-2.12.so
6.99% _backend_agg.so
4.72% sshd
1.48% multiarray.so
1.39% libfreetype.so.6.3.22
1.37% perf
0.71% libgobject-2.0.so.0.2200.5
0.53% [tg3]
0.48% libglib-2.0.so.0.2200.5
0.44% libstdc++.so.6.0.13
0.40% libcairo.so.2.10800.8
0.38% libm-2.12.so
0.34% umath.so
0.30% libgdk-x11-2.0.so.0.1800.9
0.22% libpthread-2.12.so
0.20% libgtk-x11-2.0.so.0.1800.9
0.20% librt-2.12.so
0.15% _path.so
0.13% libpango-1.0.so.0.2800.1
0.11% libatlas.so.3.0
0.09% ft2font.so
0.09% libpangoft2-1.0.so.0.2800.1
0.08% libX11.so.6.3.0
0.07% [vdso]
0.06% cyclictest
^C
All the filter lists can be used as well: --dsos, --comms, --symbols,
etc.
The 'perf report' TUI is also reused, being possible to apply all the
zoom operations, do annotation, etc.
This change will allow multiple simplifications in the symbol system as
well, that will be detailed in upcoming changesets.
Cc: David Ahern <dsahern@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Link: http://lkml.kernel.org/n/tip-xzaaldxq7zhqrrxdxjifk1mh@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-10-05 19:16:15 -03:00
|
|
|
|
|
|
|
|
|
2012-10-04 21:49:41 +09:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2011-10-20 06:45:44 -02:00
|
|
|
|
|
|
|
|
|
2011-10-13 08:01:33 -03:00
|
|
|
|
2011-10-20 06:45:44 -02:00
|
|
|
|
2014-01-14 14:25:37 +09:00
|
|
|
|
2012-09-11 13:15:07 +09:00
|
|
|
|
|
|
|
|
|
2016-01-05 12:06:00 +09:00
|
|
|
|
2025-04-30 13:55:41 -07:00
|
|
|
|
2011-10-20 06:45:44 -02:00
|
|
|
|
2016-02-25 00:13:49 +09:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:49 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:49 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-20 06:45:44 -02:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
perf top: Reuse the 'report' hist_entry/hists classes
This actually fixes several problems we had in the old 'perf top':
1. Unresolved symbols not show, limitation that came from the old
"KernelTop" codebase, to solve it we would need to do changes
that would make sym_entry have most of the hist_entry fields.
2. It was using the number of samples, not the sum of sample->period.
And brings the --sort code that allows us to have all the views in
'perf report', for instance:
[root@emilia ~]# perf top --sort dso
PerfTop: 5903 irqs/sec kernel:77.5% exact: 0.0% [1000Hz cycles], (all, 8 CPUs)
------------------------------------------------------------------------------
31.59% libcrypto.so.1.0.0
21.55% [kernel]
18.57% libpython2.6.so.1.0
7.04% libc-2.12.so
6.99% _backend_agg.so
4.72% sshd
1.48% multiarray.so
1.39% libfreetype.so.6.3.22
1.37% perf
0.71% libgobject-2.0.so.0.2200.5
0.53% [tg3]
0.48% libglib-2.0.so.0.2200.5
0.44% libstdc++.so.6.0.13
0.40% libcairo.so.2.10800.8
0.38% libm-2.12.so
0.34% umath.so
0.30% libgdk-x11-2.0.so.0.1800.9
0.22% libpthread-2.12.so
0.20% libgtk-x11-2.0.so.0.1800.9
0.20% librt-2.12.so
0.15% _path.so
0.13% libpango-1.0.so.0.2800.1
0.11% libatlas.so.3.0
0.09% ft2font.so
0.09% libpangoft2-1.0.so.0.2800.1
0.08% libX11.so.6.3.0
0.07% [vdso]
0.06% cyclictest
^C
All the filter lists can be used as well: --dsos, --comms, --symbols,
etc.
The 'perf report' TUI is also reused, being possible to apply all the
zoom operations, do annotation, etc.
This change will allow multiple simplifications in the symbol system as
well, that will be detailed in upcoming changesets.
Cc: David Ahern <dsahern@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Link: http://lkml.kernel.org/n/tip-xzaaldxq7zhqrrxdxjifk1mh@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-10-05 19:16:15 -03:00
|
|
|
|
|
|
|
|
|
2014-12-19 12:41:28 -03:00
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2014-12-19 12:41:28 -03:00
|
|
|
|
2016-02-25 00:13:49 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-03 13:54:42 +02:00
|
|
|
|
2016-02-25 00:13:49 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2014-12-19 12:41:28 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-05-14 11:09:01 +09:00
|
|
|
|
perf top: Reuse the 'report' hist_entry/hists classes
This actually fixes several problems we had in the old 'perf top':
1. Unresolved symbols not show, limitation that came from the old
"KernelTop" codebase, to solve it we would need to do changes
that would make sym_entry have most of the hist_entry fields.
2. It was using the number of samples, not the sum of sample->period.
And brings the --sort code that allows us to have all the views in
'perf report', for instance:
[root@emilia ~]# perf top --sort dso
PerfTop: 5903 irqs/sec kernel:77.5% exact: 0.0% [1000Hz cycles], (all, 8 CPUs)
------------------------------------------------------------------------------
31.59% libcrypto.so.1.0.0
21.55% [kernel]
18.57% libpython2.6.so.1.0
7.04% libc-2.12.so
6.99% _backend_agg.so
4.72% sshd
1.48% multiarray.so
1.39% libfreetype.so.6.3.22
1.37% perf
0.71% libgobject-2.0.so.0.2200.5
0.53% [tg3]
0.48% libglib-2.0.so.0.2200.5
0.44% libstdc++.so.6.0.13
0.40% libcairo.so.2.10800.8
0.38% libm-2.12.so
0.34% umath.so
0.30% libgdk-x11-2.0.so.0.1800.9
0.22% libpthread-2.12.so
0.20% libgtk-x11-2.0.so.0.1800.9
0.20% librt-2.12.so
0.15% _path.so
0.13% libpango-1.0.so.0.2800.1
0.11% libatlas.so.3.0
0.09% ft2font.so
0.09% libpangoft2-1.0.so.0.2800.1
0.08% libX11.so.6.3.0
0.07% [vdso]
0.06% cyclictest
^C
All the filter lists can be used as well: --dsos, --comms, --symbols,
etc.
The 'perf report' TUI is also reused, being possible to apply all the
zoom operations, do annotation, etc.
This change will allow multiple simplifications in the symbol system as
well, that will be detailed in upcoming changesets.
Cc: David Ahern <dsahern@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Link: http://lkml.kernel.org/n/tip-xzaaldxq7zhqrrxdxjifk1mh@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-10-05 19:16:15 -03:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
perf top: Reuse the 'report' hist_entry/hists classes
This actually fixes several problems we had in the old 'perf top':
1. Unresolved symbols not show, limitation that came from the old
"KernelTop" codebase, to solve it we would need to do changes
that would make sym_entry have most of the hist_entry fields.
2. It was using the number of samples, not the sum of sample->period.
And brings the --sort code that allows us to have all the views in
'perf report', for instance:
[root@emilia ~]# perf top --sort dso
PerfTop: 5903 irqs/sec kernel:77.5% exact: 0.0% [1000Hz cycles], (all, 8 CPUs)
------------------------------------------------------------------------------
31.59% libcrypto.so.1.0.0
21.55% [kernel]
18.57% libpython2.6.so.1.0
7.04% libc-2.12.so
6.99% _backend_agg.so
4.72% sshd
1.48% multiarray.so
1.39% libfreetype.so.6.3.22
1.37% perf
0.71% libgobject-2.0.so.0.2200.5
0.53% [tg3]
0.48% libglib-2.0.so.0.2200.5
0.44% libstdc++.so.6.0.13
0.40% libcairo.so.2.10800.8
0.38% libm-2.12.so
0.34% umath.so
0.30% libgdk-x11-2.0.so.0.1800.9
0.22% libpthread-2.12.so
0.20% libgtk-x11-2.0.so.0.1800.9
0.20% librt-2.12.so
0.15% _path.so
0.13% libpango-1.0.so.0.2800.1
0.11% libatlas.so.3.0
0.09% ft2font.so
0.09% libpangoft2-1.0.so.0.2800.1
0.08% libX11.so.6.3.0
0.07% [vdso]
0.06% cyclictest
^C
All the filter lists can be used as well: --dsos, --comms, --symbols,
etc.
The 'perf report' TUI is also reused, being possible to apply all the
zoom operations, do annotation, etc.
This change will allow multiple simplifications in the symbol system as
well, that will be detailed in upcoming changesets.
Cc: David Ahern <dsahern@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Link: http://lkml.kernel.org/n/tip-xzaaldxq7zhqrrxdxjifk1mh@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-10-05 19:16:15 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-17 09:05:04 -02:00
|
|
|
|
|
|
|
|
|
2015-03-17 17:18:58 -03:00
|
|
|
|
2014-12-19 12:41:28 -03:00
|
|
|
|
perf top: Reuse the 'report' hist_entry/hists classes
This actually fixes several problems we had in the old 'perf top':
1. Unresolved symbols not show, limitation that came from the old
"KernelTop" codebase, to solve it we would need to do changes
that would make sym_entry have most of the hist_entry fields.
2. It was using the number of samples, not the sum of sample->period.
And brings the --sort code that allows us to have all the views in
'perf report', for instance:
[root@emilia ~]# perf top --sort dso
PerfTop: 5903 irqs/sec kernel:77.5% exact: 0.0% [1000Hz cycles], (all, 8 CPUs)
------------------------------------------------------------------------------
31.59% libcrypto.so.1.0.0
21.55% [kernel]
18.57% libpython2.6.so.1.0
7.04% libc-2.12.so
6.99% _backend_agg.so
4.72% sshd
1.48% multiarray.so
1.39% libfreetype.so.6.3.22
1.37% perf
0.71% libgobject-2.0.so.0.2200.5
0.53% [tg3]
0.48% libglib-2.0.so.0.2200.5
0.44% libstdc++.so.6.0.13
0.40% libcairo.so.2.10800.8
0.38% libm-2.12.so
0.34% umath.so
0.30% libgdk-x11-2.0.so.0.1800.9
0.22% libpthread-2.12.so
0.20% libgtk-x11-2.0.so.0.1800.9
0.20% librt-2.12.so
0.15% _path.so
0.13% libpango-1.0.so.0.2800.1
0.11% libatlas.so.3.0
0.09% ft2font.so
0.09% libpangoft2-1.0.so.0.2800.1
0.08% libX11.so.6.3.0
0.07% [vdso]
0.06% cyclictest
^C
All the filter lists can be used as well: --dsos, --comms, --symbols,
etc.
The 'perf report' TUI is also reused, being possible to apply all the
zoom operations, do annotation, etc.
This change will allow multiple simplifications in the symbol system as
well, that will be detailed in upcoming changesets.
Cc: David Ahern <dsahern@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Link: http://lkml.kernel.org/n/tip-xzaaldxq7zhqrrxdxjifk1mh@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-10-05 19:16:15 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-08-12 17:16:05 +09:00
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2014-08-12 17:16:05 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-19 12:41:28 -03:00
|
|
|
|
2014-08-12 17:16:05 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-06-28 17:23:03 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2010-05-14 14:19:35 -03:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
|
|
|
|
|
2018-06-07 14:19:54 -03:00
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
|
|
|
|
|
2018-06-07 14:19:54 -03:00
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-22 13:35:14 -08:00
|
|
|
|
2023-04-04 13:59:49 -07:00
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-05 16:25:30 +01:00
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-22 13:35:14 -08:00
|
|
|
|
2023-04-04 13:59:49 -07:00
|
|
|
|
2026-01-22 13:35:14 -08:00
|
|
|
|
2023-04-04 13:59:49 -07:00
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
|
|
|
|
|
2024-07-31 16:55:00 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
perf hists: Check if a hist_entry has callchains before using them
So far if we use 'perf record -g' this will make
symbol_conf.use_callchain 'true' and logic will assume that all events
have callchains enabled, but ever since we added the possibility of
setting up callchains for some events (e.g.: -e
cycles/call-graph=dwarf/) while not for others, we limit usage scenarios
by looking at that symbol_conf.use_callchain global boolean, we better
look at each event attributes.
On the road to that we need to look if a hist_entry has callchains, that
is, to go from hist_entry->hists to the evsel that contains it, to then
look at evsel->sample_type for PERF_SAMPLE_CALLCHAIN.
The next step is to add a symbol_conf.ignore_callchains global, to use
in the places where what we really want to know is if callchains should
be ignored, even if present.
Then -g will mean just to select a callchain mode to be applied to all
events not explicitely setting some other callchain mode, i.e. a default
callchain mode, and --no-call-graph will set
symbol_conf.ignore_callchains with that clear intention.
That too will at some point become a per evsel thing, that tools can set
for all or just a few of its evsels.
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: David Ahern <dsahern@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>
Link: https://lkml.kernel.org/n/tip-0sas5cm4dsw2obn75g7ruz69@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2018-05-29 13:59:24 -03:00
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-05 16:25:30 +01:00
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
2019-03-05 16:25:31 +01:00
|
|
|
|
2023-06-12 11:10:46 -03:00
|
|
|
|
2019-03-05 16:25:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-11 07:44:58 -07:00
|
|
|
|
2024-01-06 17:41:29 +08:00
|
|
|
|
|
|
|
|
|
2019-03-11 07:44:58 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
2023-06-08 16:28:17 -07:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-05 16:25:30 +01:00
|
|
|
|
2019-03-11 07:44:58 -07:00
|
|
|
|
2019-07-04 12:06:20 -03:00
|
|
|
|
2019-03-11 07:44:58 -07:00
|
|
|
|
2019-03-05 16:25:31 +01:00
|
|
|
|
2019-07-04 12:06:20 -03:00
|
|
|
|
2019-03-05 16:25:31 +01:00
|
|
|
|
2019-03-05 16:25:30 +01:00
|
|
|
|
|
|
|
|
|
2023-10-24 15:23:14 -07:00
|
|
|
|
|
|
|
|
|
2019-07-04 12:06:20 -03:00
|
|
|
|
2019-03-05 16:25:30 +01:00
|
|
|
|
2025-11-22 00:19:18 -08:00
|
|
|
|
|
|
|
|
|
2019-03-05 16:25:30 +01:00
|
|
|
|
2023-10-24 15:23:14 -07:00
|
|
|
|
2019-07-04 12:06:20 -03:00
|
|
|
|
2019-03-05 16:25:30 +01:00
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-11 13:34:27 +09:00
|
|
|
|
|
|
|
|
|
2010-05-09 13:02:23 -03:00
|
|
|
|
2016-07-05 08:56:04 +02:00
|
|
|
|
2012-09-11 13:15:07 +09:00
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
2012-09-11 13:15:07 +09:00
|
|
|
|
2016-07-05 08:56:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-22 13:44:14 +09:00
|
|
|
|
2012-09-11 13:15:07 +09:00
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:04 +02:00
|
|
|
|
2016-07-05 08:56:03 +02:00
|
|
|
|
2018-06-07 14:19:54 -03:00
|
|
|
|
2016-07-05 08:56:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-09 13:02:23 -03:00
|
|
|
|
2012-01-04 12:27:03 -02:00
|
|
|
|
2010-05-09 13:02:23 -03:00
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:16 +01:00
|
|
|
|
2010-07-21 09:19:41 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2016-02-16 23:08:19 +09:00
|
|
|
|
perf hists: Check if a hist_entry has callchains before using them
So far if we use 'perf record -g' this will make
symbol_conf.use_callchain 'true' and logic will assume that all events
have callchains enabled, but ever since we added the possibility of
setting up callchains for some events (e.g.: -e
cycles/call-graph=dwarf/) while not for others, we limit usage scenarios
by looking at that symbol_conf.use_callchain global boolean, we better
look at each event attributes.
On the road to that we need to look if a hist_entry has callchains, that
is, to go from hist_entry->hists to the evsel that contains it, to then
look at evsel->sample_type for PERF_SAMPLE_CALLCHAIN.
The next step is to add a symbol_conf.ignore_callchains global, to use
in the places where what we really want to know is if callchains should
be ignored, even if present.
Then -g will mean just to select a callchain mode to be applied to all
events not explicitely setting some other callchain mode, i.e. a default
callchain mode, and --no-call-graph will set
symbol_conf.ignore_callchains with that clear intention.
That too will at some point become a per evsel thing, that tools can set
for all or just a few of its evsels.
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: David Ahern <dsahern@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>
Link: https://lkml.kernel.org/n/tip-0sas5cm4dsw2obn75g7ruz69@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2018-05-29 13:59:24 -03:00
|
|
|
|
2016-02-16 23:08:19 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
|
|
|
|
|
2016-02-16 23:08:19 +09:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
|
|
|
|
|
2016-02-16 23:08:19 +09:00
|
|
|
|
|
|
|
|
|
2015-05-19 11:31:22 -03:00
|
|
|
|
|
|
|
|
|
2023-06-08 16:28:03 -07:00
|
|
|
|
2015-05-19 11:31:22 -03:00
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
|
|
|
|
|
2013-10-01 07:22:15 -07:00
|
|
|
|
2013-12-18 14:21:11 +09:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
|
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
2012-12-10 17:29:54 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
2016-01-28 00:40:49 +09:00
|
|
|
|
2024-04-11 11:17:17 -07:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2016-01-28 00:40:49 +09:00
|
|
|
|
2012-09-11 13:15:07 +09:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2012-03-27 03:14:18 -04:00
|
|
|
|
2024-05-07 11:35:40 -07:00
|
|
|
|
2019-06-28 17:22:59 +08:00
|
|
|
|
2023-03-20 14:16:18 +08:00
|
|
|
|
|
|
|
|
|
2012-03-27 03:14:18 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
perf report: Fix segfault when 'sym' sort key is not used
The fields in the hist_entry are filled on-demand which means they only
have meaningful values when relevant sort keys are used.
So if neither of 'dso' nor 'sym' sort keys are used, the map/symbols in
the hist entry can be garbage. So it shouldn't access it
unconditionally.
I got a segfault, when I wanted to see cgroup profiles.
$ sudo perf record -a --all-cgroups --synth=cgroup true
$ sudo perf report -s cgroup
Program received signal SIGSEGV, Segmentation fault.
0x00005555557a8d90 in map__dso (map=0x0) at util/map.h:48
48 return RC_CHK_ACCESS(map)->dso;
(gdb) bt
#0 0x00005555557a8d90 in map__dso (map=0x0) at util/map.h:48
#1 0x00005555557aa39b in map__load (map=0x0) at util/map.c:344
#2 0x00005555557aa592 in map__find_symbol (map=0x0, addr=140736115941088) at util/map.c:385
#3 0x00005555557ef000 in hists__findnew_entry (hists=0x555556039d60, entry=0x7fffffffa4c0, al=0x7fffffffa8c0, sample_self=true)
at util/hist.c:644
#4 0x00005555557ef61c in __hists__add_entry (hists=0x555556039d60, al=0x7fffffffa8c0, sym_parent=0x0, bi=0x0, mi=0x0, ki=0x0,
block_info=0x0, sample=0x7fffffffaa90, sample_self=true, ops=0x0) at util/hist.c:761
#5 0x00005555557ef71f in hists__add_entry (hists=0x555556039d60, al=0x7fffffffa8c0, sym_parent=0x0, bi=0x0, mi=0x0, ki=0x0,
sample=0x7fffffffaa90, sample_self=true) at util/hist.c:779
#6 0x00005555557f00fb in iter_add_single_normal_entry (iter=0x7fffffffa900, al=0x7fffffffa8c0) at util/hist.c:1015
#7 0x00005555557f09a7 in hist_entry_iter__add (iter=0x7fffffffa900, al=0x7fffffffa8c0, max_stack_depth=127, arg=0x7fffffffbce0)
at util/hist.c:1260
#8 0x00005555555ba7ce in process_sample_event (tool=0x7fffffffbce0, event=0x7ffff7c14128, sample=0x7fffffffaa90, evsel=0x555556039ad0,
machine=0x5555560388e8) at builtin-report.c:334
#9 0x00005555557b30c8 in evlist__deliver_sample (evlist=0x555556039010, tool=0x7fffffffbce0, event=0x7ffff7c14128,
sample=0x7fffffffaa90, evsel=0x555556039ad0, machine=0x5555560388e8) at util/session.c:1232
#10 0x00005555557b32bc in machines__deliver_event (machines=0x5555560388e8, evlist=0x555556039010, event=0x7ffff7c14128,
sample=0x7fffffffaa90, tool=0x7fffffffbce0, file_offset=110888, file_path=0x555556038ff0 "perf.data") at util/session.c:1271
#11 0x00005555557b3848 in perf_session__deliver_event (session=0x5555560386d0, event=0x7ffff7c14128, tool=0x7fffffffbce0,
file_offset=110888, file_path=0x555556038ff0 "perf.data") at util/session.c:1354
#12 0x00005555557affaf in ordered_events__deliver_event (oe=0x555556038e60, event=0x555556135aa0) at util/session.c:132
#13 0x00005555557bb605 in do_flush (oe=0x555556038e60, show_progress=false) at util/ordered-events.c:245
#14 0x00005555557bb95c in __ordered_events__flush (oe=0x555556038e60, how=OE_FLUSH__ROUND, timestamp=0) at util/ordered-events.c:324
#15 0x00005555557bba46 in ordered_events__flush (oe=0x555556038e60, how=OE_FLUSH__ROUND) at util/ordered-events.c:342
#16 0x00005555557b1b3b in perf_event__process_finished_round (tool=0x7fffffffbce0, event=0x7ffff7c15bb8, oe=0x555556038e60)
at util/session.c:780
#17 0x00005555557b3b27 in perf_session__process_user_event (session=0x5555560386d0, event=0x7ffff7c15bb8, file_offset=117688,
file_path=0x555556038ff0 "perf.data") at util/session.c:1406
As you can see the entry->ms.map was NULL even if he->ms.map has a
value. This is because 'sym' sort key is not given, so it cannot assume
whether he->ms.sym and entry->ms.sym is the same. I only checked the
'sym' sort key here as it implies 'dso' behavior (so maps are the same).
Fixes: ac01c8c4246546fd ("perf hist: Update hist symbol when updating maps")
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Ian Rogers <irogers@google.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Kan Liang <kan.liang@linux.intel.com>
Cc: Matt Fleming <matt@readmodwrite.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Link: https://lore.kernel.org/r/20240826221045.1202305-2-namhyung@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2024-08-26 15:10:42 -07:00
|
|
|
|
2024-08-15 15:22:12 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-15 23:29:51 -03:00
|
|
|
|
|
|
|
|
|
2012-03-27 03:14:18 -04:00
|
|
|
|
2010-05-09 13:02:23 -03:00
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
|
|
|
|
|
2012-09-11 13:34:27 +09:00
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
2013-05-14 11:09:02 +09:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2016-01-28 00:40:49 +09:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2016-02-16 23:08:19 +09:00
|
|
|
|
2014-12-22 13:44:09 +09:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2010-05-09 13:02:23 -03:00
|
|
|
|
2012-09-11 13:34:27 +09:00
|
|
|
|
|
|
|
|
|
2012-09-11 13:15:07 +09:00
|
|
|
|
|
|
|
|
|
2025-04-30 13:55:41 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-10-03 10:42:45 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-11 07:44:58 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2019-06-28 17:22:59 +08:00
|
|
|
|
2016-07-05 08:56:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
perf tools: Add 'cgroup_id' sort order keyword
This patch introduces a cgroup identifier entry field in perf report to
identify or distinguish data of different cgroups. It uses the device
number and inode number of cgroup namespace, included in perf data with
the new PERF_RECORD_NAMESPACES event, as cgroup identifier.
With the assumption that each container is created with it's own cgroup
namespace, this allows assessment/analysis of multiple containers at
once.
A simple test for this would be to clone a few processes passing
SIGCHILD & CLONE_NEWCROUP flags to each of them, execute shell and run
different workloads on each of those contexts, while running perf
record command with --namespaces option.
Shown below is the output of perf report, sorted with cgroup identifier,
on perf.data generated with the above test scenario, clearly indicating
one context's considerable use of kernel memory in comparison with
others:
$ perf report -s cgroup_id,sample --stdio
#
# Total Lost Samples: 0
#
# Samples: 5K of event 'kmem:kmalloc'
# Event count (approx.): 5965
#
# Overhead cgroup id (dev/inode) Samples
# ........ ..................... ............
#
81.27% 3/0xeffffffb 4848
16.24% 3/0xf00000d0 969
1.16% 3/0xf00000ce 69
0.82% 3/0xf00000cf 49
0.50% 0/0x0 30
While this is a start, there is further scope of improving this. For
example, instead of cgroup namespace's device and inode numbers, dev
and inode numbers of some or all namespaces may be used to distinguish
which processes are running in a given container context.
Also, scripts to map device and inode info to containers sounds
plausible for better tracing of containers.
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Alexei Starovoitov <ast@fb.com>
Cc: Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>
Cc: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
Cc: Brendan Gregg <brendan.d.gregg@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Eric Biederman <ebiederm@xmission.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sargun Dhillon <sargun@sargun.me>
Cc: Steven Rostedt <rostedt@goodmis.org>
Link: http://lkml.kernel.org/r/148891933338.25309.756882900782042645.stgit@hbathini.in.ibm.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2017-03-08 02:12:13 +05:30
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
|
|
|
|
|
2013-09-13 16:28:57 +09:00
|
|
|
|
perf tools: Add 'cgroup_id' sort order keyword
This patch introduces a cgroup identifier entry field in perf report to
identify or distinguish data of different cgroups. It uses the device
number and inode number of cgroup namespace, included in perf data with
the new PERF_RECORD_NAMESPACES event, as cgroup identifier.
With the assumption that each container is created with it's own cgroup
namespace, this allows assessment/analysis of multiple containers at
once.
A simple test for this would be to clone a few processes passing
SIGCHILD & CLONE_NEWCROUP flags to each of them, execute shell and run
different workloads on each of those contexts, while running perf
record command with --namespaces option.
Shown below is the output of perf report, sorted with cgroup identifier,
on perf.data generated with the above test scenario, clearly indicating
one context's considerable use of kernel memory in comparison with
others:
$ perf report -s cgroup_id,sample --stdio
#
# Total Lost Samples: 0
#
# Samples: 5K of event 'kmem:kmalloc'
# Event count (approx.): 5965
#
# Overhead cgroup id (dev/inode) Samples
# ........ ..................... ............
#
81.27% 3/0xeffffffb 4848
16.24% 3/0xf00000d0 969
1.16% 3/0xf00000ce 69
0.82% 3/0xf00000cf 49
0.50% 0/0x0 30
While this is a start, there is further scope of improving this. For
example, instead of cgroup namespace's device and inode numbers, dev
and inode numbers of some or all namespaces may be used to distinguish
which processes are running in a given container context.
Also, scripts to map device and inode info to containers sounds
plausible for better tracing of containers.
Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Alexei Starovoitov <ast@fb.com>
Cc: Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>
Cc: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
Cc: Brendan Gregg <brendan.d.gregg@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Eric Biederman <ebiederm@xmission.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sargun Dhillon <sargun@sargun.me>
Cc: Steven Rostedt <rostedt@goodmis.org>
Link: http://lkml.kernel.org/r/148891933338.25309.756882900782042645.stgit@hbathini.in.ibm.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2017-03-08 02:12:13 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-25 21:45:32 +09:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
2026-01-22 13:35:14 -08:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-05 16:25:31 +01:00
|
|
|
|
2015-09-04 10:45:42 -04:00
|
|
|
|
2014-05-27 12:28:05 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-05 11:57:51 -08:00
|
|
|
|
2025-02-13 10:08:15 +01:00
|
|
|
|
2012-10-04 21:49:41 +09:00
|
|
|
|
2012-10-04 21:49:42 +09:00
|
|
|
|
2015-12-23 02:06:58 +09:00
|
|
|
|
2024-04-11 11:17:17 -07:00
|
|
|
|
|
|
|
|
|
2025-07-24 09:33:00 -07:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2012-10-04 21:49:41 +09:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
2014-03-17 18:18:54 -03:00
|
|
|
|
2013-10-22 19:01:31 -03:00
|
|
|
|
2013-10-31 15:56:03 +09:00
|
|
|
|
2024-07-31 16:55:00 -07:00
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2019-06-28 17:22:59 +08:00
|
|
|
|
2015-12-23 02:06:58 +09:00
|
|
|
|
2015-12-24 11:16:17 +09:00
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:05 +02:00
|
|
|
|
2019-03-11 07:44:54 -07:00
|
|
|
|
perf sort: Fix the 'weight' sort key behavior
Currently, the 'weight' field in the perf sample has latency information
for some instructions like in memory accesses. And perf tool has 'weight'
and 'local_weight' sort keys to display the info.
But it's somewhat confusing what it shows exactly. In my understanding,
'local_weight' shows a weight in a single sample, and (global) 'weight'
shows a sum of the weights in the hist_entry.
For example:
$ perf mem record -t load dd if=/dev/zero of=/dev/null bs=4k count=1M
$ perf report --stdio -n -s +local_weight
...
#
# Overhead Samples Command Shared Object Symbol Local Weight
# ........ ....... ....... ................ ......................... ............
#
21.23% 313 dd [kernel.vmlinux] [k] lockref_get_not_zero 32
12.43% 183 dd [kernel.vmlinux] [k] lockref_get_not_zero 35
11.97% 159 dd [kernel.vmlinux] [k] lockref_get_not_zero 36
10.40% 141 dd [kernel.vmlinux] [k] lockref_put_return 32
7.63% 113 dd [kernel.vmlinux] [k] lockref_get_not_zero 33
6.37% 92 dd [kernel.vmlinux] [k] lockref_get_not_zero 34
6.15% 90 dd [kernel.vmlinux] [k] lockref_put_return 33
...
So let's look at the 'lockref_get_not_zero' symbols. The top entry
shows that 313 samples were captured with 'local_weight' 32, so the
total weight should be 313 x 32 = 10016. But it's not the case:
$ perf report --stdio -n -s +local_weight,weight -S lockref_get_not_zero
...
#
# Overhead Samples Command Shared Object Local Weight Weight
# ........ ....... ....... ................ ............ ......
#
1.36% 4 dd [kernel.vmlinux] 36 144
0.47% 4 dd [kernel.vmlinux] 37 148
0.42% 4 dd [kernel.vmlinux] 32 128
0.40% 4 dd [kernel.vmlinux] 34 136
0.35% 4 dd [kernel.vmlinux] 36 144
0.34% 4 dd [kernel.vmlinux] 35 140
0.30% 4 dd [kernel.vmlinux] 36 144
0.30% 4 dd [kernel.vmlinux] 34 136
0.30% 4 dd [kernel.vmlinux] 32 128
0.30% 4 dd [kernel.vmlinux] 32 128
...
With the 'weight' sort key, it's divided to 4 samples even with the same
info ('comm', 'dso', 'sym' and 'local_weight'). I don't think this is
what we want.
I found this because of the way it aggregates the 'weight' value. Since
it's not a period, we should not add them in the he->stat. Otherwise,
two 32 'weight' entries will create a 64 'weight' entry.
After that, new 32 'weight' samples don't have a matching entry so it'd
create a new entry and make it a 64 'weight' entry again and again.
Later, they will be merged into 128 'weight' entries during the
hists__collapse_resort() with 4 samples, multiple times like above.
Let's keep the weight and display it differently. For 'local_weight',
it can show the weight as is, and for (global) 'weight' it can display
the number multiplied by the number of samples.
With this change, I can see the expected numbers.
$ perf report --stdio -n -s +local_weight,weight -S lockref_get_not_zero
...
#
# Overhead Samples Command Shared Object Local Weight Weight
# ........ ....... ....... ................ ............ .....
#
21.23% 313 dd [kernel.vmlinux] 32 10016
12.43% 183 dd [kernel.vmlinux] 35 6405
11.97% 159 dd [kernel.vmlinux] 36 5724
7.63% 113 dd [kernel.vmlinux] 33 3729
6.37% 92 dd [kernel.vmlinux] 34 3128
4.17% 59 dd [kernel.vmlinux] 37 2183
0.08% 1 dd [kernel.vmlinux] 269 269
0.08% 1 dd [kernel.vmlinux] 38 38
Reviewed-by: Athira Jajeev <atrajeev@linux.vnet.ibm.com>
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Tested-by: Athira Jajeev <atrajeev@linux.vnet.ibm.com>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: Ian Rogers <irogers@google.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Kan Liang <kan.liang@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Link: https://lore.kernel.org/r/20211105225617.151364-1-namhyung@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2021-11-05 15:56:15 -07:00
|
|
|
|
2021-11-05 15:56:16 -07:00
|
|
|
|
2025-07-24 09:33:00 -07:00
|
|
|
|
perf report: Add 'simd' sort field
Add 'simd' sort field to visualize SIMD ops in 'perf report'.
Rows are labeled with the SIMD ISA, and the type of predicate (if any):
- [p] partial predicate
- [e] empty predicate (no elements in the vector being used)
Example with Arm SPE and SVE (Scalable Vector Extension):
#include <arm_sve.h>
double src[1025], dst[1025];
int main(void) {
svfloat64_t vc = svdup_f64(1);
for(;;)
for(int i = 0; i < 1025; i += svcntd())
{
svbool_t pg = svwhilelt_b64(i, 1025);
svfloat64_t vsrc = svld1(pg, &src[i]);
svfloat64_t vdst = svadd_x(pg, vsrc, vc);
svst1(pg, &dst[i], vdst);
}
return 0;
}
... compiled using "gcc-11 -march=armv8-a+sve -O3"
Profiling on a platform that implements FEAT_SVE and FEAT_SPEv1p1:
$ perf record -e arm_spe_0// -- ./a.out
$ perf report --itrace=i1i -s overhead,pid,simd,sym
Overhead Pid:Command Simd Symbol
........ ................ ....... ......................
53.76% 10758:program [.] main
46.14% 10758:program [.] SVE [.] main
0.09% 10758:program [p] SVE [.] main
The report shows 0.09% of the sampled SVE operations use partial
predicates due to src and dst arrays not being multiples of the vector
register lengths.
Signed-off-by: German Gomez <german.gomez@arm.com>
Acked-by: Ian Rogers <irogers@google.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Anshuman.Khandual@arm.com
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: John Garry <john.g.garry@oracle.com>
Cc: Leo Yan <leo.yan@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Mike Leach <mike.leach@linaro.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Link: https://lore.kernel.org/r/20230320151509.1137462-2-james.clark@arm.com
Signed-off-by: James Clark <james.clark@arm.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2023-03-20 15:15:08 +00:00
|
|
|
|
2018-06-07 14:42:27 -03:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
2018-06-07 14:42:27 -03:00
|
|
|
|
|
|
|
|
|
2019-03-11 07:44:58 -07:00
|
|
|
|
|
|
|
|
|
2018-06-07 14:42:27 -03:00
|
|
|
|
2012-02-09 23:21:01 +01:00
|
|
|
|
|
|
|
|
|
2016-07-05 08:56:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2016-07-05 08:56:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2016-07-05 08:56:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2016-07-05 08:56:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2016-07-05 08:56:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-06-28 17:22:59 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-11-07 15:47:16 +08:00
|
|
|
|
2026-01-22 13:35:14 -08:00
|
|
|
|
2019-11-07 15:47:16 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-06-28 17:22:59 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
2014-10-09 13:13:41 -03:00
|
|
|
|
2015-12-23 02:06:58 +09:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-23 02:06:58 +09:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-23 02:06:58 +09:00
|
|
|
|
|
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2016-06-14 20:19:21 +02:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-07 17:02:25 +09:00
|
|
|
|
|
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2014-10-09 13:13:41 -03:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-09 13:13:41 -03:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-07-18 20:13:14 +08:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-22 13:35:14 -08:00
|
|
|
|
|
|
|
|
|
2023-06-08 16:28:03 -07:00
|
|
|
|
|
|
|
|
|
2019-11-04 15:57:38 -03:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-07 17:02:25 +09:00
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2014-10-09 13:13:41 -03:00
|
|
|
|
2015-12-23 02:06:58 +09:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
2019-11-04 15:57:38 -03:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-23 02:06:58 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2016-06-14 20:19:21 +02:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-06 23:51:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-19 22:59:42 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-06 23:51:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-19 22:59:42 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-06-14 20:19:21 +02:00
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-07 17:02:25 +09:00
|
|
|
|
|
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-09 13:13:41 -03:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
2015-09-25 16:15:47 +03:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
2023-06-08 16:28:21 -07:00
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
2023-06-08 16:28:21 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-08 14:32:02 -03:00
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
|
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2014-10-09 13:13:41 -03:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2016-06-14 20:19:21 +02:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
2014-12-22 13:44:14 +09:00
|
|
|
|
2013-12-26 17:44:10 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-08 16:28:21 -07:00
|
|
|
|
2013-12-26 17:44:10 +09:00
|
|
|
|
2014-10-09 13:13:41 -03:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-08 16:28:21 -07:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-31 13:58:30 +09:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
2020-03-19 13:25:17 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
2015-08-10 15:45:55 -03:00
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-22 13:35:14 -08:00
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-05 16:25:31 +01:00
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
2015-12-24 11:16:17 +09:00
|
|
|
|
|
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
|
|
|
|
|
2023-06-08 16:28:21 -07:00
|
|
|
|
2020-03-19 13:25:17 -07:00
|
|
|
|
2013-12-26 17:44:10 +09:00
|
|
|
|
2023-06-08 16:28:21 -07:00
|
|
|
|
|
|
|
|
|
2013-12-26 17:44:10 +09:00
|
|
|
|
2023-06-08 16:28:21 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-19 13:25:17 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-07 17:02:25 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
2014-01-07 17:02:25 +09:00
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
2016-06-14 20:19:21 +02:00
|
|
|
|
2023-03-15 22:51:05 +08:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
perf hists: Check if a hist_entry has callchains before using them
So far if we use 'perf record -g' this will make
symbol_conf.use_callchain 'true' and logic will assume that all events
have callchains enabled, but ever since we added the possibility of
setting up callchains for some events (e.g.: -e
cycles/call-graph=dwarf/) while not for others, we limit usage scenarios
by looking at that symbol_conf.use_callchain global boolean, we better
look at each event attributes.
On the road to that we need to look if a hist_entry has callchains, that
is, to go from hist_entry->hists to the evsel that contains it, to then
look at evsel->sample_type for PERF_SAMPLE_CALLCHAIN.
The next step is to add a symbol_conf.ignore_callchains global, to use
in the places where what we really want to know is if callchains should
be ignored, even if present.
Then -g will mean just to select a callchain mode to be applied to all
events not explicitely setting some other callchain mode, i.e. a default
callchain mode, and --no-call-graph will set
symbol_conf.ignore_callchains with that clear intention.
That too will at some point become a per evsel thing, that tools can set
for all or just a few of its evsels.
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: David Ahern <dsahern@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>
Link: https://lkml.kernel.org/n/tip-0sas5cm4dsw2obn75g7ruz69@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2018-05-29 13:59:24 -03:00
|
|
|
|
2014-12-22 13:44:14 +09:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:45 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
2013-10-31 10:05:29 +09:00
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-11 14:13:04 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
2014-01-07 17:02:25 +09:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
2017-01-05 22:23:31 -08:00
|
|
|
|
|
|
|
|
|
2018-05-24 11:20:39 -03:00
|
|
|
|
2017-01-05 22:23:31 -08:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
2023-06-08 16:28:21 -07:00
|
|
|
|
2015-05-19 17:04:10 +09:00
|
|
|
|
2019-03-16 16:05:49 +08:00
|
|
|
|
|
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
2019-03-16 16:05:49 +08:00
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-07 17:02:25 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-07 17:02:25 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-05 22:23:31 -08:00
|
|
|
|
|
|
|
|
|
2013-10-30 09:40:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2016-01-18 10:24:24 +01:00
|
|
|
|
2014-03-03 12:07:47 +09:00
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
perf hist: Fix bogus profiles when filters are enabled
When a filtered column is not present in the sort order, profiles become
arbitrary broken. Filtered and non-filtered entries are collapsed
together, and the filtered-by field ends up with a random value (either
from a filtered or non-filtered entry). If we end up with filtered
entry/value, then the whole collapsed entry will be filtered out and will
be missing in the profile. If we end up with non-filtered entry/value,
then the overhead value will be wrongly larger (include some subset
of filtered out samples).
This leads to very confusing profiles. The problem is hard to notice,
and if noticed hard to understand. If the filter is for a single value,
then it can be fixed by adding the corresponding field to the sort order
(provided user understood the problem). But if the filter is for multiple
values, it's impossible to fix b/c there is no concept of binary sorting
based on filter predicate (we want to group all non-filtered values in
one bucket, and all filtered values in another).
Examples of affected commands:
perf report --tid=123
perf report --sort overhead,symbol --comm=foo,bar
Fix this by considering filtered status as the highest priority
sort/collapse predicate.
As a side effect this effectively adds a new feature of showing profile
where several lines are combined based on arbitrary filtering predicate.
For example, showing symbols from binaries foo and bar combined together,
but not from other binaries; or showing combined overhead of several
particular threads.
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Link: https://lore.kernel.org/r/359dc444ce94d20e59d3a9e360c36fbeac833a04.1736927981.git.dvyukov@google.com
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
2025-01-15 09:00:42 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
|
|
|
|
|
2016-02-27 03:52:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
2014-12-19 12:31:40 -03:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2016-07-05 08:56:04 +02:00
|
|
|
|
|
|
|
|
|
2025-03-06 22:12:50 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-02 22:21:35 -03:00
|
|
|
|
2023-10-24 15:23:14 -07:00
|
|
|
|
2015-06-15 23:29:51 -03:00
|
|
|
|
|
|
|
|
|
2024-08-06 23:51:36 -07:00
|
|
|
|
2015-06-15 23:29:51 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-07 11:35:44 -07:00
|
|
|
|
|
|
|
|
|
2018-03-07 16:50:06 +01:00
|
|
|
|
2015-06-15 23:29:51 -03:00
|
|
|
|
|
|
|
|
|
2019-06-28 17:23:01 +08:00
|
|
|
|
2024-05-07 11:35:40 -07:00
|
|
|
|
2019-06-28 17:23:01 +08:00
|
|
|
|
2023-03-20 14:16:18 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-11 07:44:58 -07:00
|
|
|
|
2012-09-11 13:15:07 +09:00
|
|
|
|
2023-06-08 16:28:22 -07:00
|
|
|
|
2015-08-07 15:54:24 -07:00
|
|
|
|
2019-07-04 12:06:20 -03:00
|
|
|
|
2014-12-30 14:38:13 +09:00
|
|
|
|
2019-07-04 12:06:20 -03:00
|
|
|
|
|
|
|
|
|
2025-04-30 13:55:41 -07:00
|
|
|
|
2016-07-05 08:56:04 +02:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
perf hists: Do column alignment on the format iterator
We were doing column alignment in the format function for each cell,
returning a string padded with spaces so that when the next column is
printed the cursor is at its column alignment.
This ends up needlessly printing trailing spaces, do it at the format
iterator, that is where we know if it is needed, i.e. if there is more
columns to be printed.
This eliminates the need for triming lines when doing a dump using 'P'
in the TUI browser and also produces far saner results with things like
piping 'perf report' to 'less'.
Right now only the formatters for sym->name and the 'locked' column
(perf mem report), that are the ones that end up at the end of lines
in the default 'perf report', 'perf top' and 'perf mem report' tools,
the others will be done in a subsequent patch.
In the end the 'width' parameter for the formatters now mean, in
'printf' terms, the 'precision', where before it was the field 'width'.
Reported-by: Dave Jones <davej@codemonkey.org.uk>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Link: http://lkml.kernel.org/n/tip-s7iwl2gj23w92l6tibnrcqzr@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2016-02-11 17:14:13 -03:00
|
|
|
|
|
|
|
|
|
2018-12-03 11:22:00 +01:00
|
|
|
|
perf hists: Do column alignment on the format iterator
We were doing column alignment in the format function for each cell,
returning a string padded with spaces so that when the next column is
printed the cursor is at its column alignment.
This ends up needlessly printing trailing spaces, do it at the format
iterator, that is where we know if it is needed, i.e. if there is more
columns to be printed.
This eliminates the need for triming lines when doing a dump using 'P'
in the TUI browser and also produces far saner results with things like
piping 'perf report' to 'less'.
Right now only the formatters for sym->name and the 'locked' column
(perf mem report), that are the ones that end up at the end of lines
in the default 'perf report', 'perf top' and 'perf mem report' tools,
the others will be done in a subsequent patch.
In the end the 'width' parameter for the formatters now mean, in
'printf' terms, the 'precision', where before it was the field 'width'.
Reported-by: Dave Jones <davej@codemonkey.org.uk>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Link: http://lkml.kernel.org/n/tip-s7iwl2gj23w92l6tibnrcqzr@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2016-02-11 17:14:13 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-06-14 20:19:20 +02:00
|
|
|
|
perf hists: Do column alignment on the format iterator
We were doing column alignment in the format function for each cell,
returning a string padded with spaces so that when the next column is
printed the cursor is at its column alignment.
This ends up needlessly printing trailing spaces, do it at the format
iterator, that is where we know if it is needed, i.e. if there is more
columns to be printed.
This eliminates the need for triming lines when doing a dump using 'P'
in the TUI browser and also produces far saner results with things like
piping 'perf report' to 'less'.
Right now only the formatters for sym->name and the 'locked' column
(perf mem report), that are the ones that end up at the end of lines
in the default 'perf report', 'perf top' and 'perf mem report' tools,
the others will be done in a subsequent patch.
In the end the 'width' parameter for the formatters now mean, in
'printf' terms, the 'precision', where before it was the field 'width'.
Reported-by: Dave Jones <davej@codemonkey.org.uk>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Link: http://lkml.kernel.org/n/tip-s7iwl2gj23w92l6tibnrcqzr@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2016-02-11 17:14:13 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
2016-03-09 22:46:58 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-09 22:46:58 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-08-17 14:55:23 +02:00
|
|
|
|
2016-03-09 22:46:58 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-09 22:46:58 +09:00
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
2016-03-09 22:46:58 +09:00
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
2025-04-30 13:55:41 -07:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
|
|
|
|
|
2016-03-09 22:46:58 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
2025-04-30 13:55:41 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-09 22:46:58 +09:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
perf hists: Check if a hist_entry has callchains before using them
So far if we use 'perf record -g' this will make
symbol_conf.use_callchain 'true' and logic will assume that all events
have callchains enabled, but ever since we added the possibility of
setting up callchains for some events (e.g.: -e
cycles/call-graph=dwarf/) while not for others, we limit usage scenarios
by looking at that symbol_conf.use_callchain global boolean, we better
look at each event attributes.
On the road to that we need to look if a hist_entry has callchains, that
is, to go from hist_entry->hists to the evsel that contains it, to then
look at evsel->sample_type for PERF_SAMPLE_CALLCHAIN.
The next step is to add a symbol_conf.ignore_callchains global, to use
in the places where what we really want to know is if callchains should
be ignored, even if present.
Then -g will mean just to select a callchain mode to be applied to all
events not explicitely setting some other callchain mode, i.e. a default
callchain mode, and --no-call-graph will set
symbol_conf.ignore_callchains with that clear intention.
That too will at some point become a per evsel thing, that tools can set
for all or just a few of its evsels.
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: David Ahern <dsahern@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>
Link: https://lkml.kernel.org/n/tip-0sas5cm4dsw2obn75g7ruz69@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2018-05-29 13:59:24 -03:00
|
|
|
|
|
|
|
|
|
2023-06-08 16:28:21 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-24 13:52:17 +01:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-03-24 13:52:17 +01:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2016-02-25 00:13:34 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-16 23:08:25 +09:00
|
|
|
|
|
|
|
|
|
2012-10-04 21:49:43 +09:00
|
|
|
|
2012-09-11 13:15:07 +09:00
|
|
|
|
|
|
|
|
|
2025-04-30 13:55:41 -07:00
|
|
|
|
2012-09-26 16:47:28 +09:00
|
|
|
|
perf hists: Check if a hist_entry has callchains before using them
So far if we use 'perf record -g' this will make
symbol_conf.use_callchain 'true' and logic will assume that all events
have callchains enabled, but ever since we added the possibility of
setting up callchains for some events (e.g.: -e
cycles/call-graph=dwarf/) while not for others, we limit usage scenarios
by looking at that symbol_conf.use_callchain global boolean, we better
look at each event attributes.
On the road to that we need to look if a hist_entry has callchains, that
is, to go from hist_entry->hists to the evsel that contains it, to then
look at evsel->sample_type for PERF_SAMPLE_CALLCHAIN.
The next step is to add a symbol_conf.ignore_callchains global, to use
in the places where what we really want to know is if callchains should
be ignored, even if present.
Then -g will mean just to select a callchain mode to be applied to all
events not explicitely setting some other callchain mode, i.e. a default
callchain mode, and --no-call-graph will set
symbol_conf.ignore_callchains with that clear intention.
That too will at some point become a per evsel thing, that tools can set
for all or just a few of its evsels.
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: David Ahern <dsahern@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>
Link: https://lkml.kernel.org/n/tip-0sas5cm4dsw2obn75g7ruz69@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2018-05-29 13:59:24 -03:00
|
|
|
|
2023-06-08 16:28:21 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-14 04:51:58 +01:00
|
|
|
|
2014-12-19 12:31:40 -03:00
|
|
|
|
2016-02-16 23:08:25 +09:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2014-12-22 13:44:10 +09:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-16 23:08:25 +09:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2022-08-26 09:42:28 -07:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-26 09:42:28 -07:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-19 13:09:10 -02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-03-16 17:50:51 +09:00
|
|
|
|
2015-09-04 10:45:44 -04:00
|
|
|
|
2025-02-13 10:08:17 +01:00
|
|
|
|
2011-10-19 13:09:10 -02:00
|
|
|
|
|
|
|
|
|
2016-02-16 23:08:25 +09:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
|
|
|
|
|
2016-02-16 23:08:25 +09:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2016-05-03 13:54:42 +02:00
|
|
|
|
2016-02-16 23:08:25 +09:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2014-12-22 13:44:10 +09:00
|
|
|
|
|
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2014-12-22 13:44:10 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
|
|
|
|
|
2013-09-17 16:34:28 -03:00
|
|
|
|
|
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-16 23:08:25 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-19 13:09:10 -02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-11 14:15:38 +09:00
|
|
|
|
|
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2016-02-16 23:08:25 +09:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
|
|
|
|
|
2014-04-24 16:37:26 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2014-04-24 16:37:26 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2014-04-24 16:37:26 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2014-04-24 16:37:26 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
2014-04-24 16:37:26 +09:00
|
|
|
|
|
|
|
|
|
2016-03-09 22:47:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-03-09 22:47:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
|
|
|
|
|
2016-03-09 22:47:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
|
|
|
|
|
2016-03-09 22:47:02 +09:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
|
|
|
|
|
2016-03-09 22:47:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
|
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-27 03:52:47 +09:00
|
|
|
|
|
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
2022-12-15 11:28:14 -08:00
|
|
|
|
|
|
|
|
|
2016-03-07 16:44:46 -03:00
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-08 22:08:33 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
perf hist: Introduce hists class and move lots of methods to it
In cbbc79a we introduced support for multiple events by introducing a
new "event_stat_id" struct and then made several perf_session methods
receive a point to it instead of a pointer to perf_session, and kept the
event_stats and hists rb_tree in perf_session.
While working on the new newt based browser, I realised that it would be
better to introduce a new class, "hists" (short for "histograms"),
renaming the "event_stat_id" struct and the perf_session methods that
were really "hists" methods, as they manipulate only struct hists
members, not touching anything in the other perf_session members.
Other optimizations, such as calculating the maximum lenght of a symbol
name present in an hists instance will be possible as we add them,
avoiding a re-traversal just for finding that information.
The rationale for the name "hists" to replace "event_stat_id" is that we
may have multiple sets of hists for the same event_stat id, as, for
instance, the 'perf diff' tool has, so event stat id is not what
characterizes what this struct and the functions that manipulate it do.
Cc: Eric B Munson <ebmunson@us.ibm.com>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-05-10 13:04:11 -03:00
|
|
|
|
2015-08-11 06:30:48 -04:00
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
2016-02-27 03:52:47 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2016-01-28 00:40:48 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-04-02 09:50:42 -03:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2016-01-28 00:40:48 +09:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-03 14:18:00 +09:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-27 03:52:47 +09:00
|
|
|
|
2022-12-15 11:28:14 -08:00
|
|
|
|
2016-02-27 03:52:47 +09:00
|
|
|
|
2022-12-15 11:28:14 -08:00
|
|
|
|
|
|
|
|
|
2016-02-27 03:52:47 +09:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
2016-01-18 10:23:59 +01:00
|
|
|
|
2019-02-04 15:18:06 +01:00
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
2016-02-16 23:08:19 +09:00
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
2016-02-16 23:08:19 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-09 22:47:02 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:35 +09:00
|
|
|
|
|
|
|
|
|
2016-05-03 13:54:42 +02:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
|
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2019-02-04 15:18:06 +01:00
|
|
|
|
2016-08-01 20:02:34 +02:00
|
|
|
|
|
|
|
|
|
2015-08-11 06:30:48 -04:00
|
|
|
|
2014-04-24 16:21:46 +09:00
|
|
|
|
2014-04-24 16:25:19 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-22 13:44:10 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-28 15:32:55 +02:00
|
|
|
|
2011-10-05 17:50:23 -03:00
|
|
|
|
2009-12-14 11:37:11 -02:00
|
|
|
|
2020-05-06 12:58:55 -03:00
|
|
|
|
|
|
|
|
|
2016-01-18 10:23:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-05-28 16:00:29 -03:00
|
|
|
|
2016-01-18 10:23:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
perf report: Make --branch-history work without callgraphs(-g) option in perf record
perf record -b -g <command>
perf report --branch-history
This merges the LBRs with the callgraphs.
However it would be nice if it also works without callgraphs (-g) set in
perf record, so that only the LBRs are displayed. But currently perf
report errors in this case. For example,
perf record -b <command>
perf report --branch-history
Error:
Selected -g or --branch-history but no callchain data. Did
you call 'perf record' without -g?
This patch displays the LBRs only even if callgraphs(-g) is not enabled
in perf record.
Change log:
v2: According to Milian Wolff's comment, change the obsolete error
message. Now the error message is:
┌─Error:─────────────────────────────────────┐
│Selected -g or --branch-history. │
│But no callchain or branch data. │
│Did you call 'perf record' without -g or -b?│
│ │
│ │
│Press any key... │
└────────────────────────────────────────────┘
When passing the last parameter to hists__fprintf,
changes "|" to "||".
hists__fprintf(hists, !quiet, 0, 0, rep->min_percent, stdout,
symbol_conf.use_callchain || symbol_conf.show_branchflag_count);
Signed-off-by: Yao Jin <yao.jin@linux.intel.com>
Reviewed-by: Andi Kleen <ak@linux.intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Kan Liang <kan.liang@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1494240182-28899-1-git-send-email-yao.jin@linux.intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2017-05-08 18:43:02 +08:00
|
|
|
|
|
|
|
|
|
2019-02-04 15:18:07 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-06 12:58:55 -03:00
|
|
|
|
2019-02-04 15:18:07 +01:00
|
|
|
|
2020-05-06 12:58:55 -03:00
|
|
|
|
2016-01-18 10:24:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-04 15:18:06 +01:00
|
|
|
|
2016-08-01 20:02:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-04 15:18:06 +01:00
|
|
|
|
2016-01-18 10:23:59 +01:00
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:36 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:36 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:36 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-26 21:13:16 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-26 21:13:16 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
2010-07-16 12:35:07 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:38 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-26 21:13:19 +09:00
|
|
|
|
2016-02-25 00:13:38 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-07-16 12:35:07 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-24 16:44:16 +09:00
|
|
|
|
2015-05-05 23:55:46 +09:00
|
|
|
|
2016-02-26 21:13:19 +09:00
|
|
|
|
2010-07-26 17:13:40 -03:00
|
|
|
|
2015-03-11 20:36:03 +08:00
|
|
|
|
2014-04-24 16:37:26 +09:00
|
|
|
|
2013-12-26 15:11:52 +09:00
|
|
|
|
2010-07-16 12:35:07 -03:00
|
|
|
|
2014-04-24 16:37:26 +09:00
|
|
|
|
2011-09-26 12:33:28 -03:00
|
|
|
|
2010-07-16 12:35:07 -03:00
|
|
|
|
|
|
|
|
|
2011-10-19 13:09:10 -02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-04 14:38:01 -07:00
|
|
|
|
2011-10-19 13:09:10 -02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-10-24 15:23:07 -07:00
|
|
|
|
2011-10-19 13:09:10 -02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-03-16 17:50:51 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-04 10:45:44 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-20 10:15:21 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-04 10:45:45 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2015-09-04 10:45:45 -04:00
|
|
|
|
|
|
|
|
|
2016-01-20 10:15:21 +09:00
|
|
|
|
2015-09-04 10:45:45 -04:00
|
|
|
|
|
|
|
|
|
2016-01-20 10:15:21 +09:00
|
|
|
|
2015-09-04 10:45:45 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:38 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:38 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:38 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
2016-03-09 22:47:02 +09:00
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-02-25 00:13:39 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:38 +09:00
|
|
|
|
|
|
|
|
|
2016-01-20 10:15:21 +09:00
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:38 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-20 10:15:21 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:38 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-20 10:15:21 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:38 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-20 10:15:21 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-25 00:13:38 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-20 10:15:21 +09:00
|
|
|
|
|
|
|
|
|
2025-02-13 10:08:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-18 16:24:46 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-26 18:37:13 -07:00
|
|
|
|
2010-05-14 10:36:42 -03:00
|
|
|
|
2021-04-26 18:37:13 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-14 10:36:42 -03:00
|
|
|
|
2012-11-08 17:54:33 -03:00
|
|
|
|
2014-05-28 14:12:18 +09:00
|
|
|
|
|
|
|
|
|
2021-04-26 18:37:13 -07:00
|
|
|
|
2014-05-28 14:12:18 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-09-01 12:57:38 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-20 08:45:03 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
|
|
|
|
|
2013-10-01 07:22:15 -07:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
2016-05-03 13:54:42 +02:00
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
|
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
|
|
|
|
|
2012-09-11 13:34:27 +09:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
2012-11-12 13:20:03 -03:00
|
|
|
|
|
|
|
|
|
2016-04-24 23:28:09 -07:00
|
|
|
|
|
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2014-04-24 16:21:46 +09:00
|
|
|
|
2012-12-01 21:18:20 +01:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-08 17:54:33 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
|
|
|
|
|
2016-05-03 13:54:42 +02:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-11-08 17:54:33 -03:00
|
|
|
|
|
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
|
|
|
|
|
2012-11-08 17:54:33 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-09-13 16:45:46 +09:00
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-09-13 16:45:46 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
2016-09-13 16:45:46 +09:00
|
|
|
|
|
|
|
|
|
2025-01-15 09:00:41 +01:00
|
|
|
|
2016-09-13 16:45:46 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2016-09-13 16:45:46 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-09-13 16:45:46 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-08 17:54:33 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-11-08 17:54:33 -03:00
|
|
|
|
2019-08-28 08:15:55 +09:00
|
|
|
|
2012-11-08 17:54:33 -03:00
|
|
|
|
2016-09-13 16:45:46 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-03 13:54:42 +02:00
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
2012-11-08 17:54:33 -03:00
|
|
|
|
|
|
|
|
|
2019-08-28 08:15:55 +09:00
|
|
|
|
2012-11-29 15:38:34 +09:00
|
|
|
|
2012-11-08 17:54:33 -03:00
|
|
|
|
|
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-13 16:45:47 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-03 13:54:42 +02:00
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2012-12-10 17:29:55 +09:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-29 15:38:34 +09:00
|
|
|
|
2012-11-08 18:03:09 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-14 11:52:48 +09:00
|
|
|
|
2019-08-28 08:15:55 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-07-18 08:24:49 -07:00
|
|
|
|
2019-11-07 15:47:15 +08:00
|
|
|
|
2024-08-13 09:02:03 -07:00
|
|
|
|
2015-07-18 08:24:49 -07:00
|
|
|
|
|
|
|
|
|
2020-02-28 08:30:00 -08:00
|
|
|
|
2015-07-18 08:24:49 -07:00
|
|
|
|
|
|
|
|
|
2020-02-28 08:30:00 -08:00
|
|
|
|
2015-07-18 08:24:49 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-10-24 15:23:08 -07:00
|
|
|
|
2015-07-18 08:24:49 -07:00
|
|
|
|
|
|
|
|
|
2024-08-13 09:02:03 -07:00
|
|
|
|
|
|
|
|
|
2015-07-18 08:24:49 -07:00
|
|
|
|
2019-11-07 15:47:15 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-07-18 08:24:49 -07:00
|
|
|
|
2023-10-24 15:23:08 -07:00
|
|
|
|
2023-10-24 15:23:14 -07:00
|
|
|
|
|
|
|
|
|
2023-10-24 15:23:08 -07:00
|
|
|
|
2015-07-18 08:24:49 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-10 15:49:21 -03:00
|
|
|
|
2024-06-07 13:29:17 -07:00
|
|
|
|
2014-10-10 15:49:21 -03:00
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2014-10-10 15:49:21 -03:00
|
|
|
|
|
|
|
|
|
2016-06-23 11:26:15 -03:00
|
|
|
|
2021-04-26 18:37:13 -07:00
|
|
|
|
2024-08-20 08:45:03 -07:00
|
|
|
|
2021-04-26 18:37:13 -07:00
|
|
|
|
2024-08-20 08:45:03 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-26 18:37:15 -07:00
|
|
|
|
|
|
|
|
|
2020-04-29 16:07:09 -03:00
|
|
|
|
2022-09-01 12:57:39 -07:00
|
|
|
|
2024-08-20 08:45:03 -07:00
|
|
|
|
2022-09-01 12:57:39 -07:00
|
|
|
|
|
|
|
|
|
2024-08-20 08:45:03 -07:00
|
|
|
|
2022-09-01 12:57:39 -07:00
|
|
|
|
2024-08-20 08:45:03 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-10 15:49:21 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-14 11:52:48 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-07 12:06:07 +09:00
|
|
|
|
2025-02-13 10:08:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-27 15:11:49 +09:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
2021-04-26 18:37:13 -07:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2020-04-29 16:07:09 -03:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-30 10:51:16 -03:00
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
2020-04-29 16:09:12 -03:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-26 18:37:13 -07:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-21 13:24:29 +02:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-21 13:24:46 +02:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-08 16:28:00 -07:00
|
|
|
|
|
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-08 16:28:00 -07:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-04 14:38:01 -07:00
|
|
|
|
2018-04-02 14:24:28 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-07 12:06:07 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-24 13:44:10 -03:00
|
|
|
|
2017-03-30 10:54:40 +01:00
|
|
|
|
2014-02-07 12:06:07 +09:00
|
|
|
|
2017-01-24 13:44:10 -03:00
|
|
|
|
2014-02-07 12:06:07 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-14 12:02:15 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-09 16:16:00 -03:00
|
|
|
|
2016-01-18 10:24:22 +01:00
|
|
|
|
2014-10-09 16:16:00 -03:00
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2014-10-09 16:16:00 -03:00
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
2022-08-26 09:42:28 -07:00
|
|
|
|
2015-09-04 10:45:44 -04:00
|
|
|
|
2025-02-13 10:08:17 +01:00
|
|
|
|
2016-01-18 10:24:22 +01:00
|
|
|
|
2016-03-07 16:44:45 -03:00
|
|
|
|
2014-10-09 16:16:00 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
2015-12-10 16:53:20 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-06 11:18:18 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-10 16:53:20 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2015-12-09 11:11:29 +09:00
|
|
|
|
|
|
|
|
|
2016-03-07 16:44:45 -03:00
|
|
|
|
|
|
|
|
|
2015-12-09 11:11:29 +09:00
|
|
|
|
2015-12-10 16:53:20 +09:00
|
|
|
|
2025-04-30 13:55:42 -07:00
|
|
|
|
perf hist: Hide unused mem stat columns
Some mem_stat types don't use all 8 columns. And there are cases only
samples in certain kinds of mem_stat types are available only. For that
case hide columns which has no samples.
The new output for the previous data would be:
$ perf mem report -F overhead,op,comm --stdio
...
# ------ Mem Op -------
# Overhead Load Store Other Command
# ........ ..................... ...............
#
44.85% 21.1% 30.7% 48.3% swapper
26.82% 98.8% 0.3% 0.9% netsli-prober
7.19% 51.7% 13.7% 34.6% perf
5.81% 89.7% 2.2% 8.1% qemu-system-ppc
4.77% 100.0% 0.0% 0.0% notifications_c
1.77% 95.9% 1.2% 3.0% MemoryReleaser
0.77% 71.6% 4.1% 24.3% DefaultEventMan
0.19% 66.7% 22.2% 11.1% gnome-shell
...
On Intel machines, the event is only for loads or stores so it'll have
only one column:
# Mem Op
# Overhead Load Command
# ........ ....... ...............
#
20.55% 100.0% swapper
17.13% 100.0% chrome
9.02% 100.0% data-loop.0
6.26% 100.0% pipewire-pulse
5.63% 100.0% threaded-ml
5.47% 100.0% GraphRunner
5.37% 100.0% AudioIP~allback
5.30% 100.0% Chrome_ChildIOT
3.17% 100.0% Isolated Web Co
...
Committer testing:
# grep "model name" -m1 /proc/cpuinfo
model name : AMD Ryzen 9 9950X3D 16-Core Processo
# perf mem report -F overhead,op,comm --stdio
# Total Lost Samples: 0
#
# Samples: 2K of event 'cycles:P'
# Total weight : 2637
# Sort order : local_weight,mem,sym,dso,symbol_daddr,dso_daddr,snoop,tlb,locked,blocked,local_ins_lat,local_p_stage_cyc
#
# ------ Mem Op -------
# Overhead Load Store Other Command
# ........ ..................... ...............
#
61.02% 14.4% 25.5% 60.1% swapper
5.61% 26.4% 13.5% 60.1% Isolated Web Co
5.50% 21.4% 29.7% 49.0% perf
4.74% 27.2% 15.2% 57.6% gnome-shell
4.63% 33.6% 11.5% 54.9% mdns_service
4.29% 28.3% 12.4% 59.3% ptyxis
2.16% 24.6% 19.3% 56.1% DOM Worker
0.99% 23.1% 34.6% 42.3% firefox
0.72% 26.3% 15.8% 57.9% IPC I/O Parent
0.61% 12.5% 12.5% 75.0% kworker/u130:20
0.61% 37.5% 18.8% 43.8% podman
0.57% 33.3% 6.7% 60.0% Timer
0.53% 14.3% 7.1% 78.6% KMS thread
0.49% 30.8% 7.7% 61.5% kworker/u130:3-
0.46% 41.7% 33.3% 25.0% IPDL Background
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Ian Rogers <irogers@google.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Kan Liang <kan.liang@linux.intel.com>
Cc: Leo Yan <leo.yan@arm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ravi Bangoria <ravi.bangoria@amd.com>
Link: https://lore.kernel.org/r/20250430205548.789750-9-namhyung@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2025-04-30 13:55:45 -07:00
|
|
|
|
2016-03-07 16:44:45 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-04 12:13:46 -03:00
|
|
|
|
2016-03-07 16:44:45 -03:00
|
|
|
|
|
|
|
|
|
2019-07-04 12:13:46 -03:00
|
|
|
|
2016-03-07 16:44:45 -03:00
|
|
|
|
|
|
|
|
|
2015-12-09 11:11:29 +09:00
|
|
|
|
|
|
|
|
|
2019-07-21 13:23:51 +02:00
|
|
|
|
2016-01-07 10:14:10 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-18 10:24:22 +01:00
|
|
|
|
2016-01-07 10:14:10 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-09 16:16:00 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-06 12:55:06 -03:00
|
|
|
|
|
|
|
|
|
2014-10-09 16:16:00 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-18 10:24:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|