tools/perf/ui/progress.h

File Facts

System

Linux kernel

Corpus path

tools/perf/ui/progress.h

Extension

.h

Size

773 bytes

Lines

35

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

• linux/types.h

Detected Declarations

• struct ui_progress
• struct ui_progress_ops

Annotated Snippet

struct ui_progress {
	const char *title;
	u64 curr, next, step, total;
	bool size;
};

void __ui_progress__init(struct ui_progress *p, u64 total,
			 const char *title, bool size);

#define ui_progress__init(p, total, title) \
	__ui_progress__init(p, total, title, false)

#define ui_progress__init_size(p, total, title) \
	__ui_progress__init(p, total, title, true)

void ui_progress__update(struct ui_progress *p, u64 adv);

struct ui_progress_ops {
	void (*init)(struct ui_progress *p);
	void (*update)(struct ui_progress *p);
	void (*finish)(void);
};

extern struct ui_progress_ops *ui_progress__ops;

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct ui_progress`, `struct ui_progress_ops`.
• 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.