Lines Matching refs:P0
72 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().
262 8 P0(int *x, int *y)
316 below, P0() is one side checking to see if an operation may proceed and
323 5 P0(int *x, int *y)
390 5 P0(int *x, int *y)
443 5 P0(int *x, int *y)
517 6 P0(int *sl, int *x0, int *x1)
549 that process sets "sl" back to "0". P0()'s lock acquisition is emulated
628 7 P0(int *sl, int *x0, int *x1)
694 8 P0(int *x, int **y)
725 P0()'s line 10 initializes "x" to the value 1 then line 11 links to "x"
783 12 P0(int *x, int **y) // F
828 9 P0(int *x, int *z, int **y)
861 P0() on lines 9-18 enters an RCU read-side critical section, loads the