arch/m68k/virt/ints.c

File Facts

System

Linux kernel

Corpus path

arch/m68k/virt/ints.c

Extension

.c

Size

3698 bytes

Lines

155

Domain

Architecture Layer

Bucket

arch/m68k

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/delay.h
• linux/interrupt.h
• linux/irq.h
• linux/kernel.h
• linux/sched.h
• linux/sched/debug.h
• linux/types.h
• linux/ioport.h
• asm/hwtest.h
• asm/irq.h
• asm/irq_regs.h
• asm/processor.h
• asm/virt.h

Detected Declarations

• function gfpic_read
• function gfpic_write
• function virt_irq_enable
• function virt_irq_disable
• function virt_irq_startup
• function virt_nmi_handler
• function goldfish_pic_irq
• function virt_init_IRQ

Annotated Snippet

if (request_resource(&iomem_resource, &picres[i])) {
			pr_err("Cannot allocate %s resource\n", picname[i]);
			return;
		}

		irq_set_chained_handler(virt_bi_data.pic.irq + i,
					goldfish_pic_irq);
	}

	if (request_irq(IRQ_AUTO_7, virt_nmi_handler, 0, "NMI",
			virt_nmi_handler))
		pr_err("Couldn't register NMI\n");
}

Annotation

• Immediate include surface: `linux/delay.h`, `linux/interrupt.h`, `linux/irq.h`, `linux/kernel.h`, `linux/sched.h`, `linux/sched/debug.h`, `linux/types.h`, `linux/ioport.h`.
• Detected declarations: `function gfpic_read`, `function gfpic_write`, `function virt_irq_enable`, `function virt_irq_disable`, `function virt_irq_startup`, `function virt_nmi_handler`, `function goldfish_pic_irq`, `function virt_init_IRQ`.
• Atlas domain: Architecture Layer / arch/m68k.
• 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.