drivers/perf/arm_dsu_pmu.c

File Facts

System

Linux kernel

Corpus path

drivers/perf/arm_dsu_pmu.c

Extension

.c

Size

22943 bytes

Lines

872

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/bitmap.h
• linux/bitops.h
• linux/bug.h
• linux/cpumask.h
• linux/device.h
• linux/interrupt.h
• linux/kernel.h
• linux/module.h
• linux/of.h
• linux/perf_event.h
• linux/platform_device.h
• linux/spinlock.h
• linux/smp.h
• linux/sysfs.h
• linux/types.h
• asm/arm_dsu_pmu.h
• asm/local64.h

Detected Declarations

• struct dsu_hw_events
• struct dsu_pmu
• function Unit
• function dsu_pmu_sysfs_event_show
• function dsu_pmu_cpumask_show
• function dsu_pmu_event_attr_is_visible
• function dsu_pmu_counter_valid
• function dsu_pmu_read_counter
• function dsu_pmu_write_counter
• function dsu_pmu_get_event_idx
• function dsu_pmu_enable_counter
• function dsu_pmu_disable_counter
• function dsu_pmu_set_event
• function dsu_pmu_counter_mask
• function dsu_pmu_event_update
• function dsu_pmu_read
• function dsu_pmu_get_reset_overflow
• function dsu_pmu_set_event_period
• function dsu_pmu_handle_irq
• function for_each_set_bit
• function dsu_pmu_start
• function dsu_pmu_stop
• function dsu_pmu_add
• function dsu_pmu_del
• function dsu_pmu_enable
• function dsu_pmu_disable
• function dsu_pmu_validate_event
• function dsu_pmu_validate_group
• function dsu_pmu_event_init
• function dsu_pmu_dt_get_cpus
• function dsu_pmu_acpi_get_cpus
• function dsu_pmu_probe_pmu
• function dsu_pmu_set_active_cpu
• function dsu_pmu_init_pmu
• function dsu_pmu_device_probe
• function dsu_pmu_device_remove
• function dsu_pmu_cpu_online
• function dsu_pmu_cpu_teardown
• function dsu_pmu_init
• function dsu_pmu_exit
• module init dsu_pmu_init

Annotated Snippet

module_init(dsu_pmu_init);
module_exit(dsu_pmu_exit);

MODULE_DESCRIPTION("Perf driver for ARM DynamIQ Shared Unit");
MODULE_AUTHOR("Suzuki K Poulose <suzuki.poulose@arm.com>");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/bitmap.h`, `linux/bitops.h`, `linux/bug.h`, `linux/cpumask.h`, `linux/device.h`, `linux/interrupt.h`, `linux/kernel.h`.
• Detected declarations: `struct dsu_hw_events`, `struct dsu_pmu`, `function Unit`, `function dsu_pmu_sysfs_event_show`, `function dsu_pmu_cpumask_show`, `function dsu_pmu_event_attr_is_visible`, `function dsu_pmu_counter_valid`, `function dsu_pmu_read_counter`, `function dsu_pmu_write_counter`, `function dsu_pmu_get_event_idx`.
• 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.