| /linux-6.12.1/tools/perf/Documentation/ ! |
| D | perf-intel-pt.txt | 35 or "branches" events had been recorded. Presently 3 tools support this:
98 To represent software control flow, "branches" samples are produced. By default
163 Note IPC for "branches" events is calculated separately from IPC for "instructions"
183 Another note, in the case of "branches" events, non-taken branches are not
195 branches, and supports 2 additional modes selected by option:
914 b synthesize "branches" events
918 c synthesize branches events (calls only)
919 r synthesize branches events (returns only)
940 TNT packet representing multiple branches) happens causes a packet to
946 "Branches" events look like they were recorded by "perf record -e branches". "c"
[all …]
|
| D | itrace.txt | 3 b synthesize branches events (branch misses for Arm SPE)
4 c synthesize branches events (calls only)
5 r synthesize branches events (returns only)
52 It is also possible to skip events generated (instructions, branches, transactions,
|
| D | tips.txt | 22 Treat branches as callchains: perf record -b ... ; perf report --branch-history
37 To only collect call graph on one event use perf record -e cpu/cpu-cycles,callgraph=1/,branches ; p…
38 …f individual events use perf record -e cpu/cpu-cycles,period=100001/,cpu/branches,period=10001/ ...
39 …ents which need to be collected together for accuracy use {}: perf record -e {cycles,branches}' ...
|
| D | perf-top.txt | 248 taken branches. The number of branches captured with each sample depends on the
249 underlying hardware, the type of branches of interest, and the executed code.
250 It is possible to select the types of branches captured by enabling filters.
262 Add the addresses of sampled taken branches to the callstack.
|
| D | intel-hybrid.txt | 186 cpu_core/branches/,
187 cpu_atom/branches/,
|
| /linux-6.12.1/Documentation/staging/ ! |
| D | static-keys.rst | 76 Using the 'asm goto', we can create branches that are either taken or not taken
157 Note that switching branches results in some locks being taken,
303 208,368,926 branches # 243.507 M/sec ( +- 0.06% )
304 5,569,188 branch-misses # 2.67% of all branches ( +- 0.54% )
320 206,859,359 branches # 245.956 M/sec ( +- 0.04% )
321 4,884,119 branch-misses # 2.36% of all branches ( +- 0.85% )
325 The percentage of saved branches is .7%, and we've saved 12% on
327 this optimization is about reducing the number of branches. In addition, we've
|
| /linux-6.12.1/tools/perf/tests/shell/ ! |
| D | record_lbr.sh | 7 if [ ! -f /sys/devices/cpu/caps/branches ] && [ ! -f /sys/devices/cpu_core/caps/branches ]
|
| D | stat+std_output.sh | 14 …e-faults stalled-cycles-frontend stalled-cycles-backend cycles instructions branches branch-misses)
|
| /linux-6.12.1/tools/perf/scripts/python/ ! |
| D | export-to-sqlite.py | 121 branches = (columns == "branches") variable
205 if branches:
589 if branches:
706 if branches:
|
| D | export-to-postgresql.py | 300 branches = (columns == "branches") variable
381 if branches:
1032 if branches:
|
| /linux-6.12.1/fs/ubifs/ ! |
| D | misc.h | 203 return (struct ubifs_branch *)((void *)idx->branches + in ubifs_idx_branch()
215 return (void *)((struct ubifs_branch *)idx->branches)->key; in ubifs_idx_key()
|
| /linux-6.12.1/Documentation/process/ ! |
| D | maintainer-soc.rst | 176 Just as the main SoC tree has several branches, it is expected that
178 all be split into separate branches and appear in separate pull requests to the
180 regressions that originate from dependencies on other branches.
186 top-level branches, e.g. for a treewide rework, or the addition of new SoC
190 topics branches, even if they end up getting merged into the same branch of the
200 small branches as time gets closer to the merge window.
203 again having multiple smaller branches is better than trying to combine too many
|
| D | 7.AdvancedTopics.rst | 42 the tree, use branches, etc. An understanding of git's tools for the
45 remote branches, the index, fast-forward merges, pushes and pulls, detached
60 The normal git workflow involves the use of a lot of branches. Each line
65 Publicly-available branches should be created with care; merge in patches
66 from development branches when they are in complete form and ready to go -
97 of the reasons why development should be done in private branches (which
98 can be rewritten if necessary) and only moved into public branches when
|
| D | maintainer-kvm-x86.rst | 38 The KVM x86 tree is organized into multiple topic branches. The purpose of
39 using finer-grained topic branches is to make it easier to keep tabs on an area
45 All topic branches, except for ``next`` and ``fixes``, are rolled into ``next``
57 following rc7 for "normal" releases. If all goes well, the topic branches are
95 dependencies across topic branches, it is the maintainer's job to sort them
166 Note, these don't align with the topics branches (the topic branches care much
340 solution is to derive the names of your development branches based on their
381 patch's SHA1 changes. However, in some scenarios, e.g. if all KVM x86 branches
|
| /linux-6.12.1/Documentation/features/core/jump-labels/ ! |
| D | arch-support.txt | 4 # description: arch supports live patched, high efficiency branches
|
| /linux-6.12.1/arch/m68k/ifpsp060/ ! |
| D | iskeleton.S | 60 | _isp_unimp() branches to here so that the operating system
88 | stack frame and branches to this routine.
123 | Integer Instruction stack frame and branches to this routine.
128 | stack frame and branches to the _real_trace() entry point.
|
| /linux-6.12.1/tools/perf/util/ ! |
| D | parse-events.l | 256 …instruction|LLC|L2|dTLB|d-tlb|Data-TLB|iTLB|i-tlb|Instruction-TLB|branch|branches|bpu|btb|bpc|node)
340 branch-instructions|branches { return hw_term(yyscanner, PERF_COUNT_HW_BRANCH_INSTRUCTIONS); }
393 branch-instructions|branches { return sym(yyscanner, PERF_TYPE_HARDWARE, PERF_COUNT_HW_BRANCH_INS…
|
| /linux-6.12.1/Documentation/networking/ ! |
| D | tc-actions-env-rules.rst | 14 or intentionally branches by redirecting a packet, then you need to
|
| /linux-6.12.1/arch/mips/include/asm/ ! |
| D | fpu_emulator.h | 28 unsigned long branches; member
|
| /linux-6.12.1/arch/x86/events/ ! |
| D | Kconfig | 53 16 consecutive taken branches in registers.
|
| /linux-6.12.1/arch/powerpc/platforms/8xx/ ! |
| D | Kconfig | 121 (by not placing conditional branches or branches to LR or CTR
|
| /linux-6.12.1/arch/mips/math-emu/ ! |
| D | me-debugfs.c | 57 __this_cpu_write((fpuemustats).branches, 0); in fpuemustats_clear_show()
213 FPU_STAT_CREATE(branches); in debugfs_fpuemu()
|
| /linux-6.12.1/Documentation/maintainer/ ! |
| D | rebasing-and-merging.rst | 100 which may contain multiple topic branches; each branch is usually developed
104 Many projects require that branches in pull requests be based on the
106 is not such a project; any rebasing of branches to avoid merges will, most
128 branches. Failure to do so threatens the security of the development
|
| D | configure-git.rst | 6 Tagged branches used in pull requests (see
|
| /linux-6.12.1/Documentation/devicetree/bindings/clock/ ! |
| D | lpc1850-ccu.txt | 3 Each CGU base clock has several clock branches which can be turned on
|