arch/mips/kernel/crash.c

File Facts

System

Linux kernel

Corpus path

arch/mips/kernel/crash.c

Extension

.c

Size

2432 bytes

Lines

104

Domain

Architecture Layer

Bucket

arch/mips

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/smp.h
• linux/reboot.h
• linux/kexec.h
• linux/memblock.h
• linux/crash_dump.h
• linux/delay.h
• linux/irq.h
• linux/types.h
• linux/sched.h
• linux/sched/task_stack.h

Detected Declarations

• function crash_shutdown_secondary
• function crash_kexec_prepare_cpus
• function crash_smp_send_stop
• function crash_kexec_prepare_cpus

Annotated Snippet

static void crash_kexec_prepare_cpus(void) {}
#endif /* !defined(CONFIG_SMP)	*/

void default_machine_crash_shutdown(struct pt_regs *regs)
{
	local_irq_disable();
	crashing_cpu = smp_processor_id();
	crash_save_cpu(regs, crashing_cpu);
	crash_kexec_prepare_cpus();
	cpumask_set_cpu(crashing_cpu, &cpus_in_crash);
}

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/smp.h`, `linux/reboot.h`, `linux/kexec.h`, `linux/memblock.h`, `linux/crash_dump.h`, `linux/delay.h`, `linux/irq.h`.
• Detected declarations: `function crash_shutdown_secondary`, `function crash_kexec_prepare_cpus`, `function crash_smp_send_stop`, `function crash_kexec_prepare_cpus`.
• Atlas domain: Architecture Layer / arch/mips.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.