Searched full:implies (Results 1 – 25 of 742) sorted by relevance
12345678910>>...30
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/skylake/ |
| D | virtual-memory.json | 8 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
39 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
49 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
59 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
69 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
89 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
120 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
130 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
140 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
150 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | virtual-memory.json | 8 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
39 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
49 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
59 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
69 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
89 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
120 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
130 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
140 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
150 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | virtual-memory.json | 8 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
39 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
49 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
59 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
69 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
89 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
120 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
130 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
140 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
150 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| D | virtual-memory.json | 34 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
46 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
58 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
70 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
119 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
131 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
143 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
155 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
204 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
216 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | virtual-memory.json | 34 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
46 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
58 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
70 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
119 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
131 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
143 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
155 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
204 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
216 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/icelake/ |
| D | virtual-memory.json | 34 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
46 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
58 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
107 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
119 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
131 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
180 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
192 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
204 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
|
| /Linux-v6.1/arch/xtensa/include/asm/ |
| D | asm-uaccess.h | 31 * <error>. This implies that the macro falls through to the next
42 * <error> label to branch to on error; implies fall-through
61 * <error>. This implies that the macro falls through to the next
72 * <error> label to branch to on error; implies fall-through
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | virtual-memory.json | 17 …page walk or instruction (I) page walk is in progress. Since a pagewalk implies a TLB miss, the a…
36 …ts when a data (D) page walk is completed or started. Since a page walk implies a TLB miss, the n…
55 …an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, the n…
65 …an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, the n…
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | virtual-memory.json | 32 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
43 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
54 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
99 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
166 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
177 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
188 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
|
| /Linux-v6.1/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-v6.1/arch/mips/include/asm/ |
| D | bitops.h | 139 * clear_bit() is atomic and implies release semantics before the memory
175 * This operation is atomic and implies acquire ordering semantics
205 * It also implies a memory barrier.
220 * It also implies a memory barrier.
257 * It also implies a memory barrier.
292 * __clear_bit() is non-atomic and implies release semantics before the memory
|
| /Linux-v6.1/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-v6.1/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,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,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,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 | 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 | 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
|
| /Linux-v6.1/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-v6.1/drivers/net/ethernet/intel/ice/ |
| D | ice_virtchnl_fdir.c | 476 * @tun: 0 implies non-tunnel type filter, 1 implies tunnel type filter
549 * @tun: 0 implies non-tunnel type filter, 1 implies tunnel type filter
664 * @tun: 0 implies non-tunnel type filter, 1 implies tunnel type filter
1187 * @add: true implies add rule, false implies del rules
1188 * @is_tun: false implies non-tunnel type filter, true implies tunnel filter
1449 * @success: true implies success, false implies failure
1513 * @success: true implies success, false implies failure
|
| /Linux-v6.1/Documentation/userspace-api/media/rc/ |
| D | lirc-get-features.rst | 59 :ref:`LIRC_MODE_MODE2 <lirc-mode-MODE2>` is used. This also implies
151 :ref:`LIRC_MODE_PULSE <lirc-mode-pulse>`. This implies that
|
12345678910>>...30
