drivers/perf/qcom_l2_pmu.c

File Facts

System

Linux kernel

Corpus path

drivers/perf/qcom_l2_pmu.c

Extension

.c

Size

26704 bytes

Lines

1001

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/bitops.h
• linux/bug.h
• linux/cpuhotplug.h
• linux/cpumask.h
• linux/device.h
• linux/errno.h
• linux/interrupt.h
• linux/irq.h
• linux/kernel.h
• linux/list.h
• linux/percpu.h
• linux/perf_event.h
• linux/platform_device.h
• linux/smp.h
• linux/spinlock.h
• linux/sysfs.h
• linux/types.h
• asm/barrier.h
• asm/local64.h
• asm/sysreg.h
• soc/qcom/kryo-l2-accessors.h

Detected Declarations

• struct cluster_pmu
• struct l2cache_pmu
• struct cluster_pmu
• function idx_to_reg_bit
• function cluster_pmu_reset
• function cluster_pmu_enable
• function cluster_pmu_disable
• function cluster_pmu_counter_set_value
• function cluster_pmu_counter_get_value
• function cluster_pmu_counter_enable
• function cluster_pmu_counter_disable
• function cluster_pmu_counter_enable_interrupt
• function cluster_pmu_counter_disable_interrupt
• function cluster_pmu_set_evccntcr
• function cluster_pmu_set_evcntcr
• function cluster_pmu_set_evtyper
• function cluster_pmu_set_resr
• function cluster_pmu_set_evfilter_sys_mode
• function cluster_pmu_getreset_ovsr
• function cluster_pmu_has_overflowed
• function cluster_pmu_counter_has_overflowed
• function l2_cache_event_update
• function l2_cache_cluster_set_period
• function l2_cache_get_event_idx
• function l2_cache_clear_event_idx
• function l2_cache_handle_irq
• function for_each_set_bit
• function l2_cache_pmu_enable
• function l2_cache_pmu_disable
• function l2_cache_event_init
• function for_each_sibling_event
• function for_each_sibling_event
• function l2_cache_event_start
• function l2_cache_event_stop
• function l2_cache_event_add
• function l2_cache_event_del
• function l2_cache_event_read
• function l2_cache_pmu_cpumask_show
• function l2cache_pmu_event_show
• function get_num_counters
• function list_for_each_entry
• function l2cache_pmu_online_cpu
• function l2cache_pmu_offline_cpu
• function l2_cache_pmu_probe_cluster
• function l2_cache_pmu_probe
• function l2_cache_pmu_remove
• function register_l2_cache_pmu_driver
• module init register_l2_cache_pmu_driver

Annotated Snippet

device_initcall(register_l2_cache_pmu_driver);

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/bitops.h`, `linux/bug.h`, `linux/cpuhotplug.h`, `linux/cpumask.h`, `linux/device.h`, `linux/errno.h`, `linux/interrupt.h`.
• Detected declarations: `struct cluster_pmu`, `struct l2cache_pmu`, `struct cluster_pmu`, `function idx_to_reg_bit`, `function cluster_pmu_reset`, `function cluster_pmu_enable`, `function cluster_pmu_disable`, `function cluster_pmu_counter_set_value`, `function cluster_pmu_counter_get_value`, `function cluster_pmu_counter_enable`.
• 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.