From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Amos Kong <akong@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] monitor: intervally send down events to guest in hold time
Date: Mon, 22 Apr 2013 17:41:37 +0200 [thread overview]
Message-ID: <51755A31.9060809@redhat.com> (raw)
In-Reply-To: <5175554B.20607@redhat.com>
Il 22/04/2013 17:20, Gerd Hoffmann ha scritto:
>> > Yes, if PS/2 keyboard emulation emulated the autorepeat rate/delay, then
>> > the code we have in QMP would just work. However it would need to be
>> > done for all devices (ignoring repeated keydown events from the upper
>> > layers, and creating its own repeated event). So it makes sense to have
>> > it in common code and have keyboard devices just tell common code the
>> > desired rate/delay.
> Yep, that'll work too.
Ok, in that sense Amos's patch is not too bad. The problems are that it
hardcodes 100/100 as the repeat/delay, and that the autorepeat is only
done for the send-key command. If the first was replaced with at least
two #defines it would be acceptable IMO.
>>> >> IIRC the (ps/2) kbd controller can be programmed with rate+delay.
>> >
>> > Yes, but we ignore the command. For the PS/2 keyboard, I think what we
>> > send now to the guest is based on the rate/delay that is emulated in
>> > software by the GUI layers (for Unix it should just be X11 for all of
>> > SDL/VNC/Spice).
> Exactly. Thats why keys getting stuck on migration isn't a big issue in
> practice.
Hmm, but if you press "a" and migrate, the receiver will see "key down
a" and no "key up a". Software autorepeat will then generate an endless
stream of a's...
It isn't a big issue because it's just very unlikely to happen, or
perhaps because no one plays games on VDI during migration.
Paolo
next prev parent reply other threads:[~2013-04-22 15:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 4:44 [Qemu-devel] [PATCH] monitor: intervally send down events to guest in hold time Amos Kong
2013-04-20 16:06 ` Eric Blake
2013-04-22 7:32 ` Amos Kong
2013-04-22 8:09 ` Amos Kong
2013-04-22 9:33 ` Paolo Bonzini
2013-04-22 12:43 ` Luiz Capitulino
2013-04-22 13:03 ` Paolo Bonzini
2013-04-22 13:35 ` Gerd Hoffmann
2013-04-22 14:32 ` Paolo Bonzini
2013-04-22 15:20 ` Gerd Hoffmann
2013-04-22 15:41 ` Paolo Bonzini [this message]
2013-04-22 14:02 ` Anthony Liguori
2013-04-22 14:22 ` Luiz Capitulino
2013-04-23 2:24 ` Amos Kong
2013-04-22 8:25 ` [Qemu-devel] [PATCH] ui/input.c: replace magic numbers by macros Amos Kong
2013-04-22 16:25 ` [Qemu-devel] [PATCH] monitor: intervally send down events to guest in hold time Eric Blake
2013-05-14 12:42 ` Laszlo Ersek
2013-05-14 14:55 ` Anthony Liguori
2013-05-15 8:13 ` Amos Kong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51755A31.9060809@redhat.com \
--to=pbonzini@redhat.com \
--cc=akong@redhat.com \
--cc=kraxel@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).