arch/microblaze/kernel/irq.c
Source file repositories/reference/linux-study-clean/arch/microblaze/kernel/irq.c
File Facts
- System
- Linux kernel
- Corpus path
arch/microblaze/kernel/irq.c- Extension
.c- Size
- 937 bytes
- Lines
- 40
- Domain
- Architecture Layer
- Bucket
- arch/microblaze
- 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/init.hlinux/ftrace.hlinux/kernel.hlinux/hardirq.hlinux/interrupt.hlinux/irqflags.hlinux/seq_file.hlinux/kernel_stat.hlinux/irq.hlinux/irqchip.hlinux/of_irq.h
Detected Declarations
function Copyrightfunction init_IRQ
Annotated Snippet
#include <linux/init.h>
#include <linux/ftrace.h>
#include <linux/kernel.h>
#include <linux/hardirq.h>
#include <linux/interrupt.h>
#include <linux/irqflags.h>
#include <linux/seq_file.h>
#include <linux/kernel_stat.h>
#include <linux/irq.h>
#include <linux/irqchip.h>
#include <linux/of_irq.h>
void __irq_entry do_IRQ(struct pt_regs *regs)
{
struct pt_regs *old_regs = set_irq_regs(regs);
trace_hardirqs_off();
irq_enter();
handle_arch_irq(regs);
irq_exit();
set_irq_regs(old_regs);
trace_hardirqs_on();
}
void __init init_IRQ(void)
{
/* process the entire interrupt tree in one go */
irqchip_init();
}
Annotation
- Immediate include surface: `linux/init.h`, `linux/ftrace.h`, `linux/kernel.h`, `linux/hardirq.h`, `linux/interrupt.h`, `linux/irqflags.h`, `linux/seq_file.h`, `linux/kernel_stat.h`.
- Detected declarations: `function Copyright`, `function init_IRQ`.
- Atlas domain: Architecture Layer / arch/microblaze.
- 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.