| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | itrace.txt | 2 b synthesize branches events (branch misses for Arm SPE)
3 c synthesize branches events (calls only)
4 r synthesize branches events (returns only)
45 It is also possible to skip events generated (instructions, branches, transactions,
|
| 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
157 the average IPC since the last IPC for that event type. Note IPC for "branches"
166 Another note, in the case of "branches" events, non-taken branches are not
858 b synthesize "branches" events
862 c synthesize branches events (calls only)
863 r synthesize branches events (returns only)
876 "Branches" events look like they were recorded by "perf record -e branches". "c"
883 Note that "instructions", "branches" and "transactions" events depend on code
1009 It is also possible to skip events generated (instructions, branches, transactions)
[all …]
|
| D | perf-top.txt | 240 taken branches. The number of branches captured with each sample depends on the
241 underlying hardware, the type of branches of interest, and the executed code.
242 It is possible to select the types of branches captured by enabling filters.
|
| D | security.txt | 203 19,628,798 branches # 0.539 M/sec
204 1,259,201 branch-misses # 6.42% of all branches
|
| /kernel/linux/linux-5.10/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,
306 208,368,926 branches # 243.507 M/sec ( +- 0.06% )
307 5,569,188 branch-misses # 2.67% of all branches ( +- 0.54% )
323 206,859,359 branches # 245.956 M/sec ( +- 0.04% )
324 4,884,119 branch-misses # 2.36% of all branches ( +- 0.85% )
328 The percentage of saved branches is .7%, and we've saved 12% on
330 this optimization is about reducing the number of branches. In addition, we've
|
| /kernel/linux/linux-5.10/tools/perf/scripts/python/ |
| D | export-to-sqlite.py | 121 branches = (columns == "branches") variable
205 if branches:
586 if branches:
703 if branches:
|
| D | export-to-postgresql.py | 300 branches = (columns == "branches") variable
381 if branches:
1029 if branches:
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/features/core/jump-labels/ |
| D | arch-support.txt | 4 # description: arch supports live patched, high efficiency branches
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | tc-actions-env-rules.rst | 14 or intentionally branches by redirecting a packet, then you need to
|
| /kernel/linux/linux-5.10/arch/x86/net/ |
| D | bpf_jit_comp.c | 1663 u8 **branches) in invoke_bpf_mod_ret() argument
1689 branches[i] = prog; in invoke_bpf_mod_ret()
1784 u8 **branches = NULL; in arch_prepare_bpf_trampoline() local
1830 branches = kcalloc(fmod_ret->nr_progs, sizeof(u8 *), in arch_prepare_bpf_trampoline()
1832 if (!branches) in arch_prepare_bpf_trampoline()
1836 branches)) { in arch_prepare_bpf_trampoline()
1868 emit_cond_near_jump(&branches[i], prog, branches[i], in arch_prepare_bpf_trampoline()
1912 kfree(branches); in arch_prepare_bpf_trampoline()
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | page_owner.rst | 34 memory overhead. And, page owner inserts just two unlikely branches into
36 like as the kernel without page owner. These two unlikely branches should
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | fpu_emulator.h | 28 unsigned long branches; member
|
| /kernel/uniproton/cmake/tool_chain/ |
| D | uniproton_tool_chain.cmake | 17 …arger-than=4096 -Wduplicated-cond -Wdisabled-optimization -Wduplicated-branches -Wignored-qualifi…
|
| /kernel/linux/linux-5.10/arch/c6x/kernel/ |
| D | vectors.S | 10 ; branches to the label _c_int00 which handles initialization for the C code.
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/8xx/ |
| D | Kconfig | 120 (by not placing conditional branches or branches to LR or CTR
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/tools/perf/util/ |
| D | parse-events.l | 334 branch-instructions|branches { return sym(yyscanner, PERF_TYPE_HARDWARE, PERF_COUNT_HW_BRANCH_INS…
369 branch|branches|bpu|btb|bpc |
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/ |
| D | lpc1850-ccu.txt | 3 Each CGU base clock has several clock branches which can be turned on
|
| /kernel/linux/linux-5.10/Documentation/maintainer/ |
| D | configure-git.rst | 8 Tagged branches used in :ref:`Documentation/maintainer/pull-requests.rst
|
| 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
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 61 conditional branches, while Spectre variant 2 attacks use speculative
62 execution of indirect branches to leak privileged memory.
93 execution of indirect branches :ref:`[3] <spec_ref3>`. The indirect
95 indirect branches can be influenced by an attacker, causing gadget code
103 branches in the victim to gadget code by poisoning the branch target
218 indirect branches. Return trampolines trap speculative execution paths
290 for indirect branches to bypass the poisoned branch target buffer,
505 can be compiled with return trampolines for indirect branches.
|
| /kernel/linux/linux-5.10/Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 11 'libnvdimm-fixes' or 'libnvdimm-for-next' branch. Those branches are
|