arch/arm64/include/asm/system_misc.h

File Facts

System

Linux kernel

Corpus path

arch/arm64/include/asm/system_misc.h

Extension

.h

Size

733 bytes

Lines

34

Domain

Architecture Layer

Bucket

arch/arm64

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/compiler.h
• linux/linkage.h
• linux/irqflags.h
• linux/signal.h
• linux/ratelimit.h
• linux/reboot.h

Detected Declarations

• struct pt_regs
• struct siginfo
• struct mm_struct

Annotated Snippet

#ifndef __ASM_SYSTEM_MISC_H
#define __ASM_SYSTEM_MISC_H

#ifndef __ASSEMBLER__

#include <linux/compiler.h>
#include <linux/linkage.h>
#include <linux/irqflags.h>
#include <linux/signal.h>
#include <linux/ratelimit.h>
#include <linux/reboot.h>

struct pt_regs;

void die(const char *msg, struct pt_regs *regs, long err);

struct siginfo;
void arm64_notify_die(const char *str, struct pt_regs *regs,
		      int signo, int sicode, unsigned long far,
		      unsigned long err);

struct mm_struct;
extern void __show_regs(struct pt_regs *);

#endif	/* __ASSEMBLER__ */

#endif	/* __ASM_SYSTEM_MISC_H */

Annotation

• Immediate include surface: `linux/compiler.h`, `linux/linkage.h`, `linux/irqflags.h`, `linux/signal.h`, `linux/ratelimit.h`, `linux/reboot.h`.
• Detected declarations: `struct pt_regs`, `struct siginfo`, `struct mm_struct`.
• Atlas domain: Architecture Layer / arch/arm64.
• Implementation status: source implementation candidate.

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.