arch/um/include/asm/irqflags.h
Source file repositories/reference/linux-study-clean/arch/um/include/asm/irqflags.h
File Facts
- System
- Linux kernel
- Corpus path
arch/um/include/asm/irqflags.h- Extension
.h- Size
- 806 bytes
- Lines
- 39
- 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.
Dependency Surface
asm-generic/irqflags.h
Detected Declarations
function arch_local_save_flagsfunction arch_local_irq_restorefunction arch_local_irq_enablefunction arch_local_irq_disable
Annotated Snippet
#ifndef __UM_IRQFLAGS_H
#define __UM_IRQFLAGS_H
int um_get_signals(void);
int um_set_signals(int enable);
void block_signals(void);
void unblock_signals(void);
#define arch_local_save_flags arch_local_save_flags
static inline unsigned long arch_local_save_flags(void)
{
return um_get_signals();
}
#define arch_local_irq_restore arch_local_irq_restore
static inline void arch_local_irq_restore(unsigned long flags)
{
um_set_signals(flags);
}
#define arch_local_irq_enable arch_local_irq_enable
static inline void arch_local_irq_enable(void)
{
unblock_signals();
}
#define arch_local_irq_disable arch_local_irq_disable
static inline void arch_local_irq_disable(void)
{
block_signals();
}
#define ARCH_IRQ_DISABLED 0
#include <asm-generic/irqflags.h>
#endif
Annotation
- Immediate include surface: `asm-generic/irqflags.h`.
- Detected declarations: `function arch_local_save_flags`, `function arch_local_irq_restore`, `function arch_local_irq_enable`, `function arch_local_irq_disable`.
- Atlas domain: Architecture Layer / arch/um.
- 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.