arch/arm64/include/asm/irq.h
Source file repositories/reference/linux-study-clean/arch/arm64/include/asm/irq.h
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/include/asm/irq.h- Extension
.h- Size
- 571 bytes
- Lines
- 27
- 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/cpumask.hasm-generic/irq.h
Detected Declarations
struct pt_regsfunction nr_legacy_irqs
Annotated Snippet
#ifndef __ASM_IRQ_H
#define __ASM_IRQ_H
#ifndef __ASSEMBLER__
#include <linux/cpumask.h>
#include <asm-generic/irq.h>
void arch_trigger_cpumask_backtrace(const cpumask_t *mask, int exclude_cpu);
#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace
struct pt_regs;
int set_handle_irq(void (*handle_irq)(struct pt_regs *));
#define set_handle_irq set_handle_irq
int set_handle_fiq(void (*handle_fiq)(struct pt_regs *));
static inline int nr_legacy_irqs(void)
{
return 0;
}
#endif /* !__ASSEMBLER__ */
#endif
Annotation
- Immediate include surface: `linux/cpumask.h`, `asm-generic/irq.h`.
- Detected declarations: `struct pt_regs`, `function nr_legacy_irqs`.
- 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.