kernel/irq/kexec.c

File Facts

System

Linux kernel

Corpus path

kernel/irq/kexec.c

Extension

.c

Size

870 bytes

Lines

37

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/interrupt.h
• linux/irq.h
• linux/irqdesc.h
• linux/irqnr.h
• internals.h

Detected Declarations

• function machine_kexec_mask_interrupts
• function for_each_irq_desc

Annotated Snippet

if (IS_ENABLED(CONFIG_GENERIC_IRQ_KEXEC_CLEAR_VM_FORWARD)) {
			/*
			 * First try to remove the active state from an interrupt which is forwarded
			 * to a VM. If the interrupt is not forwarded, try to EOI the interrupt.
			 */
			check_eoi = irq_set_irqchip_state(i, IRQCHIP_STATE_ACTIVE, false);
		}

		if (check_eoi && chip->irq_eoi && irqd_irq_inprogress(&desc->irq_data))
			chip->irq_eoi(&desc->irq_data);

		irq_shutdown(desc);
	}
}

Annotation

• Immediate include surface: `linux/interrupt.h`, `linux/irq.h`, `linux/irqdesc.h`, `linux/irqnr.h`, `internals.h`.
• Detected declarations: `function machine_kexec_mask_interrupts`, `function for_each_irq_desc`.
• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• 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.