Home
last modified time | relevance | path

Searched refs:branches (Results 1 – 25 of 120) sorted by relevance

12345

/linux-6.15/tools/perf/Documentation/
H A Dperf-intel-pt.txt35 or "branches" events had been recorded. Presently 3 tools support this:
183 Another note, in the case of "branches" events, non-taken branches are not
195 branches, and supports 2 additional modes selected by option:
968 b synthesize "branches" events
972 c synthesize branches events (calls only)
973 r synthesize branches events (returns only)
994 TNT packet representing multiple branches) happens causes a packet to
1169 - conditional branches
1174 - asynchronous branches such as interrupts
1175 - indirect branches
[all …]
H A Ditrace.txt3 b synthesize branches events
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,
H A Dtips.txt22 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}' ...
H A Dperf-top.txt248 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.
/linux-6.15/Documentation/admin-guide/hw-vuln/
H A Dindirect-target-selection.rst8 of indirect branches and RETs located in the lower half of a cacheline.
14 - **eIBRS Guest/Host Isolation**: Indirect branches in KVM/kernel may still be
21 branches may still be predicted with targets corresponding to direct branches
57 As only the indirect branches and RETs that have their last byte of instruction
59 the mitigation is to not allow indirect branches in the lower half.
75 Note, for simplicity, indirect branches in eBPF programs are always replaced
82 thunks. But, RETs significantly outnumber indirect branches, and any benefit
88 Retpoline sequence also mitigates ITS-unsafe indirect branches. For this
119 indirect branches.
157 - The mitigation is enabled, affected indirect branches and RETs are
/linux-6.15/tools/perf/tests/shell/
H A Drecord_lbr.sh7 if [ ! -f /sys/devices/cpu/caps/branches ] && [ ! -f /sys/devices/cpu_core/caps/branches ]
H A Dstat+std_output.sh14 …e-faults stalled-cycles-frontend stalled-cycles-backend cycles instructions branches branch-misses)
/linux-6.15/Documentation/staging/
H A Dstatic-keys.rst76 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.15/tools/perf/scripts/python/
H A Dexport-to-sqlite.py121 branches = (columns == "branches") variable
205 if branches:
589 if branches:
706 if branches:
H A Dexport-to-postgresql.py300 branches = (columns == "branches") variable
381 if branches:
1032 if branches:
/linux-6.15/arch/powerpc/net/
H A Dbpf_jit_comp.c541 int run_ctx_off, u32 *branches) in invoke_bpf_mod_ret() argument
569 branches[i] = ctx->idx; in invoke_bpf_mod_ret()
662 u32 *branches = NULL; in __arch_prepare_bpf_trampoline() local
849 branches = kcalloc(fmod_ret->nr_links, sizeof(u32), GFP_KERNEL); in __arch_prepare_bpf_trampoline()
850 if (!branches) in __arch_prepare_bpf_trampoline()
854 run_ctx_off, branches)) { in __arch_prepare_bpf_trampoline()
898 if (create_cond_branch(&branch_insn, &image[branches[i]], in __arch_prepare_bpf_trampoline()
904 image[branches[i]] = ppc_inst_val(branch_insn); in __arch_prepare_bpf_trampoline()
968 kfree(branches); in __arch_prepare_bpf_trampoline()
/linux-6.15/fs/ubifs/
H A Dmisc.h203 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.15/Documentation/process/
H A Dmaintainer-soc.rst176 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
H A D7.AdvancedTopics.rst42 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
H A Dmaintainer-kvm-x86.rst38 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.15/Documentation/features/core/jump-labels/
H A Darch-support.txt4 # description: arch supports live patched, high efficiency branches
/linux-6.15/arch/m68k/ifpsp060/
H A Diskeleton.S60 | _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.15/tools/perf/util/
H A Dparse-events.l259 …instruction|LLC|L2|dTLB|d-tlb|Data-TLB|iTLB|i-tlb|Instruction-TLB|branch|branches|bpu|btb|bpc|node)
344 branch-instructions|branches { return hw_term(yyscanner, PERF_COUNT_HW_BRANCH_INSTRUCTIONS); }
399 branch-instructions|branches { return sym(yyscanner, PERF_TYPE_HARDWARE, PERF_COUNT_HW_BRANCH_INS…
/linux-6.15/Documentation/networking/
H A Dtc-actions-env-rules.rst14 or intentionally branches by redirecting a packet, then you need to
/linux-6.15/arch/mips/include/asm/
H A Dfpu_emulator.h28 unsigned long branches; member
/linux-6.15/arch/x86/events/
H A DKconfig53 16 consecutive taken branches in registers.
/linux-6.15/arch/powerpc/platforms/8xx/
H A DKconfig121 (by not placing conditional branches or branches to LR or CTR
/linux-6.15/arch/mips/math-emu/
H A Dme-debugfs.c57 __this_cpu_write((fpuemustats).branches, 0); in fpuemustats_clear_show()
213 FPU_STAT_CREATE(branches); in debugfs_fpuemu()
/linux-6.15/Documentation/devicetree/bindings/clock/
H A Dlpc1850-ccu.txt3 Each CGU base clock has several clock branches which can be turned on
/linux-6.15/Documentation/maintainer/
H A Dconfigure-git.rst6 Tagged branches used in pull requests (see

12345