drivers/perf/arm_cspmu/arm_cspmu.c

File Facts

System

Linux kernel

Corpus path

drivers/perf/arm_cspmu/arm_cspmu.c

Extension

.c

Size

36827 bytes

Lines

1448

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/acpi.h
• linux/cacheinfo.h
• linux/ctype.h
• linux/interrupt.h
• linux/io-64-nonatomic-lo-hi.h
• linux/module.h
• linux/mutex.h
• linux/of.h
• linux/perf_event.h
• linux/platform_device.h
• arm_cspmu.h
• acpi/processor.h

Detected Declarations

• function read_reg64_hilohi
• function supports_cycle_counter
• function counter_size
• function counter_mask
• function use_64b_counter_reg
• function arm_cspmu_sysfs_event_show
• function arm_cspmu_get_event_attrs
• function arm_cspmu_event_attr_is_visible
• function arm_cspmu_get_format_attrs
• function arm_cspmu_event_type
• function arm_cspmu_is_cycle_counter_event
• function arm_cspmu_identifier_show
• function arm_cspmu_cpumask_show
• function arm_cspmu_get_pmiidr
• function arm_cspmu_init_impl_ops
• function arm_cspmu_alloc_event_attr_group
• function arm_cspmu_alloc_format_attr_group
• function arm_cspmu_alloc_attr_groups
• function arm_cspmu_reset_counters
• function arm_cspmu_start_counters
• function arm_cspmu_stop_counters
• function arm_cspmu_enable
• function arm_cspmu_disable
• function arm_cspmu_get_event_idx
• function arm_cspmu_validate_event
• function arm_cspmu_validate_group
• function for_each_sibling_event
• function arm_cspmu_event_init
• function task
• function counter_offset
• function arm_cspmu_write_counter
• function arm_cspmu_read_counter
• function arm_cspmu_set_event_period
• function arm_cspmu_enable_counter
• function arm_cspmu_disable_counter
• function arm_cspmu_event_update
• function arm_cspmu_set_event
• function arm_cspmu_set_ev_filter
• function arm_cspmu_set_cc_filter
• function arm_cspmu_start
• function arm_cspmu_stop
• function to_phys_idx
• function arm_cspmu_add
• function arm_cspmu_del
• function arm_cspmu_read
• function arm_cspmu_init_mmio
• function arm_cspmu_get_reset_overflow
• function arm_cspmu_handle_irq

Annotated Snippet

module_init(arm_cspmu_init);
module_exit(arm_cspmu_exit);

MODULE_DESCRIPTION("ARM CoreSight Architecture Performance Monitor Driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/cacheinfo.h`, `linux/ctype.h`, `linux/interrupt.h`, `linux/io-64-nonatomic-lo-hi.h`, `linux/module.h`, `linux/mutex.h`, `linux/of.h`.
• Detected declarations: `function read_reg64_hilohi`, `function supports_cycle_counter`, `function counter_size`, `function counter_mask`, `function use_64b_counter_reg`, `function arm_cspmu_sysfs_event_show`, `function arm_cspmu_get_event_attrs`, `function arm_cspmu_event_attr_is_visible`, `function arm_cspmu_get_format_attrs`, `function arm_cspmu_event_type`.
• 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.