LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Zachary Amsden <zach@vmware.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 9/11] Panic delay fix
Date: 8 Feb 2007 14:33:21 +0100 [thread overview]
Date: Thu, 8 Feb 2007 14:33:21 +0100 [thread overview]
Message-ID: <20070208133321.GA36397@muc.de> (raw)
In-Reply-To: <45CAE87E.8070502@vmware.com>
On Thu, Feb 08, 2007 at 01:08:14AM -0800, Zachary Amsden wrote:
> Andi Kleen wrote:
> >On Wed, Feb 07, 2007 at 02:31:57PM -0800, Zachary Amsden wrote:
> >
> >>Dmitry Torokhov wrote:
> >>
> >>>I am confused - does i8042 talk to a virtual or real hardware here? In
> >>>any case I think you need to fix kernel/panic.c to have proper
> >>>(m)delay, not mess with i8042.
> >>>
> >>I think I need to fix both of them actually. This is virtual hardware,
> >>but when you grab focus on a VM, the virtual hardware gets reflected to
> >>the actual physical keyboard. Driving physical hardware that fast is bad.
> >>
> >
> >???
> >
> >Surely the physical keyboard is always handled by the host kernel?
> >I hope you're not saying it's trying to access the io ports directly?
> >
>
> No, not that. But the virtual keyboard I/O gets processed and converted
> to physical keyboard I/O when a keyboard is attached to a VM. The
You mean the commands to change the keyboard LEDs?
> result is that the virtual keyboard spinning out of control causes the
> physical keyboard to receive the same commands, far too rapidly.
Hmm i would expect the host kernel keyboard driver to throttle these.
I'm pretty sure the Linux one does the necessary mdelays at least.
> So the keyboard blinks out of control and acts as if possessed by demons.
Still sounds weird.
-Andi
next prev parent reply other threads:[~2007-02-08 13:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 3:53 Zachary Amsden
2007-02-06 12:27 ` Andi Kleen
2007-02-06 21:59 ` Zachary Amsden
2007-02-07 12:35 ` Pavel Machek
2007-02-07 20:36 ` Rusty Russell
2007-02-07 22:23 ` Zachary Amsden
2007-02-08 14:43 ` Dmitry Torokhov
2007-02-08 21:26 ` Zachary Amsden
2007-02-08 21:37 ` Dmitry Torokhov
2007-02-14 12:26 ` Pavel Machek
2007-02-14 19:47 ` Zachary Amsden
2007-02-14 12:52 ` Alan
2007-02-14 20:04 ` Zachary Amsden
2007-02-14 21:34 ` Alan
2007-02-14 21:53 ` Zachary Amsden
2007-02-15 0:33 ` Alan
2007-02-15 10:17 ` Pavel Machek
2007-02-15 23:42 ` Zachary Amsden
2007-02-15 23:49 ` Pavel Machek
2007-02-15 23:50 ` Jeremy Fitzhardinge
2007-02-16 3:22 ` Rusty Russell
2007-02-07 14:58 ` Dmitry Torokhov
2007-02-07 22:31 ` Zachary Amsden
2007-02-08 8:24 ` Andi Kleen
2007-02-08 9:08 ` Zachary Amsden
2007-02-08 13:33 ` Andi Kleen [this message]
2007-02-08 14:41 ` Dmitry Torokhov
2007-02-14 12:49 ` Alan
2007-02-14 22:51 ` Rusty Russell
2007-02-15 0:28 ` Alan
2007-02-15 13:35 ` Dmitry Torokhov
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=20070208133321.GA36397@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=zach@vmware.com \
--subject='Re: [PATCH 9/11] Panic delay fix' \
/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
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).