Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@kernel.org>
Cc: Sasha Levin <levinsasha928@gmail.com>,
	kvm@vger.kernel.org, asias.hejun@gmail.com, gorcunov@gmail.com,
	prasadjoshi124@gmail.com, John Floren <john@jfloren.net>
Subject: Re: [PATCH] kvm tools: Add support for PS/2 keyboard system
Date: Thu, 2 Jun 2011 11:34:39 +0200	[thread overview]
Message-ID: <20110602093439.GA10741@elte.hu> (raw)
In-Reply-To: <1307006604.27309.0.camel@jaguar>


* Pekka Enberg <penberg@kernel.org> wrote:

> On Thu, 2011-06-02 at 11:18 +0200, Ingo Molnar wrote:
> > * Pekka Enberg <penberg@kernel.org> wrote:
> > 
> > > On Thu, 2 Jun 2011, Sasha Levin wrote:
> > > >Strange, those are the same errors you're supposed to get when theres no
> > > >i8042 device at all.
> > > >
> > > >Could you verify that hw/pckbd.c is being built? Did the makefile get
> > > >updated?
> > > >
> > > >What I'm seeing here is:
> > > >
> > > >[   49.326316] i8042: PNP: No PS/2 controller found. Probing ports
> > > >directly.
> > > >[   50.410492] serio: i8042 KBD port at 0x60,0x64 irq 1
> > > >[   51.518829] serio: i8042 AUX port at 0x60,0x64 irq 12
> > > >[   51.519104] mousedev: PS/2 mouse device common for all mice
> > > 
> > > kbd_init() is called if that's what you wanted to know.
> > 
> > btw., i suspect port IO printf()s in i8042.c would be rather 
> > informative now: they would nicely and synchronously interlace with 
> > guest serial console output, showing exactly what is going on in the 
> > probing sequence.
> 
> Do you mean a generic ioport tracing thing?
> 
>   ./kvm run --trace=ioport
> 
> or something?

heh, yeah :-)

btw., i'm getting the same message here:

[    1.458000] usbcore: registered new interface driver libusual
[    1.460000] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    1.463000] i8042: Can't read CTR while initializing i8042
[    1.464000] i8042: probe of i8042 failed with error -5
[    1.465000] mousedev: PS/2 mouse device common for all mice
[    1.467000] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0

Thanks,

	Ingo

  reply	other threads:[~2011-06-02  9:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 14:53 [PATCH] kvm tools: Add support for PS/2 keyboard system Sasha Levin
2011-06-02  7:21 ` Ingo Molnar
2011-06-02  8:57   ` Pekka Enberg
2011-06-02  8:52 ` Pekka Enberg
2011-06-02  9:10   ` Sasha Levin
2011-06-02  9:15     ` Pekka Enberg
2011-06-02  9:18       ` Ingo Molnar
2011-06-02  9:23         ` Pekka Enberg
2011-06-02  9:34           ` Ingo Molnar [this message]
2011-06-02  9:34       ` Sasha Levin
2011-06-02  9:42         ` Ingo Molnar

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=20110602093439.GA10741@elte.hu \
    --to=mingo@elte.hu \
    --cc=asias.hejun@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=john@jfloren.net \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=penberg@kernel.org \
    --cc=prasadjoshi124@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