tools/perf/util/addr_location.h

File Facts

System

Linux kernel

Corpus path

tools/perf/util/addr_location.h

Extension

.h

Size

763 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 thread
• struct maps
• struct map
• struct symbol
• struct addr_location

Annotated Snippet

struct addr_location {
	struct thread *thread;
	struct map    *map;
	struct symbol *sym;
	const char    *srcline;
	u64	      addr;
	char	      level;
	u8	      cpumode;
	u16	      filtered;
	s32	      cpu;
	s32	      socket;
	/* Same as machine.parallelism but within [1, nr_cpus]. */
	int	      parallelism;
	/* See he_stat.latency. */
	u64	      latency;
};

void addr_location__init(struct addr_location *al);
void addr_location__exit(struct addr_location *al);

void addr_location__copy(struct addr_location *dst, struct addr_location *src);

#endif /* __PERF_ADDR_LOCATION */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct thread`, `struct maps`, `struct map`, `struct symbol`, `struct addr_location`.
• 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.