drivers/vfio/pci/qat/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/vfio/pci/qat/Kconfig

Extension

[no extension]

Size

449 bytes

Lines

13

Domain

Driver Families

Bucket

drivers/vfio

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 QAT_VFIO_PCI
	tristate "VFIO support for QAT VF PCI devices"
	select VFIO_PCI_CORE
	depends on CRYPTO_DEV_QAT_4XXX || CRYPTO_DEV_QAT_420XX || CRYPTO_DEV_QAT_6XXX
	help
	  This provides migration support for Intel(R) QAT Virtual Function
	  using the VFIO framework.

	  To compile this as a module, choose M here: the module
	  will be called qat_vfio_pci. If you don't know what to do here,
	  say N.

Annotation

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