arch/microblaze/kernel/stacktrace.c
Source file repositories/reference/linux-study-clean/arch/microblaze/kernel/stacktrace.c
File Facts
- System
- Linux kernel
- Corpus path
arch/microblaze/kernel/stacktrace.c- Extension
.c- Size
- 830 bytes
- Lines
- 32
- Domain
- Architecture Layer
- Bucket
- arch/microblaze
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/export.hlinux/sched.hlinux/stacktrace.hlinux/thread_info.hlinux/ptrace.hasm/unwind.h
Detected Declarations
function Copyrightfunction save_stack_trace_tskexport save_stack_traceexport save_stack_trace_tsk
Annotated Snippet
#include <linux/export.h>
#include <linux/sched.h>
#include <linux/stacktrace.h>
#include <linux/thread_info.h>
#include <linux/ptrace.h>
#include <asm/unwind.h>
void save_stack_trace(struct stack_trace *trace)
{
/* Exclude our helper functions from the trace*/
trace->skip += 2;
microblaze_unwind(NULL, trace, "");
}
EXPORT_SYMBOL_GPL(save_stack_trace);
void save_stack_trace_tsk(struct task_struct *tsk, struct stack_trace *trace)
{
microblaze_unwind(tsk, trace, "");
}
EXPORT_SYMBOL_GPL(save_stack_trace_tsk);
Annotation
- Immediate include surface: `linux/export.h`, `linux/sched.h`, `linux/stacktrace.h`, `linux/thread_info.h`, `linux/ptrace.h`, `asm/unwind.h`.
- Detected declarations: `function Copyright`, `function save_stack_trace_tsk`, `export save_stack_trace`, `export save_stack_trace_tsk`.
- Atlas domain: Architecture Layer / arch/microblaze.
- Implementation status: integration 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.