drivers/perf/riscv_pmu_sbi.c

File Facts

System

Linux kernel

Corpus path

drivers/perf/riscv_pmu_sbi.c

Extension

.c

Size

47085 bytes

Lines

1573

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/mod_devicetable.h
• linux/perf/riscv_pmu.h
• linux/platform_device.h
• linux/irq.h
• linux/irqdomain.h
• linux/of_irq.h
• linux/of.h
• linux/cpu_pm.h
• linux/sched/clock.h
• linux/soc/andes/irq.h
• linux/workqueue.h
• asm/errata_list.h
• asm/sbi.h
• asm/cpufeature.h
• asm/vendor_extensions.h
• asm/vendor_extensions/andes.h

Detected Declarations

• struct sbi_pmu_event_data
• struct hw_gen_event
• struct hw_cache_event
• function pmu_sbi_check_event_info
• function pmu_sbi_check_event
• function pmu_sbi_check_std_events
• function pmu_sbi_ctr_get_width
• function pmu_sbi_ctr_is_fw
• function riscv_pmu_get_event_info
• function riscv_pmu_get_hpm_info
• function for_each_set_bit
• function pmu_sbi_csr_index
• function pmu_sbi_get_filter_flags
• function pmu_sbi_ctr_get_idx
• function pmu_sbi_ctr_clear_idx
• function pmu_event_find_cache
• function pmu_sbi_is_fw_event
• function pmu_sbi_event_map
• function pmu_sbi_snapshot_free
• function for_each_possible_cpu
• function pmu_sbi_snapshot_alloc
• function for_each_possible_cpu
• function pmu_sbi_snapshot_disable
• function pmu_sbi_snapshot_setup
• function pmu_sbi_ctr_read
• function pmu_sbi_set_scounteren
• function pmu_sbi_reset_scounteren
• function pmu_sbi_ctr_start
• function pmu_sbi_ctr_stop
• function pmu_sbi_find_num_ctrs
• function pmu_sbi_get_ctrinfo
• function pmu_sbi_stop_all
• function pmu_sbi_stop_hw_ctrs
• function pmu_sbi_start_ovf_ctrs_sbi
• function pmu_sbi_start_ovf_ctrs_snapshot
• function for_each_set_bit
• function pmu_sbi_start_overflow_mask
• function pmu_sbi_ovf_handler
• function for_each_set_bit
• function pmu_sbi_starting_cpu
• function pmu_sbi_dying_cpu
• function pmu_sbi_setup_irqs
• function riscv_cached_mvendorid
• function IS_ENABLED
• function riscv_pm_pmu_notify
• function riscv_pm_pmu_register
• function riscv_pm_pmu_unregister
• function riscv_pm_pmu_register

Annotated Snippet

device_initcall(pmu_sbi_devinit)

Annotation

• Immediate include surface: `linux/mod_devicetable.h`, `linux/perf/riscv_pmu.h`, `linux/platform_device.h`, `linux/irq.h`, `linux/irqdomain.h`, `linux/of_irq.h`, `linux/of.h`, `linux/cpu_pm.h`.
• Detected declarations: `struct sbi_pmu_event_data`, `struct hw_gen_event`, `struct hw_cache_event`, `function pmu_sbi_check_event_info`, `function pmu_sbi_check_event`, `function pmu_sbi_check_std_events`, `function pmu_sbi_ctr_get_width`, `function pmu_sbi_ctr_is_fw`, `function riscv_pmu_get_event_info`, `function riscv_pmu_get_hpm_info`.
• 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.