/kernel/linux/linux-5.10/tools/perf/ |
D | builtin-annotate.c | 337 int (*annotate)(struct hist_entry *he, in hists__find_annotations() local 341 annotate = dlsym(perf_gtk_handle, in hists__find_annotations() 343 if (annotate == NULL) { in hists__find_annotations() 348 ret = annotate(he, evsel, NULL); in hists__find_annotations() 472 struct perf_annotate annotate = { in cmd_annotate() local 498 OPT_STRING('s', "symbol", &annotate.sym_hist_filter, "symbol", in cmd_annotate() 506 OPT_BOOLEAN(0, "gtk", &annotate.use_gtk, "Use the GTK interface"), in cmd_annotate() 507 OPT_BOOLEAN(0, "tui", &annotate.use_tui, "Use the TUI interface"), in cmd_annotate() 508 OPT_BOOLEAN(0, "stdio", &annotate.use_stdio, "Use the stdio interface"), in cmd_annotate() 509 OPT_BOOLEAN(0, "stdio2", &annotate.use_stdio2, "Use the stdio interface"), in cmd_annotate() [all …]
|
D | command-list.txt | 5 perf-annotate mainporcelain common
|
D | Build | 2 perf-y += builtin-annotate.o
|
/kernel/linux/linux-5.10/scripts/dtc/ |
D | dtx_diff | 22 --annotate synonym for -T 32 -T annotate output .dts with input source file and line 176 annotate="" 219 -T | --annotate ) 220 if [ "${annotate}" = "" ] ; then 221 annotate="-T" 222 elif [ "${annotate}" = "-T" ] ; then 223 annotate="-T -T" 346 -O dts -qq -f ${dtc_sort} ${annotate} -o -"
|
D | treesource.c | 206 if (annotate) { in write_propval() 207 srcstr = srcpos_string_first(prop->srcpos, annotate); in write_propval() 271 if (annotate) { in write_propval() 272 srcstr = srcpos_string_first(prop->srcpos, annotate); in write_propval() 296 if (annotate) { in write_tree_source_node() 297 srcstr = srcpos_string_first(tree->srcpos, annotate); in write_tree_source_node() 318 if (annotate) { in write_tree_source_node() 319 srcstr = srcpos_string_last(tree->srcpos, annotate); in write_tree_source_node()
|
D | dtc.c | 23 int annotate; /* Level of annotation: 1 for input source location variable 257 annotate++; in main() 297 if (annotate && (!streq(inform, "dts") || !streq(outform, "dts"))) in main()
|
D | dtc.h | 46 extern int annotate; /* annotate .dts with input source location */
|
/kernel/linux/linux-5.10/tools/perf/Documentation/ |
D | perfconfig.example | 15 annotate = on 23 [annotate]
|
D | perf-config.txt | 90 annotate = on 97 [annotate] 131 You can hide source code of annotate feature setting the config to false with 133 % perf config annotate.hide_src_code=true 169 'report', 'top' and 'annotate' in the TUI. They should specify the 197 from sub-commands (top, report, annotate). 204 This selects colors for addresses from 'annotate'. 217 Subcommands that can be configured here are 'top', 'report' and 'annotate'. 241 annotate.*:: 245 annotate.disassembler_style: [all …]
|
D | perf-annotate.txt | 1 perf-annotate(1) 6 perf-annotate - Read perf.data (created by perf record) and display annotated code 11 'perf annotate' [-i <file> | --input=file] [symbol_name] 32 Symbol to annotate.
|
D | tips.txt | 29 See assembly instructions with percentage: perf annotate <symbol> 30 If you prefer Intel style assembly, try: perf annotate -M intel
|
D | examples.txt | 189 Or you can annotate the recorded 'git gc' run on a per symbol basis 192 titan:~/git> perf annotate __GI___fork
|
D | perf-report.txt | 300 --tui:: Use the TUI interface, that is integrated with annotate and allows 566 linkperf:perf-stat[1], linkperf:perf-annotate[1], linkperf:perf-record[1],
|
D | perf-top.txt | 103 --sym-annotate=<symbol>::
|
/kernel/linux/linux-5.10/tools/perf/ui/browsers/ |
D | Build | 1 perf-y += annotate.o
|
/kernel/linux/linux-5.10/tools/perf/ui/gtk/ |
D | Build | 9 gtk-y += annotate.o
|
/kernel/linux/linux-5.10/Documentation/kbuild/ |
D | Kconfig.recursion-issue-02 | 12 # annotate those requirements, ie, some drivers use "depends on" while others 15 # annotate this, all features that driver A selects cannot now be negated by
|
/kernel/linux/linux-5.10/Documentation/ |
D | asm-annotations.rst | 28 *non-standard* calling convention. In contrast, ``ENDPROC`` should annotate 75 1. ``SYM_FUNC_*`` -- to annotate C-like functions. This means functions with 83 to these rules. The tools can also easily annotate these functions with
|
/kernel/linux/linux-5.10/Documentation/gpu/ |
D | introduction.rst | 66 start with a /** kerneldoc marker. Similar for data structures, annotate
|
/kernel/linux/linux-5.10/tools/perf/util/ |
D | Build | 1 perf-y += annotate.o
|
/kernel/linux/linux-5.10/Documentation/trace/ |
D | tracepoint-analysis.rst | 313 $ perf annotate pixmanFillsse2
|
/kernel/linux/linux-5.10/tools/objtool/Documentation/ |
D | stack-validation.txt | 252 kernel entry code), change ENDPROC to END and annotate manually with
|
/kernel/linux/linux-5.10/Documentation/driver-api/mtd/ |
D | nand_ecc.rst | 15 I decided to annotate my steps in this file. Perhaps it is useful to someone
|
/kernel/linux/linux-5.10/Documentation/locking/ |
D | lockdep-design.rst | 237 Two constructs can be used to annotate and check where and if certain locks
|
/kernel/linux/linux-5.10/Documentation/networking/ |
D | timestamping.rst | 649 to the driver, for it to annotate it with a timestamp, if that is immediately
|