arch/s390/pci/pci_kvm_hook.c

File Facts

System

Linux kernel

Corpus path

arch/s390/pci/pci_kvm_hook.c

Extension

.c

Size

311 bytes

Lines

14

Domain

Architecture Layer

Bucket

arch/s390

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kvm_host.h
• linux/export.h

Detected Declarations

• export zpci_kvm_hook

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0-only
/*
 * VFIO ZPCI devices support
 *
 * Copyright (C) IBM Corp. 2022.  All rights reserved.
 *	Author(s): Pierre Morel <pmorel@linux.ibm.com>
 */

#include <linux/kvm_host.h>
#include <linux/export.h>

struct zpci_kvm_hook zpci_kvm_hook;
EXPORT_SYMBOL_GPL(zpci_kvm_hook);

Annotation

• Immediate include surface: `linux/kvm_host.h`, `linux/export.h`.
• Detected declarations: `export zpci_kvm_hook`.
• Atlas domain: Architecture Layer / arch/s390.
• Implementation status: integration implementation candidate.

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.