kvm_mmu_split_memory_region(9)

🌸 kvm_mmu_split_memory_region(9) 🌸

okay so bestie, you're reading the Kernel API Manual page for kvm_mmu_split_memory_region — literally the glow-up where stage 2 blocks get split into PAGE_SIZE pages for a memory slot ✨

💅 NAME 💅

kvm_mmu_split_memory_region — split the stage 2 blocks into PAGE_SIZE pages for memory slot 🎀

✨ SYNOPSIS ✨

void kvm_mmu_split_memory_region (struct kvm *kvm , int slot );

like, that's the whole vibe. void return, two args, no drama 🌈

🫶 ARGUMENTS 🫶

• kvm — The KVM pointer 👑 (the main character, obviously)
• slot — The memory slot to split 🔪 (this is the one getting the makeover)

🔥 DESCRIPTION 🔥

So what actually goes down: it acquires kvm->mmu_lock 🔒 — no cap, that lock is taken.

And here's the tea 🍓: this whole thing is called with the kvm->slots_lock mutex already acquired, which is what serializes operations for VM memory regions. iykyk — don't be out here calling it without that mutex held, fr fr 💀

🦋 SEE ALSO 🦋

Kernel file ./arch/arm64/kvm/mmu.c — and the whole friend group 💖:

• kvm_arch_flush_remote_tlbs(9)
• __unmap_stage2_range(9)
• stage2_flush_vm(9)
• free_hyp_pgds(9)
• create_hyp_mappings(9)
• hyp_alloc_private_va_range(9)
• create_hyp_io_mappings(9)
• create_hyp_exec_mappings(9)
• kvm_init_stage2_mmu(9)
• stage2_unmap_vm(9)
• kvm_phys_addr_ioremap(9)
• kvm_stage2_wp_range(9)
• kvm_mmu_wp_memory_region(9)
• kvm_handle_guest_abort(9)

and that's the page, bestie 🧚💜 this came straight out of ./arch/arm64/kvm, dated October 2026, and it's the kvm_mmu_split_memory_region(9) manual — go split some blocks, periodt 💅⭐