arch/xtensa/include/asm/stacktrace.h

File Facts

System

Linux kernel

Corpus path

arch/xtensa/include/asm/stacktrace.h

Extension

.h

Size

1135 bytes

Lines

45

Domain

Architecture Layer

Bucket

arch/xtensa

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

Dependency Surface

• linux/sched.h

Detected Declarations

• struct stackframe

Annotated Snippet

struct stackframe {
	unsigned long pc;
	unsigned long sp;
};

static __always_inline unsigned long *stack_pointer(struct task_struct *task)
{
	unsigned long sp;

	if (!task || task == current)
		sp = current_stack_pointer;
	else
		sp = task->thread.sp;

	return (unsigned long *)sp;
}

void walk_stackframe(unsigned long *sp,
		int (*fn)(struct stackframe *frame, void *data),
		void *data);

void xtensa_backtrace_kernel(struct pt_regs *regs, unsigned int depth,
			     int (*kfn)(struct stackframe *frame, void *data),
			     int (*ufn)(struct stackframe *frame, void *data),
			     void *data);
void xtensa_backtrace_user(struct pt_regs *regs, unsigned int depth,
			   int (*ufn)(struct stackframe *frame, void *data),
			   void *data);

#endif /* _XTENSA_STACKTRACE_H */

Annotation

• Immediate include surface: `linux/sched.h`.
• Detected declarations: `struct stackframe`.
• Atlas domain: Architecture Layer / arch/xtensa.
• 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.