vmmouse_report_events(9)

✨ vmmouse_report_events(9) — Kernel API Manual ✨

okay bestie, welcome to the little kernel page for vmmouse_report_events(9) 💅 it’s giving “tiny function, big communications-channel energy,” and we’re gonna get through it together 🫶

---

🎀 NAME 🎀

vmmouse_report_events — process events on the vmmouse communications channel 💖

---

🌸 SYNOPSIS 🌸

psmouse_ret_t vmmouse_report_events (struct psmouse *psmouse );

---

🦋 ARGUMENTS 🦋

• psmouse — Pointer to the psmouse struct. literally just a pointer to the psmouse struct, no cap 🫡

---

💜 DESCRIPTION 💜

so this function pulls events from the vmmouse communications channel and reports them on the correct input device — and yes, that’s the absolute or relative input device, depending on what’s correct for the event 💫

When the communications channel is drained, or if we’ve processed more than 255 psmouse commands, the function returns PSMOUSE_FULL_PACKET ✨ like “okay, packet’s full, we’re done here.”

If there’s a host- or synchronization error, the function returns PSMOUSE_BAD_DATA in the hope that the caller will reset the communications channel 😭 that’s the documented hope, bestie. the function is basically sending up a little “pls reset” signal and trusting the caller to handle it 🙈

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/input/mouse/vmmouse.c
• struct vmmouse_data(9)
• vmmouse_report_button(9)
• vmmouse_process_byte(9)
• vmmouse_disable(9)
• vmmouse_enable(9)
• vmmouse_check_hypervisor(9)
• vmmouse_detect(9)
• vmmouse_reset(9)
• vmmouse_disconnect(9)
• vmmouse_reconnect(9)
• vmmouse_init(9)

---

and that’s the whole vibe 💅 this page lives under ./drivers/input/mouse, dated October 2026, and it’s the vmmouse_report_events(9) manual — iconic, honestly 👑💖