arch/x86/kvm/svm/hyperv.h

File Facts

System

Linux kernel

Corpus path

arch/x86/kvm/svm/hyperv.h

Extension

.h

Size

1774 bytes

Lines

62

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/mshyperv.h
• ../hyperv.h
• svm.h

Detected Declarations

• function nested_svm_hv_update_vm_vp_ids
• function nested_svm_l2_tlb_flush_enabled
• function nested_svm_is_l2_tlb_flush_hcall
• function nested_svm_hv_update_vm_vp_ids
• function svm_hv_inject_synthetic_vmexit_post_tlb_flush

Annotated Snippet

static inline void nested_svm_hv_update_vm_vp_ids(struct kvm_vcpu *vcpu) {}
static inline bool nested_svm_is_l2_tlb_flush_hcall(struct kvm_vcpu *vcpu)
{
	return false;
}
static inline void svm_hv_inject_synthetic_vmexit_post_tlb_flush(struct kvm_vcpu *vcpu) {}
#endif /* CONFIG_KVM_HYPERV */

#endif /* __ARCH_X86_KVM_SVM_HYPERV_H__ */

Annotation

• Immediate include surface: `asm/mshyperv.h`, `../hyperv.h`, `svm.h`.
• Detected declarations: `function nested_svm_hv_update_vm_vp_ids`, `function nested_svm_l2_tlb_flush_enabled`, `function nested_svm_is_l2_tlb_flush_hcall`, `function nested_svm_hv_update_vm_vp_ids`, `function svm_hv_inject_synthetic_vmexit_post_tlb_flush`.
• 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.