Searched full:branch (Results 1 – 25 of 107) sorted by relevance
12345
| /Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 6 Spectre is a class of side channel attacks that exploit branch prediction
18 use branch prediction and speculative execution.
46 CVE-2017-5715 Branch target injection Spectre variant 2
55 buffers, and branch predictors. Malicious software may be able to
70 of speculative execution that bypasses conditional branch instructions
89 Spectre variant 2 (Branch Target Injection)
92 The branch target injection attack takes advantage of speculative
94 branch predictors inside the processor used to guess the target of
103 branches in the victim to gadget code by poisoning the branch target
104 buffer of a CPU used for predicting indirect branch addresses. Such
[all …]
|
| D | indirect-target-selection.rst | 15 predicted with unintended target corresponding to a branch in the guest.
20 - **Indirect Branch Prediction Barrier (IBPB)**: After an IBPB, indirect
63 added ITS-safe thunks. These safe thunks consists of indirect branch in the
66 indirect branch.
72 improve the branch prediction accuracy. Also, it is a defense-in-depth measure
116 on (default) Deploy the "Aligned branch/return thunks" mitigation.
156 * - Mitigation: Aligned branch/return thunks
|
| /Documentation/staging/ |
| D | static-keys.rst | 48 The static_branch_unlikely() branch will be generated into the code with as little
56 Currently, tracepoints are implemented using a conditional branch. The
78 the branch site to change the branch direction.
80 For example, if we have a simple branch that is disabled by default::
83 printk("I am the true branch\n");
87 straight-line code path. When the branch is 'flipped', we will patch the
89 out-of-line true branch. Thus, changing branch direction is expensive but
90 branch selection is basically 'free'. That is the basic tradeoff of this
130 Branch(es) can be set true via::
138 The branch(es) can then be switched via reference counts::
[all …]
|
| D | speculation.rst | 11 employ speculative execution techniques such as branch prediction, performing
20 For example, in the presence of branch prediction, it is possible for bounds
42 It is possible that a CPU mis-predicts the conditional branch, and
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 57 expose an unstable branch for others to test with or for automated
58 testing services. If you do expose a branch that may be unstable in
61 - Do not rebase a branch that contains history created by others. If you
100 which may contain multiple topic branches; each branch is usually developed
102 required before any given branch finds its way into an upstream repository.
132 history into your tree, you cannot rebase that branch, even if you
139 trees tend to be a red flag when it comes time to push a branch upstream.
143 It is natural to want to merge the master branch into a repository; this
150 branch. They will significantly increase your chances of encountering bugs
155 a well-managed branch.
[all …]
|
| D | messy-diffstat.rst | 35 When a subsystem maintainer creates a branch and commits changes to it, the
43 the mainline branch (let's call it "linus") and cN, there are still two
54 Our maintainer has created one branch at vN-rc1 and another at vN-rc2; the
70 branch or performing another merge with the linus branch, then recreating
76 situation is to indeed to do a merge with the branch you intend your work
78 shame. Create a new, throwaway branch and do the merge there::
88 the differences from the mainline branch. Now it will be possible to
93 Save the output from this command, then simply delete the TEMP branch;
|
| D | pull-requests.rst | 19 Create Branch
23 the pull request on a separate branch. Typically you will base this branch
24 off of a branch in the developers tree whom you intend to send the pull
27 In order to create the pull request you must first tag the branch that you
35 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch
41 last commit in the ``char-misc-next`` branch, and sign it with your gpg key
145 branch (which in my case points to the last location in Linus's
|
| D | modifying-patches.rst | 6 If you are a subsystem or branch maintainer, sometimes you need to slightly
23 This practice is particularly helpful if you maintain a stable branch and
|
| /Documentation/devicetree/bindings/clock/ |
| D | lpc1850-ccu.txt | 5 branch clocks are distributed between CCU1 and CCU2.
20 are the branch clock names defined in table below.
35 Which branch clocks that are available on the CCU depends on the
71 /* A user of CCU branch clocks */
|
| D | qcom,gpucc-sdm660.yaml | 27 - description: GPLL0 main gpu branch
28 - description: GPLL0 divider gpu branch
|
| D | qcom,qcm2290-gpucc.yaml | 30 - description: GPLL0 main branch source
31 - description: GPLL0 div branch source
|
| D | qcom,sm6375-gpucc.yaml | 26 - description: GPLL0 main branch source
27 - description: GPLL0 div branch source
|
| D | qcom,sm8450-gpucc.yaml | 36 - description: GPLL0 main branch source
37 - description: GPLL0 div branch source
|
| D | qcom,gpucc.yaml | 44 - description: GPLL0 main branch source
45 - description: GPLL0 div branch source
|
| /Documentation/process/ |
| D | maintainer-soc.rst | 28 tree as a dedicated branch covering multiple subsystems.
107 Driver Branch Dependencies
114 Usually the branch that includes a driver change will also include the
116 in fact compatible. This means that the devicetree branch can end up causing
134 * Change the bindings in a shared immutable branch that is used as the base for
179 SoC maintainers. Each branch should be usable by itself and avoid
190 topics branches, even if they end up getting merged into the same branch of the
191 SoC tree. An example here would be one branch for devicetree warning fixes, one
207 a signed tag, rather than a branch. This tag should contain a short description
|
| D | 7.AdvancedTopics.rst | 61 of development can be separated into a separate "topic branch" and
64 development in any branch which you intend to ask others to pull from.
75 shifted from one branch to another. And so on. Judicious use of git's
103 edge. For a private branch, rebasing can be an easy way to keep up with
110 perform test merges in a private branch. The git "rerere" tool can be
131 branch stick closely to the associated topic; a "driver fixes" branch
144 your tree is, what branch to pull, and what changes will result from the
|
| D | backporting.rst | 48 to your older stable branch.
55 it to the older branch.
99 For backports, what likely happened was that the branch you are
100 backporting from contains patches not in the branch you are backporting
139 Most conflicts happen because the branch you are backporting to is
140 missing some patches compared to the branch you are backporting *from*.
142 development could have happened on either branch, or the branches have
143 simply diverged -- perhaps your older branch had some other backports
161 between your currently checked-out branch (``HEAD``) and the parent of
234 being changed does not even exist in your current branch then this would
[all …]
|
| D | maintainer-kvm-x86.rst | 30 through the KVM x86 tree, it will be applied to the ``fixes`` branch before
41 commits, e.g. dropping the HEAD commit of a topic branch has no impact on other
43 delays only that topic branch.
46 via a Cthulhu merge on an as-needed basis, i.e. when a topic branch is updated.
55 requests (from KVM x86 to main KVM) are sent for each KVM x86 topic branch,
85 Base Tree/Branch
94 select a specific topic branch as the base. If there are conflicts and/or
337 Note, ``--base=auto`` works as expected if and only if a branch's upstream is
338 set to the base topic branch, e.g. it will do the wrong thing if your upstream
342 and then write a small wrapper to extract ``pmu`` from the current branch name
[all …]
|
| D | maintainer-tip.rst | 38 sched/core branch - with occasional sub-topic trees for
45 tree, in the locking/core branch - with occasional sub-topic trees
50 - interrupt core development happens in the irq/core branch
53 branch, but the patches are usually applied in a separate maintainer
59 happens in the timers/core branch, but patches are usually applied in
63 branch, but patches are mostly applied in a separate maintainer tree
69 perf/core branch
79 branch.
84 aggregated in the tip efi/core branch.
89 are aggregated into the tip core/rcu branch.
[all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-maintainer-entry-profile.rst | 10 Patches are generally merged to the for-next branch of the appropriate
12 After a testing period, the for-next branch is merged to the master
13 branch.
79 integration branch, tests the result locally, pushes the branch to a
109 the latest -rc or the for-next branch.
110 These patches will be merged back to the for-next branch.
|
| /Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 11 'libnvdimm-fixes' or 'libnvdimm-for-next' branch. Those branches are
17 patch should be based on the libnvdimm-for-next branch. However, since
50 stabilized in the libnvdimm-for-next branch by -rc6. Of course if a
|
| /Documentation/gpu/ |
| D | automated_testing.rst | 43 URL to git repository containing the target branch
46 Branch to which this branch is to be merged into
148 jobs from a branch in the target tree that is named as
151 If the pipeline is not in a merge request and a branch with the same name
152 exists in the local tree, commits from that branch will be merged in as well.
|
| /Documentation/arch/powerpc/ |
| D | dexcr.rst | 13 branch target prediction) and enabling return-oriented programming (ROP)
61 - Speculative Branch Hint Enable (SBHE)
65 - Indirect Branch Recurrent Target Prediction Disable (IBRTPD)
114 will set the IBRTPD aspect bit in the DEXCR, causing indirect branch prediction
|
| /Documentation/filesystems/ |
| D | ext3.rst | 8 for the 2.2 branch, and ported to 2.4 kernels by Peter Braam, Andreas Dilger,
|
| /Documentation/translations/zh_TW/process/ |
| D | submitting-patches.rst | 594 $ git checkout -t -b my-topical-branch master
595 Branch 'my-topical-branch' set up to track local branch 'master'.
596 Switched to a new branch 'my-topical-branch'
610 Switched to a new branch 'patch-review'
|
12345