Searched full:implies (Results 1 – 25 of 678) sorted by relevance
12345678910>>...28
| /linux-5.10/arch/xtensa/include/asm/ |
| D | asm-uaccess.h | 72 * <success>. This implies that the macro falls through to the next
81 * <success> label to branch to on success; implies
101 * <error>. This implies that the macro falls through to the next
112 * <error> label to branch to on error; implies fall-through
131 * <error>. This implies that the macro falls through to the next
142 * <error> label to branch to on error; implies fall-through
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | virtual-memory.json | 13 …ts when a data (D) page walk is completed or started. Since a page walk implies a TLB miss, the n…
32 …an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, the n…
51 …an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, the n…
61 …page walk or instruction (I) page walk is in progress. Since a pagewalk implies a TLB miss, the a…
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | virtual-memory.json | 17 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
47 …"Counts completed page walks (4K page size) caused by a code fetch. This implies it missed in the …
129 …s page walks of any page size (4K/2M/4M/1G) caused by a code fetch. This implies it missed in the …
149 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
159 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
189 …completed page walks (2M and 4M page sizes) caused by a code fetch. This implies it missed in the …
219 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | virtual-memory.json | 28 …completed page walks (2M and 4M page sizes) caused by a code fetch. This implies it missed in the …
38 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
79 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
160 …s page walks of any page size (4K/2M/4M/1G) caused by a code fetch. This implies it missed in the …
180 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
200 …"Counts completed page walks (4K page size) caused by a code fetch. This implies it missed in the …
249 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/skylake/ |
| D | virtual-memory.json | 3 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
43 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
84 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
124 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
175 …s page walks of any page size (4K/2M/4M/1G) caused by a code fetch. This implies it missed in the …
185 …"Counts completed page walks (4K page size) caused by a code fetch. This implies it missed in the …
215 …completed page walks (2M and 4M page sizes) caused by a code fetch. This implies it missed in the …
|
| /linux-5.10/tools/testing/selftests/android/ion/ |
| D | ipcsocket.h | 20 * name: implies a unique socket name in the system
21 * connecttype: implies server(0) or client(1)
|
| /linux-5.10/arch/x86/include/asm/ |
| D | sync_bitops.h | 81 * It also implies a memory barrier.
94 * It also implies a memory barrier.
107 * It also implies a memory barrier.
|
| /linux-5.10/arch/mips/include/asm/ |
| D | bitops.h | 141 * clear_bit() is atomic and implies release semantics before the memory
177 * This operation is atomic and implies acquire ordering semantics
207 * It also implies a memory barrier.
222 * It also implies a memory barrier.
259 * It also implies a memory barrier.
294 * __clear_bit() is non-atomic and implies release semantics before the memory
|
| /linux-5.10/arch/arm/common/ |
| D | mcpm_head.S | 101 bl vlock_trylock @ implies DMB
116 @ Control dependency implies strb not observable before previous ldrb.
163 bl vlock_unlock @ implies DMB
|
| D | vlock.S | 59 @ Control dependency implies strb not observable before previous ldrb.
63 voting_end r0, r1, r2 @ implies DMB
|
| /linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-vt8500.txt | 26 listed. In other words, a subnode that lists only a mux function implies no
28 a pull parameter implies no information about the mux function.
|
| D | lantiq,pinctrl-falcon.txt | 23 parameters implies no information about any pin configuration parameters.
24 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | qcom,ipq4019-pinctrl.txt | 40 parameters implies no information about any pin configuration parameters.
41 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | qcom,msm8660-pinctrl.txt | 37 parameters implies no information about any pin configuration parameters.
38 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | qcom,apq8064-pinctrl.txt | 37 parameters implies no information about any pin configuration parameters.
38 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | qcom,ipq8064-pinctrl.txt | 37 parameters implies no information about any pin configuration parameters.
38 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | brcm,bcm2835-gpio.txt | 42 listed. In other words, a subnode that lists only a mux function implies no
44 a pul parameter implies no information about the mux function.
|
| D | pinctrl-palmas.txt | 27 parameters implies no information about any pin configuration parameters.
28 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | qcom,msm8974-pinctrl.txt | 37 parameters implies no information about any pin configuration parameters.
38 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | qcom,mdm9615-pinctrl.txt | 72 parameters implies no information about any pin configuration parameters.
73 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | qcom,pmic-mpp.txt | 70 parameters implies no information about any pin configuration parameters.
71 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | qcom,msm8976-pinctrl.txt | 72 parameters implies no information about any pin configuration parameters.
73 Similarly, a pin subnode that describes a pullup parameter implies no
|
| /linux-5.10/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 8 whose PMC is compatible, and implies deep-sleep capability.
12 whose PMC is compatible, and implies deep-sleep capability.
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/icelake/ |
| D | virtual-memory.json | 26 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
93 …s that caused a completed page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
138 …"Counts completed page walks (4K page size) caused by a code fetch. This implies it missed in the …
160 …completed page walks (2M and 4M page sizes) caused by a code fetch. This implies it missed in the …
|
| /linux-5.10/Documentation/userspace-api/media/rc/ |
| D | lirc-get-features.rst | 59 :ref:`LIRC_MODE_MODE2 <lirc-mode-MODE2>` is used. This also implies
169 :ref:`LIRC_MODE_PULSE <lirc-mode-pulse>`. This implies that
|
12345678910>>...28