tools/tracing/rtla/src/timerlat.h

File Facts

System

Linux kernel

Corpus path

tools/tracing/rtla/src/timerlat.h

Extension

.h

Size

1281 bytes

Lines

45

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

• osnoise.h

Detected Declarations

• struct timerlat_params
• enum timerlat_tracing_mode

Annotated Snippet

struct timerlat_params {
	struct common_params	common;
	long long		timerlat_period_us;
	long long		print_stack;
	int			dma_latency;
	bool			no_aa;
	bool			dump_tasks;
	int			deepest_idle_state;
	enum timerlat_tracing_mode mode;
	const char		*bpf_action_program;
	enum stack_format	stack_format;
	bool			timerlat_align;
	unsigned long long	timerlat_align_us;
};

#define to_timerlat_params(ptr) container_of(ptr, struct timerlat_params, common)

int timerlat_apply_config(struct osnoise_tool *tool, struct timerlat_params *params);
int timerlat_main(int argc, char *argv[]);
int timerlat_enable(struct osnoise_tool *tool);
void timerlat_analyze(struct osnoise_tool *tool, bool stopped);
void timerlat_free(struct osnoise_tool *tool);

Annotation

• Immediate include surface: `osnoise.h`.
• Detected declarations: `struct timerlat_params`, `enum timerlat_tracing_mode`.
• 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.