tools/memory-model/litmus-tests/ISA2+pooncerelease+poacquirerelease+poacquireonce.litmus

File Facts

System

Linux kernel

Corpus path

tools/memory-model/litmus-tests/ISA2+pooncerelease+poacquirerelease+poacquireonce.litmus

Extension

.litmus

Size

784 bytes

Lines

40

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: tools

Status

atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• function P0

Annotated Snippet

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)

Annotation

• Detected declarations: `function P0`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: atlas-only.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.