arch/um/include/asm/irq.h

File Facts

System

Linux kernel

Corpus path

arch/um/include/asm/irq.h

Extension

.h

Size

854 bytes

Lines

41

Domain

Architecture Layer

Bucket

arch/um

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.

Dependency Surface

• asm-generic/irq.h

Detected Declarations

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

Annotated Snippet

#ifndef __UM_IRQ_H
#define __UM_IRQ_H

#define TIMER_IRQ		0
#define UMN_IRQ			1
#define UBD_IRQ			2
#define UM_ETH_IRQ		3
#define ACCEPT_IRQ		4
#define MCONSOLE_IRQ		5
#define WINCH_IRQ		6
#define SIGIO_WRITE_IRQ 	7
#define TELNETD_IRQ 		8
#define XTERM_IRQ 		9
#define RANDOM_IRQ 		10
#define SIGCHLD_IRQ		11

#ifdef CONFIG_UML_NET_VECTOR

#define VECTOR_BASE_IRQ		(SIGCHLD_IRQ + 1)
#define VECTOR_IRQ_SPACE	8

#define UM_FIRST_DYN_IRQ (VECTOR_IRQ_SPACE + VECTOR_BASE_IRQ)

#else

#define UM_FIRST_DYN_IRQ (SIGCHLD_IRQ + 1)

#endif

#define UM_LAST_SIGNAL_IRQ	64
/* If we have (simulated) PCI MSI, allow 64 more interrupt numbers for it */
#ifdef CONFIG_PCI_MSI
#define NR_IRQS			(UM_LAST_SIGNAL_IRQ + 64)
#else
#define NR_IRQS			UM_LAST_SIGNAL_IRQ
#endif /* CONFIG_PCI_MSI */

#include <asm-generic/irq.h>
#endif

Annotation

• Immediate include surface: `asm-generic/irq.h`.
• Atlas domain: Architecture Layer / arch/um.
• Implementation status: source implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.