drivers/perf/fujitsu_uncore_pmu.c

File Facts

System

Linux kernel

Corpus path

drivers/perf/fujitsu_uncore_pmu.c

Extension

.c

Size

17844 bytes

Lines

614

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.
• 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/bitops.h
• linux/interrupt.h
• linux/io.h
• linux/list.h
• linux/mod_devicetable.h
• linux/module.h
• linux/perf_event.h
• linux/platform_device.h

Detected Declarations

• struct uncore_pmu
• enum fujitsu_uncore_pmu
• function fujitsu_uncore_counter_start
• function fujitsu_uncore_counter_stop
• function fujitsu_uncore_counter_update
• function fujitsu_uncore_init
• function fujitsu_uncore_handle_irq
• function for_each_set_bit
• function fujitsu_uncore_pmu_enable
• function fujitsu_uncore_pmu_disable
• function fujitsu_uncore_validate_event_group
• function for_each_sibling_event
• function fujitsu_uncore_event_init
• function fujitsu_uncore_event_start
• function fujitsu_uncore_event_stop
• function fujitsu_uncore_event_add
• function fujitsu_uncore_event_del
• function fujitsu_uncore_event_read
• function fujitsu_uncore_pmu_event_show
• function cpumask_show
• function fujitsu_uncore_pmu_migrate
• function fujitsu_uncore_pmu_online_cpu
• function fujitsu_uncore_pmu_offline_cpu
• function fujitsu_uncore_pmu_probe
• function fujitsu_uncore_pmu_remove
• function fujitsu_uncore_pmu_init
• function fujitsu_uncore_pmu_exit
• module init fujitsu_uncore_pmu_init

Annotated Snippet

module_init(fujitsu_uncore_pmu_init);
module_exit(fujitsu_uncore_pmu_exit);

MODULE_AUTHOR("Koichi Okuno <fj2767dz@fujitsu.com>");
MODULE_DESCRIPTION("Fujitsu Uncore PMU driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/bitfield.h`, `linux/bitops.h`, `linux/interrupt.h`, `linux/io.h`, `linux/list.h`, `linux/mod_devicetable.h`, `linux/module.h`.
• Detected declarations: `struct uncore_pmu`, `enum fujitsu_uncore_pmu`, `function fujitsu_uncore_counter_start`, `function fujitsu_uncore_counter_stop`, `function fujitsu_uncore_counter_update`, `function fujitsu_uncore_init`, `function fujitsu_uncore_handle_irq`, `function for_each_set_bit`, `function fujitsu_uncore_pmu_enable`, `function fujitsu_uncore_pmu_disable`.
• Atlas domain: Driver Families / drivers/perf.
• Implementation status: integration implementation candidate.
• 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.