vmballoon_lock_op(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– vmballoon_lock_op(9) β€” Kernel API Manual πŸ’–

okay bestie, pull up a chair, because this one is a Kernel API Manual page and it's literally about telling the host what's up with your balloon pages 🎈


✨ NAME ✨

vmballoon_lock_op β€” notifies the host about inflated/deflated pages.

like, it's the little messenger that goes "hey host, these pages? mine now" (or "not mine anymore"). slay. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

unsigned long vmballoon_lock_op (struct vmballoon *b , unsigned int
num_pages , enum vmballoon_page_size_type page_size , enum vmballoon_op
op );

🌸 ARGUMENTS 🌸

  • b β€” pointer to the balloon. yes, the whole balloon. 🎈
  • num_pages β€” number of inflated/deflated pages.
  • page_size β€” size of the page.
  • op β€” the type of operation (lock or unlock).

πŸ¦‹ DESCRIPTION πŸ¦‹

so the whole vibe here is: you notify the host about page(s) that were ballooned (or removed from the balloon) so that host can use it without fear that guest will need it (or stop using them since the VM does). it's giving polite handoff energy 🫢

here's the part where you gotta pay attention though, no cap: host may reject some pages, we need to check the return value and maybe submit a different page. so like, don't just fire and forget, bestie 😭 check that return value fr fr.

the pages that are inflated/deflated are pointed by b->page. that's the hookup. iykyk.


πŸ”₯ RETURN πŸ”₯

result as provided by the hypervisor. that's it, that's the tea ⭐


🌈 SEE ALSO 🌈


ok that's the whole page, go read the source in ./drivers/misc if you want the deep lore πŸ’€

and that's a wrap, bestie πŸŽ€ this lil page lives in ./drivers/misc, dated October 2026, and it's filed under vmballoon_lock_op(9) β€” go forth and check your return values, ily, bye πŸ‘‘βœ¨

πŸ“¦ where this page comes from