arch/x86/include/asm/xen/hypervisor.h

File Facts

System

Linux kernel

Corpus path

arch/x86/include/asm/xen/hypervisor.h

Extension

.h

Size

2644 bytes

Lines

80

Domain

Architecture Layer

Bucket

arch/x86

Inferred role

Architecture Layer: implementation source

Status

source 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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• asm/bug.h
• asm/cpuid/api.h
• asm/processor.h

Detected Declarations

• struct pci_dev
• function xen_cpuid_base
• function xen_initdom_restore_msi
• function xen_sanitize_proc_cap_bits

Annotated Snippet

static inline bool xen_initdom_restore_msi(struct pci_dev *dev) { return true; }
#endif

#ifdef CONFIG_HOTPLUG_CPU
void xen_arch_register_cpu(int num);
void xen_arch_unregister_cpu(int num);
#endif

#ifdef CONFIG_PVH
void __init xen_pvh_init(struct boot_params *boot_params);
void __init mem_map_via_hcall(struct boot_params *boot_params_p);
#endif

bool xen_is_cpu_lazy_mode(void);

#if defined(CONFIG_XEN_DOM0) && defined(CONFIG_ACPI)
void xen_sanitize_proc_cap_bits(uint32_t *buf);
#else
static inline void xen_sanitize_proc_cap_bits(uint32_t *buf)
{
	BUG();
}
#endif

#endif /* _ASM_X86_XEN_HYPERVISOR_H */

Annotation

• Immediate include surface: `asm/bug.h`, `asm/cpuid/api.h`, `asm/processor.h`.
• Detected declarations: `struct pci_dev`, `function xen_cpuid_base`, `function xen_initdom_restore_msi`, `function xen_sanitize_proc_cap_bits`.
• Atlas domain: Architecture Layer / arch/x86.
• Implementation status: source 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.