Home
last modified time | relevance | path

Searched full:implies (Results 1 – 25 of 698) sorted by relevance

12345678910>>...28

/Linux-v5.15/tools/perf/pmu-events/arch/x86/skylakex/
Dvirtual-memory.json8 … 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-v5.15/tools/perf/pmu-events/arch/x86/cascadelakex/
Dvirtual-memory.json8 … 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-v5.15/tools/perf/pmu-events/arch/x86/skylake/
Dvirtual-memory.json8 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
18 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
38 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
120 …s page walks of any page size (4K/2M/4M/1G) caused by a code fetch. This implies it missed in the …
140 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
150 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
160 …Counts completed page walks (1G page sizes) caused by a code fetch. This implies it missed in the …
170 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
180 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
199 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
[all …]
/Linux-v5.15/arch/xtensa/include/asm/
Dasm-uaccess.h72 * <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-v5.15/tools/perf/pmu-events/arch/x86/icelake/
Dvirtual-memory.json21 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
58 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
70 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
82 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
107 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
131 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
143 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
155 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
179 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
/Linux-v5.15/tools/perf/pmu-events/arch/x86/icelakex/
Dvirtual-memory.json9 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
21 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
33 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
82 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
94 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
106 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
155 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
167 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
179 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
/Linux-v5.15/tools/perf/pmu-events/arch/x86/silvermont/
Dvirtual-memory.json13 …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-v5.15/tools/perf/pmu-events/arch/x86/tigerlake/
Dvirtual-memory.json32 …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-v5.15/arch/x86/include/asm/
Dsync_bitops.h81 * It also implies a memory barrier.
94 * It also implies a memory barrier.
107 * It also implies a memory barrier.
/Linux-v5.15/arch/mips/include/asm/
Dbitops.h141 * 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-v5.15/arch/arm/common/
Dmcpm_head.S101 bl vlock_trylock @ implies DMB
116 @ Control dependency implies strb not observable before previous ldrb.
163 bl vlock_unlock @ implies DMB
Dvlock.S59 @ Control dependency implies strb not observable before previous ldrb.
63 voting_end r0, r1, r2 @ implies DMB
/Linux-v5.15/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-vt8500.txt26 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.
Dlantiq,pinctrl-falcon.txt23 parameters implies no information about any pin configuration parameters.
24 Similarly, a pin subnode that describes a pullup parameter implies no
Dqcom,msm8660-pinctrl.txt37 parameters implies no information about any pin configuration parameters.
38 Similarly, a pin subnode that describes a pullup parameter implies no
Dqcom,apq8064-pinctrl.txt37 parameters implies no information about any pin configuration parameters.
38 Similarly, a pin subnode that describes a pullup parameter implies no
Dqcom,ipq4019-pinctrl.txt40 parameters implies no information about any pin configuration parameters.
41 Similarly, a pin subnode that describes a pullup parameter implies no
Dqcom,ipq8064-pinctrl.txt37 parameters implies no information about any pin configuration parameters.
38 Similarly, a pin subnode that describes a pullup parameter implies no
Dbrcm,bcm2835-gpio.txt42 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.
Dpinctrl-palmas.txt27 parameters implies no information about any pin configuration parameters.
28 Similarly, a pin subnode that describes a pullup parameter implies no
Dqcom,msm8974-pinctrl.txt37 parameters implies no information about any pin configuration parameters.
38 Similarly, a pin subnode that describes a pullup parameter implies no
Dqcom,mdm9615-pinctrl.txt72 parameters implies no information about any pin configuration parameters.
73 Similarly, a pin subnode that describes a pullup parameter implies no
/Linux-v5.15/Documentation/devicetree/bindings/powerpc/fsl/
Dpmc.txt8 whose PMC is compatible, and implies deep-sleep capability.
12 whose PMC is compatible, and implies deep-sleep capability.
/Linux-v5.15/include/linux/sched/
Dmm.h152 * PF_MEMALLOC_NOIO implies GFP_NOIO
153 * PF_MEMALLOC_NOFS implies GFP_NOFS
154 * PF_MEMALLOC_PIN implies !GFP_MOVABLE
162 * NOIO implies both NOIO and NOFS and it is a weaker context in current_gfp_context()
/Linux-v5.15/Documentation/userspace-api/media/rc/
Dlirc-get-features.rst59 :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