arch/arc/include/asm/atomic.h

File Facts

System

Linux kernel

Corpus path

arch/arc/include/asm/atomic.h

Extension

.h

Size

660 bytes

Lines

37

Domain

Architecture Layer

Bucket

arch/arc

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.

Dependency Surface

• linux/types.h
• linux/compiler.h
• asm/cmpxchg.h
• asm/barrier.h
• asm/smp.h
• asm/atomic-llsc.h
• asm/atomic-spinlock.h
• asm-generic/atomic64.h
• asm/atomic64-arcv2.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _ASM_ARC_ATOMIC_H
#define _ASM_ARC_ATOMIC_H

#ifndef __ASSEMBLER__

#include <linux/types.h>
#include <linux/compiler.h>
#include <asm/cmpxchg.h>
#include <asm/barrier.h>
#include <asm/smp.h>

#define arch_atomic_read(v)  READ_ONCE((v)->counter)

#ifdef CONFIG_ARC_HAS_LLSC
#include <asm/atomic-llsc.h>
#else
#include <asm/atomic-spinlock.h>
#endif

/*
 * 64-bit atomics
 */
#ifdef CONFIG_GENERIC_ATOMIC64
#include <asm-generic/atomic64.h>
#else
#include <asm/atomic64-arcv2.h>
#endif

#endif	/* !__ASSEMBLER__ */

#endif

Annotation

• Immediate include surface: `linux/types.h`, `linux/compiler.h`, `asm/cmpxchg.h`, `asm/barrier.h`, `asm/smp.h`, `asm/atomic-llsc.h`, `asm/atomic-spinlock.h`, `asm-generic/atomic64.h`.
• Atlas domain: Architecture Layer / arch/arc.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.