drivers/perf/alibaba_uncore_drw_pmu.c

File Facts

System

Linux kernel

Corpus path

drivers/perf/alibaba_uncore_drw_pmu.c

Extension

.c

Size

23336 bytes

Lines

824

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/bitfield.h
• linux/bitmap.h
• linux/bitops.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/module.h
• linux/mutex.h
• linux/perf_event.h
• linux/platform_device.h
• linux/printk.h
• linux/rculist.h
• linux/refcount.h

Detected Declarations

• struct ali_drw_pmu_irq
• struct ali_drw_pmu
• function ali_drw_pmu_format_show
• function ali_drw_pmu_event_show
• function ali_drw_pmu_cpumask_show
• function ali_drw_pmu_identifier_attr_visible
• function ali_drw_get_counter_idx
• function ali_drw_pmu_read_counter
• function ali_drw_pmu_event_update
• function ali_drw_pmu_event_set_period
• function ali_drw_pmu_enable_counter
• function ali_drw_pmu_disable_counter
• function ali_drw_pmu_isr
• function list_for_each_entry
• function ali_drw_pmu_init_irq
• function ali_drw_pmu_uninit_irq
• function ali_drw_pmu_event_init
• function for_each_sibling_event
• function ali_drw_pmu_start
• function ali_drw_pmu_stop
• function ali_drw_pmu_add
• function ali_drw_pmu_del
• function ali_drw_pmu_read
• function ali_drw_pmu_probe
• function ali_drw_pmu_remove
• function ali_drw_pmu_offline_cpu
• function ali_drw_pmu_init
• function ali_drw_pmu_exit
• module init ali_drw_pmu_init

Annotated Snippet

module_init(ali_drw_pmu_init);
module_exit(ali_drw_pmu_exit);

MODULE_AUTHOR("Hongbo Yao <yaohongbo@linux.alibaba.com>");
MODULE_AUTHOR("Neng Chen <nengchen@linux.alibaba.com>");
MODULE_AUTHOR("Shuai Xue <xueshuai@linux.alibaba.com>");
MODULE_DESCRIPTION("Alibaba DDR Sub-System Driveway PMU driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/bitfield.h`, `linux/bitmap.h`, `linux/bitops.h`, `linux/cpuhotplug.h`, `linux/cpumask.h`, `linux/device.h`, `linux/errno.h`.
• Detected declarations: `struct ali_drw_pmu_irq`, `struct ali_drw_pmu`, `function ali_drw_pmu_format_show`, `function ali_drw_pmu_event_show`, `function ali_drw_pmu_cpumask_show`, `function ali_drw_pmu_identifier_attr_visible`, `function ali_drw_get_counter_idx`, `function ali_drw_pmu_read_counter`, `function ali_drw_pmu_event_update`, `function ali_drw_pmu_event_set_period`.
• 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.