drivers/perf/arm_brbe.h

File Facts

System

Linux kernel

Corpus path

drivers/perf/arm_brbe.h

Extension

.h

Size

1243 bytes

Lines

48

Domain

Driver Families

Bucket

drivers/perf

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• 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 arm_pmu
• struct perf_branch_stack
• struct perf_event
• function brbe_probe
• function brbe_invalidate
• function brbe_disable
• function brbe_branch_attr_valid
• function brbe_read_filtered_entries

Annotated Snippet

static inline void brbe_probe(struct arm_pmu *arm_pmu) { }
static inline unsigned int brbe_num_branch_records(const struct arm_pmu *armpmu)
{
	return 0;
}

static inline void brbe_invalidate(void) { }

static inline void brbe_enable(const struct arm_pmu *arm_pmu) { };
static inline void brbe_disable(void) { };

static inline bool brbe_branch_attr_valid(struct perf_event *event)
{
	WARN_ON_ONCE(!has_branch_stack(event));
	return false;
}

static void brbe_read_filtered_entries(struct perf_branch_stack *branch_stack,
				       const struct perf_event *event)
{
}
#endif

Annotation

• Detected declarations: `struct arm_pmu`, `struct perf_branch_stack`, `struct perf_event`, `function brbe_probe`, `function brbe_invalidate`, `function brbe_disable`, `function brbe_branch_attr_valid`, `function brbe_read_filtered_entries`.
• Atlas domain: Driver Families / drivers/perf.
• 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.