From: Anthony Liguori <anthony@codemonkey.ws>
To: Dinesh Subhraveti <subhraveti@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] No keyboard / mouse after reboot
Date: Mon, 13 Jul 2009 20:10:24 -0500 [thread overview]
Message-ID: <4A5BDB00.8030100@codemonkey.ws> (raw)
In-Reply-To: <04b201ca0411$514a9d40$732d2b09@DineshThinkpad>
Needs a Signed-off-by. However...
Dinesh Subhraveti wrote:
> At system initialization, some guests conclude that i8042 controller
> is missing when the PS2 buffer is full. As a result, the guest comes
> up with no keyboard or mouse. The behavior is seen when the user
> types or mouses over the VNC window during the BIOS phase of a reboot,
> causing the PS2 buffer to fill up. It doesn't occur when the system
> boots the first time, since the device is initially disabled and
> doesn't accept events.
>
> This patch tunes Qemu parameters to reasonable values which make the
> guest happy. Linux assumes the size of PS2 buffer to be 16 bytes,
> while Qemu defines it as 256. Reducing PS2_QUEUE_SIZE to 15 ensures
> that the guest never sees the buffer to be full.
Why is Linux making assumptions about queue size being 16? It sounds
broken to me. In fact, I looked in one of my PC hardware books and it
claims that the typical KBD buffer size is around 20 bytes so if Linux
is assuming 16, it's definitely broken.
But there's speculation in the previous thread that we're masking a BIOS
bug. Has that been ruled out?
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-07-14 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 23:26 [Qemu-devel] [PATCH] No keyboard / mouse after reboot Dinesh Subhraveti
2009-07-14 1:10 ` Anthony Liguori [this message]
2009-07-14 1:42 ` [Qemu-devel] " Dinesh Subhraveti
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=4A5BDB00.8030100@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=subhraveti@gmail.com \
/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).