vmmouse_report_button(9)

💖 NAME 💖

okay bestie, this is vmmouse_report_button(9) from the Kernel API Manual, and the name is literally the whole assignment: report button state on the correct input device. periodt 💅✨

📜 SYNOPSIS 📜

void vmmouse_report_button (struct psmouse *psmouse , struct input_dev *abs_dev , struct input_dev *rel_dev , struct input_dev *pref_dev , unsigned int code , int value );

🎀 ARGUMENTS 🎀

• psmouse — pointer to the struct psmouse struct 🐭
• abs_dev — the absolute input device ✨
• rel_dev — the relative input device 🎀
• pref_dev — the preferred device for reporting 👑
• code — button code 🔥
• value — button value ⭐

✨ DESCRIPTION ✨

so here’s the tea 🍓: this reports value and code on pref_dev — unless the button is already pressed on the other device, in which case the state is reported on that device instead. no cap, that’s the rule 🫶💖

👀 SEE ALSO 👀

• Kernel file ./drivers/input/mouse/vmmouse.c 📁
• struct vmmouse_data(9) 🧚
• vmmouse_report_events(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) 🌱

mwah 💋 this cutie came from the source ./drivers/input/mouse, dated October 2026, and it’s the vmmouse_report_button(9) page. bye bestie 🫶🌈