Home
last modified time | relevance | path

Searched refs:P0 (Results 1 – 25 of 66) sorted by relevance

123

/Linux-v5.15/tools/memory-model/litmus-tests/
DISA2+pooncerelease+poacquirerelease+poacquireonce.litmus7 * to order P0()'s initial write against P2()'s final read. The reason
9 * case (P2() to P0()), each process reads from the preceding process's
16 P0(int *x, int *y)
DZ6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus9 * P0's write, which means that there are two non-rf links: P1() to P2()
11 * to P0() is a read-to-write link (AKA a "from-reads" or just "fr" link).
19 P0(int *x, int *y)
DS+poonceonces.litmus6 * Starting with a two-process release-acquire chain ordering P0()'s
14 P0(int *x, int *y)
DISA2+pooncelock+pooncelock+pombonce.litmus7 * (in P0() and P1()) is visible to external process P2().
12 P0(int *x, int *y, spinlock_t *mylock)
DREADME184 P0(int *x, int *y)
208 P0()'s WRITE_ONCE() is read by its first READ_ONCE(), which is a
209 reads-from link (rf) and internal to the P0() process. This is
215 P0()'s second access is a READ_ONCE(), as opposed to (for example)
218 P0()'s third access is also a READ_ONCE(), but to y rather than x.
219 This is related to P0()'s second access by program order ("po"),
221 The resulting descriptor is "PodRR". Because P0()'s third access is
224 A from-read ("fre") relation links P0()'s third to P1()'s first
229 The remainder of P1() is similar to P0(), which means we add
231 P0()'s first access, which is WRITE_ONCE(), so we add "Fre Once".
DCoWW+poonceonce.litmus12 P0(int *x)
DCoRR+poonceonce+Once.litmus12 P0(int *x)
DS+fencewmbonceonce+poacquireonce.litmus12 P0(int *x, int *y)
DLB+poonceonces.litmus12 P0(int *x, int *y)
DMP+poonceonces.litmus12 P0(int *buf, int *flag) // Producer
DCoRW+poonceonce+Once.litmus12 P0(int *x)
DCoWR+poonceonce+Once.litmus12 P0(int *x)
DMP+pooncerelease+poacquireonce.litmus13 P0(int *buf, int *flag) // Producer
DR+poonceonces.litmus13 P0(int *x, int *y)
DLB+poacquireonce+pooncerelease.litmus13 P0(int *x, int *y)
DSB+poonceonces.litmus13 P0(int *x, int *y)
DSB+rfionceonce-poonceonces.litmus11 P0(int *x, int *y)
DMP+fencewmbonceonce+fencermbonceonce.litmus13 P0(int *buf, int *flag) // Producer
/Linux-v5.15/drivers/ata/
Data_piix.c105 P0 = 0, /* port 0 */ enumerator
343 { P0, NA, P1, NA }, /* 000b */
344 { P1, NA, P0, NA }, /* 001b */
347 { P0, P1, IDE, IDE }, /* 100b */
348 { P1, P0, IDE, IDE }, /* 101b */
349 { IDE, IDE, P0, P1 }, /* 110b */
350 { IDE, IDE, P1, P0 }, /* 111b */
359 { P0, P2, P1, P3 }, /* 00b */
361 { P0, P2, IDE, IDE }, /* 10b */
376 { P0, P2, NA, NA }, /* 00b */
[all …]
/Linux-v5.15/arch/hexagon/kernel/
Dvm_entry.S284 P0 = tstbit(R0, #HVM_VMEST_UM_SFT); define
285 if (!P0.new) jump:nt restore_all;
307 P0 = cmp.eq(R0, #0); if (!P0.new) jump:nt check_work_pending; define
368 P0 = cmp.eq(R24, #0); define
372 if (P0) jump check_work_pending
/Linux-v5.15/arch/arm/boot/dts/
Daspeed-bmc-amd-ethanolx.dts125 /*P0-P7*/ "P0_VDD_CORE_RUN_VRHOT","P0_VDD_SOC_RUN_VRHOT",
144 //APML for P0
164 //P0 Power regulators
174 //P0/P1 Thermal diode
/Linux-v5.15/tools/memory-model/Documentation/
Dexplanation.txt115 P0()
131 Here the P0() function represents the interrupt handler running on one
134 Thus, P0 stores the data in buf and then sets flag. Meanwhile, P1
162 instance, P1 might run entirely before P0 begins, in which case r1 and
163 r2 will both be 0 at the end. Or P0 might run entirely before P1
167 routines run concurrently. One possibility is that P1 runs after P0's
196 Since r1 = 1, P0 must store 1 to flag before P1 loads 1 from
202 P1 must load 0 from buf before P0 stores 1 to it; otherwise r2
206 P0 stores 1 to buf before storing 1 to flag, since it executes
209 Since an instruction (in this case, P0's store to flag) cannot
[all …]
Dlitmus-tests.txt72 5 P0(int *x, int *y)
114 The name of the first process is "P0" and that of the second "P1".
123 names are significant. The fact that both P0() and P1() have a formal
125 same global variable, also named "x". So the "int *x, int *y" on P0()
128 by reference, hence "P0(int *x, int *y)", but *never* "P0(int x, int y)".
130 P0() has no local variables, but P1() has two of them named "r0" and "r1".
145 The P0() process does "WRITE_ONCE(*x, 1)" on line 7. Because "x" is a
146 pointer in P0()'s parameter list, this does an unordered store to global
148 is also in P0()'s parameter list, this does a release store to global
156 reference the same global variables that are used by P0().
[all …]
/Linux-v5.15/Documentation/litmus-tests/atomic/
DAtomic-RMW-ops-are-atomic-WRT-atomic_set.litmus14 P0(atomic_t *v)
DAtomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus14 P0(int *x, atomic_t *y)

123