drivers/misc/pvpanic/Kconfig

Source file repositories/reference/linux-study-clean/drivers/misc/pvpanic/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/misc/pvpanic/Kconfig
Extension: [no extension]
Size: 788 bytes
Lines: 28
Domain: Driver Families
Bucket: drivers/misc
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+
#
# Pvpanic Kconfig
#
# Copyright (C) 2021 Oracle.
#

config PVPANIC
	bool "pvpanic device support"
	help
	  This option allows to select a specific pvpanic device driver.
	  pvpanic is a paravirtualized device provided by QEMU; it lets
	  a virtual machine (guest) communicate panic events to the host.

config PVPANIC_MMIO
	tristate "pvpanic MMIO device support"
	depends on HAS_IOMEM && (ACPI || OF) && PVPANIC
	help
	  This driver provides support for the MMIO pvpanic device.

config PVPANIC_PCI
	tristate "pvpanic PCI device support"
	depends on PCI && PVPANIC
	help
	  This driver provides support for the PCI pvpanic device.
	  pvpanic is a paravirtualized device provided by QEMU which
	  forwards the panic events from the guest to the host.

Annotation

Atlas domain: Driver Families / drivers/misc.
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.