From: Juan Quintela <quintela@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
Dinar Valeev <dvaleev@suse.de>, Dirk Mueller <dmueller@suse.com>
Subject: Re: [Qemu-devel] [PATCH] hid: Extend the event queue size to 1024
Date: Tue, 19 Apr 2016 11:28:25 +0200 [thread overview]
Message-ID: <874maykkw6.fsf@emacs.mitica> (raw)
In-Reply-To: <1460643912-244245-1-git-send-email-agraf@suse.de> (Alexander Graf's message of "Thu, 14 Apr 2016 16:25:12 +0200")
Alexander Graf <agraf@suse.de> wrote:
> We can currently buffer up to 16 events in our event queue for input
> devices. While it sounds like 16 events backlog for everyone should
> be enough, our automated testing tools (OpenQA) manage to easily
> type faster than our guests can handle.
>
> So we run into queue overflows and start to drop input characters.
> By typing quickly, I was even able to reproduce this manually in
> a vnc session on SLOF.
>
> Fix this by increasing the queue buffer. With 1k events I'm sure we
> can get by for the foreseeable future. To maintain backwards compatibility
> on live migration, put the extra queue items into separate subsections.
>
> Reported-by: Dinar Valeev <dvaleev@suse.de>
> Signed-off-by: Alexander Graf <agraf@suse.de>
Hi
I see that it appears you have agreed in a different solution.
Just to say that this patch is ok from the migration point of view O:-)
Later, Juan.
PD. No, REAL HARDWARE don't have migration either O:-)
prev parent reply other threads:[~2016-04-19 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 14:25 [Qemu-devel] [PATCH] hid: Extend the event queue size to 1024 Alexander Graf
2016-04-14 15:17 ` Gerd Hoffmann
2016-04-14 15:29 ` Alexander Graf
2016-04-14 16:19 ` Gerd Hoffmann
2016-04-15 12:18 ` Dinar Valeev
2016-04-18 6:53 ` Gerd Hoffmann
2016-04-18 7:26 ` Alexander Graf
2016-04-18 9:21 ` Gerd Hoffmann
2016-04-18 9:27 ` Alexander Graf
2016-04-19 9:28 ` Juan Quintela [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=874maykkw6.fsf@emacs.mitica \
--to=quintela@redhat.com \
--cc=agraf@suse.de \
--cc=dmueller@suse.com \
--cc=dvaleev@suse.de \
--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 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).