File: ISA2%2Bpooncerelease%2Bpoacquirerelease%2Bpoacquireonce.litmus

package info (click to toggle)
linux 5.10.13-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 1,182,916 kB
  • sloc: ansic: 19,488,074; asm: 263,676; sh: 73,873; makefile: 44,685; perl: 34,640; python: 32,386; cpp: 6,070; yacc: 4,755; lex: 2,742; awk: 1,214; ruby: 25; sed: 5
file content (39 lines) | stat: -rw-r--r-- 784 bytes parent folder | download | duplicates (34)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
C ISA2+pooncerelease+poacquirerelease+poacquireonce

(*
 * Result: Never
 *
 * This litmus test demonstrates that a release-acquire chain suffices
 * to order P0()'s initial write against P2()'s final read.  The reason
 * that the release-acquire chain suffices is because in all but one
 * case (P2() to P0()), each process reads from the preceding process's
 * write.  In memory-model-speak, there is only one non-reads-from
 * (AKA non-rf) link, so release-acquire is all that is needed.
 *)

{}

P0(int *x, int *y)
{
	WRITE_ONCE(*x, 1);
	smp_store_release(y, 1);
}

P1(int *y, int *z)
{
	int r0;

	r0 = smp_load_acquire(y);
	smp_store_release(z, 1);
}

P2(int *x, int *z)
{
	int r0;
	int r1;

	r0 = smp_load_acquire(z);
	r1 = READ_ONCE(*x);
}

exists (1:r0=1 /\ 2:r0=1 /\ 2:r1=0)