tools/perf/util/stream.h

File Facts

System

Linux kernel

Corpus path

tools/perf/util/stream.h

Extension

.h

Size

941 bytes

Lines

42

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct callchain_node
• struct evlist
• struct evsel
• struct stream
• struct evsel_streams
• struct evlist_streams

Annotated Snippet

struct stream {
	struct callchain_node	*cnode;
	struct callchain_node	*pair_cnode;
};

struct evsel_streams {
	struct stream		*streams;
	const struct evsel	*evsel;
	int			nr_streams_max;
	int			nr_streams;
	u64			streams_hits;
};

struct evlist_streams {
	struct evsel_streams	*ev_streams;
	int			nr_evsel;
};

void evlist_streams__delete(struct evlist_streams *els);

struct evlist_streams *evlist__create_streams(struct evlist *evlist,
					      int nr_streams_max);

struct evsel_streams *evsel_streams__entry(struct evlist_streams *els,
					   const struct evsel *evsel);

void evsel_streams__match(struct evsel_streams *es_base,
			  struct evsel_streams *es_pair);

void evsel_streams__report(struct evsel_streams *es_base,
			   struct evsel_streams *es_pair);

#endif /* __PERF_STREAM_H */

Annotation

• Detected declarations: `struct callchain_node`, `struct evlist`, `struct evsel`, `struct stream`, `struct evsel_streams`, `struct evlist_streams`.
• 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.