drivers/virt/coco/efi_secret/Kconfig

Source file repositories/reference/linux-study-clean/drivers/virt/coco/efi_secret/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/virt/coco/efi_secret/Kconfig
Extension: [no extension]
Size: 664 bytes
Lines: 17
Domain: Driver Families
Bucket: drivers/virt
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 EFI_SECRET
	tristate "EFI secret area securityfs support"
	depends on EFI && (X86_64 || ARM64)
	select EFI_COCO_SECRET
	select SECURITYFS
	help
	  This is a driver for accessing the EFI secret area via securityfs.
	  The EFI secret area is a memory area designated by the firmware for
	  confidential computing secret injection (for example for AMD SEV
	  guests).  The driver exposes the secrets as files in
	  <securityfs>/secrets/coco.  Files can be read and deleted (deleting
	  a file wipes the secret from memory).

	  To compile this driver as a module, choose M here.
	  The module will be called efi_secret.

Annotation

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