arch/x86/kvm/mmu/tdp_mmu.h

Source file repositories/reference/linux-study-clean/arch/x86/kvm/mmu/tdp_mmu.h

File Facts

System: Linux kernel
Corpus path: arch/x86/kvm/mmu/tdp_mmu.h
Extension: .h
Size: 3780 bytes
Lines: 123
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.
Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

linux/kvm_host.h
spte.h

Detected Declarations

enum kvm_tdp_mmu_root_types
function kvm_tdp_mmu_get_root
function kvm_gfn_range_filter_to_root_types
function kvm_tdp_mmu_walk_lockless_begin
function kvm_tdp_mmu_walk_lockless_end
function is_tdp_mmu_page
function is_tdp_mmu_page

Annotated Snippet

static inline bool is_tdp_mmu_page(struct kvm_mmu_page *sp) { return sp->tdp_mmu_page; }
#else
static inline bool is_tdp_mmu_page(struct kvm_mmu_page *sp) { return false; }
#endif

#endif /* __KVM_X86_MMU_TDP_MMU_H */

Annotation

Immediate include surface: `linux/kvm_host.h`, `spte.h`.
Detected declarations: `enum kvm_tdp_mmu_root_types`, `function kvm_tdp_mmu_get_root`, `function kvm_gfn_range_filter_to_root_types`, `function kvm_tdp_mmu_walk_lockless_begin`, `function kvm_tdp_mmu_walk_lockless_end`, `function is_tdp_mmu_page`, `function is_tdp_mmu_page`.
Atlas domain: Architecture Layer / arch/x86.
Implementation status: source implementation candidate.
Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.