drivers/perf/arm-ccn.c

File Facts

System

Linux kernel

Corpus path

drivers/perf/arm-ccn.c

Extension

.c

Size

46350 bytes

Lines

1565

Domain

Driver Families

Bucket

drivers/perf

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/ctype.h
• linux/hrtimer.h
• linux/idr.h
• linux/interrupt.h
• linux/io.h
• linux/module.h
• linux/mod_devicetable.h
• linux/perf_event.h
• linux/platform_device.h
• linux/slab.h

Detected Declarations

• struct arm_ccn_component
• struct arm_ccn_dt
• struct arm_ccn
• struct arm_ccn_pmu_event
• function arm_ccn_node_to_xp
• function arm_ccn_node_to_xp_port
• function arm_ccn_pmu_config_set
• function here
• function arm_ccn_pmu_events_is_visible
• function arm_ccn_pmu_cmp_mask_show
• function arm_ccn_pmu_cmp_mask_store
• function arm_ccn_pmu_cpumask_show
• function arm_ccn_pmu_timer_period
• function arm_ccn_pmu_alloc_bit
• function arm_ccn_pmu_type_eq
• function arm_ccn_pmu_event_alloc
• function arm_ccn_pmu_event_release
• function arm_ccn_pmu_event_init
• function for_each_sibling_event
• function arm_ccn_pmu_read_counter
• function arm_ccn_pmu_event_update
• function arm_ccn_pmu_xp_dt_config
• function arm_ccn_pmu_event_start
• function arm_ccn_pmu_event_stop
• function arm_ccn_pmu_xp_watchpoint_config
• function arm_ccn_pmu_xp_event_config
• function arm_ccn_pmu_node_event_config
• function arm_ccn_pmu_event_config
• function arm_ccn_pmu_active_counters
• function arm_ccn_pmu_event_add
• function arm_ccn_pmu_event_del
• function arm_ccn_pmu_event_read
• function arm_ccn_pmu_enable
• function arm_ccn_pmu_disable
• function arm_ccn_pmu_overflow_handler
• function arm_ccn_pmu_timer_handler
• function arm_ccn_pmu_offline_cpu
• function arm_ccn_pmu_init
• function arm_ccn_pmu_cleanup
• function arm_ccn_for_each_valid_region
• function arm_ccn_get_nodes_num
• function arm_ccn_init_nodes
• function arm_ccn_error_handler
• function arm_ccn_irq_handler
• function arm_ccn_probe
• function arm_ccn_remove
• function arm_ccn_init
• function arm_ccn_exit

Annotated Snippet

module_init(arm_ccn_init);
module_exit(arm_ccn_exit);

MODULE_AUTHOR("Pawel Moll <pawel.moll@arm.com>");
MODULE_DESCRIPTION("ARM CCN (Cache Coherent Network) Performance Monitor Driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/ctype.h`, `linux/hrtimer.h`, `linux/idr.h`, `linux/interrupt.h`, `linux/io.h`, `linux/module.h`, `linux/mod_devicetable.h`, `linux/perf_event.h`.
• Detected declarations: `struct arm_ccn_component`, `struct arm_ccn_dt`, `struct arm_ccn`, `struct arm_ccn_pmu_event`, `function arm_ccn_node_to_xp`, `function arm_ccn_node_to_xp_port`, `function arm_ccn_pmu_config_set`, `function here`, `function arm_ccn_pmu_events_is_visible`, `function arm_ccn_pmu_cmp_mask_show`.
• Atlas domain: Driver Families / drivers/perf.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.