arch/x86/kernel/irq_work.c
Source file repositories/reference/linux-study-clean/arch/x86/kernel/irq_work.c
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/kernel/irq_work.c- Extension
.c- Size
- 688 bytes
- Lines
- 35
- Domain
- Architecture Layer
- Bucket
- arch/x86
- 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
linux/kernel.hlinux/irq_work.hlinux/hardirq.hasm/apic.hasm/idtentry.hasm/trace/irq_vectors.hlinux/interrupt.h
Detected Declarations
function Copyrightfunction arch_irq_work_raise
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* x86 specific code for irq_work
*
* Copyright (C) 2010 Red Hat, Inc., Peter Zijlstra
*/
#include <linux/kernel.h>
#include <linux/irq_work.h>
#include <linux/hardirq.h>
#include <asm/apic.h>
#include <asm/idtentry.h>
#include <asm/trace/irq_vectors.h>
#include <linux/interrupt.h>
#ifdef CONFIG_X86_LOCAL_APIC
DEFINE_IDTENTRY_SYSVEC(sysvec_irq_work)
{
apic_eoi();
trace_irq_work_entry(IRQ_WORK_VECTOR);
inc_irq_stat(IRQ_WORK);
irq_work_run();
trace_irq_work_exit(IRQ_WORK_VECTOR);
}
void arch_irq_work_raise(void)
{
if (!arch_irq_work_has_interrupt())
return;
__apic_send_IPI_self(IRQ_WORK_VECTOR);
apic_wait_icr_idle();
}
#endif
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/irq_work.h`, `linux/hardirq.h`, `asm/apic.h`, `asm/idtentry.h`, `asm/trace/irq_vectors.h`, `linux/interrupt.h`.
- Detected declarations: `function Copyright`, `function arch_irq_work_raise`.
- Atlas domain: Architecture Layer / arch/x86.
- 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.