drivers/perf/hisilicon/Kconfig

Source file repositories/reference/linux-study-clean/drivers/perf/hisilicon/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/perf/hisilicon/Kconfig
Extension: [no extension]
Size: 799 bytes
Lines: 27
Domain: Driver Families
Bucket: drivers/perf
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

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.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
config HISI_PMU
	tristate "HiSilicon SoC PMU drivers"
	depends on ARM64 && ACPI
	  help
	  Support for HiSilicon SoC L3 Cache performance monitor, Hydra Home
	  Agent performance monitor and DDR Controller performance monitor.

config HISI_PCIE_PMU
	tristate "HiSilicon PCIE PERF PMU"
	depends on PCI && ARM64
	help
	  Provide support for HiSilicon PCIe performance monitoring unit (PMU)
	  RCiEP devices.
	  Adds the PCIe PMU into perf events system for monitoring latency,
	  bandwidth etc.

config HNS3_PMU
	tristate "HNS3 PERF PMU"
	depends on ARM64 || COMPILE_TEST
	depends on PCI
	help
	  Provide support for HNS3 performance monitoring unit (PMU) RCiEP
	  devices.
	  Adds the HNS3 PMU into perf events system for monitoring latency,
	  bandwidth etc.

Annotation

Atlas domain: Driver Families / drivers/perf.
Implementation status: atlas-only.

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.