Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spice input #7

Open
arcnmx opened this issue Feb 28, 2018 · 1 comment
Open

Spice input #7

arcnmx opened this issue Feb 28, 2018 · 1 comment

Comments

@arcnmx
Copy link
Owner

arcnmx commented Feb 28, 2018 •
edited
Loading

Are there any real advantages over uinput in doing this?

Main advantage here is probably permissions and simpler setup. Looks like spice only works with input-linux driver and not vioinput so seems kind of inferior in performance, but maybe the spice agent running in the VM can handle input properly?

EDIT: can be used with virtio-mouse-pci, virtio-keyboard-pci, virtio-tablet-pci. Still not ideal because it goes through qemu's input handling, and this means device swapping for relative/absolute mode switching, but still something.
@arcnmx
Copy link
Owner Author

arcnmx commented Aug 17, 2020

The new QMP input routing mode accomplishes almost the same thing. It may not be as efficient (json input events just feel gross) but... it seems good enough to PA at rhythm games, I'm not really noticing perceivable input lag so it can't be that bad?

@arcnmx arcnmx mentioned this issue Aug 17, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@arcnmx