xenbus_unmap_ring_vfree(9)

💅 xenbus_unmap_ring_vfree(9) — Kernel API Manual 💅

okay bestie, welcome to the xenbus_unmap_ring_vfree(9) page from the Kernel API Manual. We're talking about unmapping a page of memory from another domain, and yes, it's giving cross-domain cleanup realness. 💅✨

---

🌸 NAME 🌸

xenbus_unmap_ring_vfree — unmap a page of memory from another domain. periodt. 💖

🎀 SYNOPSIS 🎀

int xenbus_unmap_ring_vfree (struct xenbus_device *dev , void *vaddr );

That's the whole signature, no cap. 🫶

🦋 ARGUMENTS 🦋

• dev — xenbus device. That's your device buddy for this whole operation. 💜
• vaddr — addr to unmap. Like, the address that's getting un-mapped. ✨

⭐ DESCRIPTION ⭐

Based on Rusty Russell's skeleton driver's unmap_page. Iconic lineage, honestly. 👑

Unmap a page of memory in this domain that was imported from another domain. Very cross-domain main character energy. 🌈

Use xenbus_unmap_ring_vfree if you mapped in your memory with xenbus_map_ring_valloc — because it will free the virtual address space. That's the vibe check. 💅

💖 RETURN 💖

0 on success or GNTST_* on error (see xen/include/interface/grant_table.h). So yeah: zero = success, GNTST_* = go check that grant table header, bestie. 😭

🌟 SEE ALSO 🌟

Kernel file ./drivers/xen/xenbus/xenbus_client.c is the source-y bestie here. Also go peek at:

• xenbus_watch_path(9)
• xenbus_watch_pathfmt(9)
• xenbus_switch_state(9)
• xenbus_dev_error(9)
• xenbus_dev_fatal(9)
• xenbus_map_ring_valloc(9)
• xenbus_unmap_ring(9)
• xenbus_read_driver_state(9)

---

and that's the page, bestie 🫶 source/version: ./drivers/xen/xenbus; date: October 2026; manual: xenbus_unmap_ring_vfree(9) — mwah 💋✨🎀