arch/sh/kernel/unwinder.c

File Facts

System

Linux kernel

Corpus path

arch/sh/kernel/unwinder.c

Extension

.c

Size

4331 bytes

Lines

166

Domain

Architecture Layer

Bucket

arch/sh

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• 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/errno.h
• linux/list.h
• linux/spinlock.h
• linux/module.h
• asm/unwinder.h
• linux/atomic.h

Detected Declarations

• function unwinder_enqueue
• function list_for_each
• function unwinder_register
• function unwind_stack
• export unwind_stack

Annotated Snippet

if (unwinder_faulted && !list_is_singular(&unwinder_list)) {
			list_del(&curr_unwinder->list);
			curr_unwinder = select_unwinder();

			unwinder_faulted = 0;
		}

		spin_unlock_irqrestore(&unwinder_lock, flags);
	}

	curr_unwinder->dump(task, regs, sp, ops, data);
}
EXPORT_SYMBOL_GPL(unwind_stack);

Annotation

• Immediate include surface: `linux/errno.h`, `linux/list.h`, `linux/spinlock.h`, `linux/module.h`, `asm/unwinder.h`, `linux/atomic.h`.
• Detected declarations: `function unwinder_enqueue`, `function list_for_each`, `function unwinder_register`, `function unwind_stack`, `export unwind_stack`.
• Atlas domain: Architecture Layer / arch/sh.
• Implementation status: integration 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.