gmap_unmap_gfn_range(9)

💅 gmap_unmap_gfn_range(9)

okay bestie, so this is a page from the Kernel API Manual and today's main character is gmap_unmap_gfn_range — say it with me, it's a mouthful, but we move 💖

✨ NAME ✨

gmap_unmap_gfn_range — unmaps a whole range of guest addresses. that's it, that's the vibe. unmap. range. periodt.

🦋 SYNOPSIS 🦋

bool gmap_unmap_gfn_range (struct gmap *gmap , struct kvm_memory_slot
*slot , gfn_t start , gfn_t end );

🎀 ARGUMENTS 🎀

• gmap — the gmap we're acting on ✨ like, the actual star of the show.
• slot — the memslot where this range lives. the address of the neighborhood, if you will 🏡
• start — the first gfn to unmap. where we start. obviously 💅
• end — the gfn after the last one to unmap. bestie this is the classic off-by-one trap 🙈 it's not the last gfn, it's the one after it, iykyk.

🌸 CONTEXT 🌸

so this gets called with the kvm mmu write lock held. as in, you already have the lock. no cap. 🫶

⭐ RETURN ⭐

returns false 💀 that's the whole return value. false. that's it.

👑 SEE ALSO 👑

kernel file ./arch/s390/kvm/gmap/gmap.c and literally the whole friend group:

gmap_new(9), gmap_dispose(9), s390_replace_asce(9), gmap_age_gfn(9), gmap_try_fixup_minor(9), gmap_2g_allowed(9), gmap_1m_allowed(9), gmap_ucas_translate(9), gmap_find_shadow(9), gmap_create_shadow(9)

<div align=center>🌈 okay that's the whole page, go unmap some things, stay hydrated, and remember this dropped out of ./arch/s390/kvm/gmap back in October 2026 🎀 mwah 💜</div>