qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Huawei PSIRT <PSIRT@huawei.com>,
	P J P <ppandit@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] input: limit kbd queue depth
Date: Tue, 02 May 2017 09:12:30 +0200	[thread overview]
Message-ID: <1493709150.8581.24.camel@redhat.com> (raw)
In-Reply-To: <87h918iuo4.fsf@dusky.pond.sub.org>

  Hi,

> Drive-by comment, feel free to ignore: I'd be tempted to lower the limit
> to something comparable to actual hardware, then dumb down the queue to
> an array.

Well, the point of this queuing feature is to make automated tests a bit
easier, i.e. a script passes something longish like a install URL to
qemu, and qemu forwards it to the guest with small delays so the
keyboard hardware buffers don't overflow.

So I left he limit relatively high.  Even 1024 isn't as much as it
sounds, each typed char is at least four queue items (keydown, delay,
keyup, delay), in case modifiers are needed even more.  So this gives
buffering room for roughly 150-250 chars typed.

Also lowering the limit to something hardware-comparable is rather
pointless, we have those buffers in the hardware emulation, so we could
just drop the queuing support at input layer altogether.  I don't think
this is a good idea though.

cheers,
  Gerd

      reply	other threads:[~2017-05-02  7:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  8:42 [Qemu-devel] [PATCH] input: limit kbd queue depth Gerd Hoffmann
2017-04-28  8:49 ` Daniel P. Berrange
2017-04-28  9:05   ` Gerd Hoffmann
2017-04-28  9:09   ` P J P
2017-04-28 12:27 ` Markus Armbruster
2017-05-02  7:12   ` Gerd Hoffmann [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=1493709150.8581.24.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=PSIRT@huawei.com \
    --cc=armbru@redhat.com \
    --cc=ppandit@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).