include/linux/trace_printk.h

File Facts

System

Linux kernel

Corpus path

include/linux/trace_printk.h

Extension

.h

Size

6866 bytes

Lines

203

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

Dependency Surface

• linux/compiler_attributes.h
• linux/instruction_pointer.h
• linux/stddef.h
• linux/stringify.h

Detected Declarations

• enum ftrace_dump_mode
• function __printf
• function tracing_start
• function tracing_snapshot
• function __printf
• function ftrace_dump

Annotated Snippet

static inline void tracing_start(void) { }
static inline void tracing_stop(void) { }
static inline void trace_dump_stack(int skip) { }

static inline void tracing_on(void) { }
static inline void tracing_off(void) { }
static inline int tracing_is_on(void) { return 0; }
static inline void tracing_snapshot(void) { }
static inline void tracing_snapshot_alloc(void) { }

static inline __printf(1, 2)
int trace_printk(const char *fmt, ...)
{
	return 0;
}
static __printf(1, 0) inline int
ftrace_vprintk(const char *fmt, va_list ap)
{
	return 0;
}
static inline void ftrace_dump(enum ftrace_dump_mode oops_dump_mode) { }
#endif /* CONFIG_TRACING */

#endif

Annotation

• Immediate include surface: `linux/compiler_attributes.h`, `linux/instruction_pointer.h`, `linux/stddef.h`, `linux/stringify.h`.
• Detected declarations: `enum ftrace_dump_mode`, `function __printf`, `function tracing_start`, `function tracing_snapshot`, `function __printf`, `function ftrace_dump`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.