arch/x86/kvm/x86.c

File Facts

System

Linux kernel

Corpus path

arch/x86/kvm/x86.c

Extension

.c

Size

403091 bytes

Lines

14519

Domain

Architecture Layer

Bucket

arch/x86

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kvm_host.h
• irq.h
• ioapic.h
• mmu.h
• i8254.h
• tss.h
• regs.h
• kvm_emulate.h
• mmu/page_track.h
• x86.h
• cpuid.h
• pmu.h
• hyperv.h
• lapic.h
• xen.h
• smm.h
• linux/clocksource.h
• linux/interrupt.h
• linux/kvm.h
• linux/fs.h
• linux/vmalloc.h
• linux/export.h
• linux/moduleparam.h
• linux/mman.h
• linux/highmem.h
• linux/iommu.h
• linux/cpufreq.h
• linux/user-return-notifier.h
• linux/srcu.h
• linux/slab.h
• linux/perf_event.h
• linux/uaccess.h

Detected Declarations

• struct kvm_user_return_msrs
• struct kvm_user_return_msr_values
• struct pvclock_clock
• struct pvclock_gtod_data
• struct kvm_x86_reg_id
• struct kvm_msr_filter_range_compat
• struct kvm_msr_filter_compat
• struct read_write_emulator_ops
• function kvm_is_immutable_feature_msr
• function kvm_is_advertised_msr
• function kvm_do_msr_access
• function kvm_destroy_user_return_msrs
• function kvm_on_user_return
• function kvm_probe_user_return_msr
• function kvm_add_user_return_msr
• function kvm_find_user_return_msr
• function kvm_user_return_msr_cpu_online
• function kvm_user_return_register_notifier
• function kvm_set_user_return_msr
• function kvm_get_user_return_msr
• function drop_user_return_notifiers
• function kvm_spurious_fault
• function exception_class
• function exception_type
• function kvm_deliver_exception_payload
• function kvm_queue_exception_vmexit
• function kvm_multiple_exception
• function kvm_queue_exception
• function kvm_queue_exception_p
• function kvm_queue_exception_e_p
• function kvm_requeue_exception
• function kvm_complete_insn_gp
• function complete_emulated_insn_gp
• function kvm_inject_page_fault
• function __kvm_inject_emulated_page_fault
• function kvm_inject_nmi
• function kvm_queue_exception_e
• function kvm_require_dr
• function pdptr_rsvd_bits
• function load_pdptrs
• function kvm_is_valid_cr0
• function kvm_post_set_cr0
• function kvm_set_cr0
• function kvm_lmsw
• function kvm_load_xfeatures
• function kvm_load_guest_pkru
• function kvm_load_host_pkru
• function kvm_guest_supported_xfd

Annotated Snippet

module_init(kvm_x86_init);

static void __exit kvm_x86_exit(void)
{
	WARN_ON_ONCE(static_branch_unlikely(&kvm_has_noapic_vcpu));
}
module_exit(kvm_x86_exit);

Annotation

• Immediate include surface: `linux/kvm_host.h`, `irq.h`, `ioapic.h`, `mmu.h`, `i8254.h`, `tss.h`, `regs.h`, `kvm_emulate.h`.
• Detected declarations: `struct kvm_user_return_msrs`, `struct kvm_user_return_msr_values`, `struct pvclock_clock`, `struct pvclock_gtod_data`, `struct kvm_x86_reg_id`, `struct kvm_msr_filter_range_compat`, `struct kvm_msr_filter_compat`, `struct read_write_emulator_ops`, `function kvm_is_immutable_feature_msr`, `function kvm_is_advertised_msr`.
• Atlas domain: Architecture Layer / arch/x86.
• Implementation status: integration implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.