tools/objtool/include/objtool/trace.h

File Facts

System

Linux kernel

Corpus path

tools/objtool/include/objtool/trace.h

Extension

.h

Size

3391 bytes

Lines

142

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• objtool/check.h
• objtool/disas.h

Detected Declarations

• function TRACE_ALT_ARG
• function trace_enable
• function trace_disable
• function trace_depth_inc
• function trace_depth_dec
• function trace_enable
• function trace_alt_end

Annotated Snippet

static inline void trace_enable(void) {}
static inline void trace_disable(void) {}
static inline void trace_depth_inc(void) {}
static inline void trace_depth_dec(void) {}
static inline void trace_alt_begin(struct instruction *orig_insn,
				   struct alternative *alt,
				   char *alt_name) {};
static inline void trace_alt_end(struct instruction *orig_insn,
				 struct alternative *alt,
				 char *alt_name) {};

#endif

#endif /* _TRACE_H */

Annotation

• Immediate include surface: `objtool/check.h`, `objtool/disas.h`.
• Detected declarations: `function TRACE_ALT_ARG`, `function trace_enable`, `function trace_disable`, `function trace_depth_inc`, `function trace_depth_dec`, `function trace_enable`, `function trace_alt_end`.
• Atlas domain: Support Tooling And Documentation / tools.
• 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.