From: Eric Blake <eblake@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] vnc: add configurable keyboard delay
Date: Tue, 31 May 2016 08:57:52 -0600 [thread overview]
Message-ID: <574DA670.6000608@redhat.com> (raw)
In-Reply-To: <1464702555-32556-1-git-send-email-kraxel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
On 05/31/2016 07:49 AM, Gerd Hoffmann wrote:
> Limits the rate kbd events from the vnc server are forwarded to the
> guest, so input devices which are typically low-bandwidth can keep
> up even on bulky input.
>
> v2: update documentation too.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> qemu-options.hx | 8 ++++++++
> ui/vnc.c | 13 +++++++++++--
> ui/vnc.h | 1 +
> 3 files changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-options.hx b/qemu-options.hx
> index 6106520..82b049a 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -1410,6 +1410,14 @@ everybody else. 'ignore' completely ignores the shared flag and
> allows everybody connect unconditionally. Doesn't conform to the rfb
> spec but is traditional QEMU behavior.
>
> +@item key-delay-ms
> +
> +Set keyboard delay, for key down and key up events, in miliseconds.
s/mili/milli/
> +Default is 1. Keyboards are low-bandwidth devices, so this slowdown
> +can help device and guest to keep up and not loose events in case
s/device/the device/
s/loose/lose/
> +events are arriving in bulk. Possible causes for the latter are flaky
> +network connections, or scripts for automated testing.
> +
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2016-05-31 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 13:49 [Qemu-devel] [PATCH v2] vnc: add configurable keyboard delay Gerd Hoffmann
2016-05-31 14:57 ` Eric Blake [this message]
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=574DA670.6000608@redhat.com \
--to=eblake@redhat.com \
--cc=kraxel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.