kvm_pgtable_stage2_destroy(9)

✨ NAME ✨

okay so this is the kvm_pgtable_stage2_destroy(9) page from the Kernel API Manual, and it does exactly one iconic thing: Destroy an unused guest stage-2 page-table. 💅

🎀 SYNOPSIS 🎀

void kvm_pgtable_stage2_destroy (struct kvm_pgtable *pgt );

🌸 ARGUMENTS 🌸

• pgt — the page-table structure, already initialised by kvm_pgtable_stage2_init*(). no cap, that asterisk matters. 🫶

🦋 DESCRIPTION 🦋

So here's the vibe check, bestie: the page-table is assumed to be unreachable by any hardware walkers prior to freeing, and therefore no TLB invalidation is performed. Not one. Zero. None. It's giving "you already handled that part, right?" energy 😭 — so don't come for this function expecting it to do TLB cleanup for you.

💖 SEE ALSO 💖

First up, the Kernel file ./arch/arm64/include/asm/kvm_pgtable.h — go read it, iykyk. Then the whole squad:

• struct kvm_pgtable_mm_ops(9)
• enum kvm_pgtable_stage2_flags(9)
• enum kvm_pgtable_prot(9)
• enum kvm_pgtable_walk_flags(9)
• struct kvm_pgtable_walker(9)
• struct kvm_pgtable(9)
• kvm_pgtable_hyp_init(9)
• kvm_pgtable_hyp_destroy(9)
• kvm_pgtable_hyp_map(9)
• kvm_pgtable_hyp_unmap(9)
• kvm_get_vtcr(9)
• kvm_pgtable_stage2_pgd_size(9)
• __kvm_pgtable_stage2_init(9)
• kvm_pgtable_stage2_destroy_range(9)
• kvm_pgtable_stage2_destroy_pgd(9)
• kvm_pgtable_stage2_free_unlinked(9)
• kvm_pgtable_stage2_create_unlinked(9)
• kvm_pgtable_stage2_map(9)
• kvm_pgtable_stage2_annotate(9)
• kvm_pgtable_stage2_unmap(9)
• kvm_pgtable_stage2_wrprotect(9)
• kvm_pgtable_stage2_mkyoung(9)
• kvm_pgtable_stage2_test_clear_young(9)
• kvm_pgtable_stage2_relax_perms(9)
• kvm_pgtable_stage2_split(9)
• kvm_pgtable_walk(9)
• kvm_pgtable_get_leaf(9)
• kvm_pgtable_stage2_pte_prot(9)
• kvm_pgtable_hyp_pte_prot(9)
• kvm_tlb_flush_vmid_range(9)

mwah 💖 this page lives under ./arch/arm64/include/asm, is dated October 2026, and is the kvm_pgtable_stage2_destroy(9) page — periodt. 🎀👑