arch/powerpc/include/asm/perf_event_fsl_emb.h

File Facts

System

Linux kernel

Corpus path

arch/powerpc/include/asm/perf_event_fsl_emb.h

Extension

.h

Size

1252 bytes

Lines

47

Domain

Architecture Layer

Bucket

arch/powerpc

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h
• asm/hw_irq.h

Detected Declarations

• struct fsl_emb_pmu

Annotated Snippet

struct fsl_emb_pmu {
	const char	*name;
	int		n_counter; /* total number of counters */

	/*
	 * The number of contiguous counters starting at zero that
	 * can hold restricted events, or zero if there are no
	 * restricted events.
	 *
	 * This isn't a very flexible method of expressing constraints,
	 * but it's very simple and is adequate for existing chips.
	 */
	int		n_restricted;

	/* Returns event flags and PMLCb (FSL_EMB_EVENT_*) */
	u64		(*xlate_event)(u64 event_id);

	int		n_generic;
	int		*generic_events;
	int		(*cache_events)[PERF_COUNT_HW_CACHE_MAX]
			       [PERF_COUNT_HW_CACHE_OP_MAX]
			       [PERF_COUNT_HW_CACHE_RESULT_MAX];
};

int register_fsl_emb_pmu(struct fsl_emb_pmu *);

Annotation

• Immediate include surface: `linux/types.h`, `asm/hw_irq.h`.
• Detected declarations: `struct fsl_emb_pmu`.
• Atlas domain: Architecture Layer / arch/powerpc.
• 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.