From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen 4 only seeing one keyboard and mouse
Date: Mon, 16 Aug 2010 18:33:54 -0400 [thread overview]
Message-ID: <20100816223354.GA4237@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1008162202140.11400@vega1.dur.ac.uk>
On Mon, Aug 16, 2010 at 10:05:58PM +0100, M A Young wrote:
> On Mon, 16 Aug 2010, Konrad Rzeszutek Wilk wrote:
>
> >There are a couple of things we can try:
> >- Compare this with the output from Xen 3.4 and see if the IOAPIC lines
> > are different. Especially if these:
> >(XEN) IOAPIC[0]: Set PCI routing entry (2-12 -> 0x78 -> IRQ 12 Mode:0 Active:0)
> >(XEN) IOAPIC[0]: Set PCI routing entry (2-1 -> 0x28 -> IRQ 1 Mode:0 Active:0
> >
> >are different. I think that previous to Xen 4, the pv-ops kernel could
> >not set the IOAPIC entries below pin 16, so you would not see them and
> >instead it would have these programmed:
> >(XEN) 01 001 01 0 0 0 0 0 1 1 28
> >(XEN) 0c 001 01 0 0 0 0 0 1 1 78
> >
> >Which is OK, as the trigger and polarity look to be correct.
>
> Logs attached as dmesg.xen3 and xm.xen3
Cool. So this is what I see
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: | (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 001 01 0 0 0 0 0 1 1 20 | (XEN) 01 001 01 0 0 0 0 0 1 1 28
(XEN) 02 001 01 0 0 0 0 0 1 1 F0 (XEN) 02 001 01 0 0 0 0 0 1 1 F0
(XEN) 03 001 01 0 0 0 0 0 1 1 28 | (XEN) 03 001 01 0 0 0 0 0 1 1 30
(XEN) 04 001 01 0 0 0 0 0 1 1 30 | (XEN) 04 001 01 0 0 0 0 0 1 1 38
(XEN) 05 001 01 0 0 0 0 0 1 1 38 | (XEN) 05 001 01 0 0 0 0 0 1 1 40
(XEN) 06 001 01 0 0 0 0 0 1 1 40 | (XEN) 06 001 01 0 0 0 0 0 1 1 48
(XEN) 07 001 01 0 0 0 0 0 1 1 48 | (XEN) 07 001 01 0 0 0 0 0 1 1 50
(XEN) 08 001 01 0 0 0 0 0 1 1 50 | (XEN) 08 001 01 0 0 0 0 0 1 1 58
(XEN) 09 001 01 1 1 0 0 0 1 1 58 | (XEN) 09 001 01 1 1 0 0 0 1 1 60
(XEN) 0a 001 01 0 0 0 0 0 1 1 60 | (XEN) 0a 001 01 0 0 0 0 0 1 1 68
(XEN) 0b 001 01 0 0 0 0 0 1 1 68 | (XEN) 0b 001 01 0 0 0 0 0 1 1 70
(XEN) 0c 001 01 0 0 0 0 0 1 1 70 | (XEN) 0c 001 01 0 0 0 0 0 1 1 78
(XEN) 0d 001 01 0 0 0 0 0 1 1 78 | (XEN) 0d 001 01 0 0 0 0 0 1 1 88
(XEN) 0e 001 01 0 0 0 0 0 1 1 88 | (XEN) 0e 001 01 0 0 0 0 0 1 1 90
(XEN) 0f 001 01 0 0 0 0 0 1 1 90 | (XEN) 0f 001 01 0 0 0 0 0 1 1 98
(XEN) 10 000 00 1 0 0 0 0 0 0 00 (XEN) 10 000 00 1 0 0 0 0 0 0 00
..
Left column is 3.4, right is 4.0.
The one thing that is odd is that in 4.0 we start with vector 0x28 while
in 3.4 it is with 0x20.
It looks as if one vector is getten eaten. But that should not be such
an issue as the internal mapping of vector->irq is still proper...
>
> >- Boot the Xen4, and trigger the IOAPIC debug printout. I think this is
> > can be done via "xm send-keys i". Also the 'q' output would be
> > usefull (it will tell us which ioports domain 0 has access to - we
> > should see dom0 see 0x60 and 0x64), and irq 1, and 12.
>
> attached as xm.debugkeys
OK. The ioports are OK, the vectors and irq are fine too.
>
> >- We can also compare this to baremetal IOAPIC programming. It should
> > be the _same_ as what Xen does. What we can do is provide
> > 'apic=debug' and that will print out the IOAPIC entries of baremetal
> > kernel. The values for irq 1 and 12 ought to be same as what Xen saw
> > and programmed it too.
>
> attached as dmesg.baremetal
Thanks. It seems to do the thing that baremetal always does..
<sigh> Still no idea what is the trouble with your box.
next prev parent reply other threads:[~2010-08-16 22:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 20:27 xen 4 only seeing one keyboard and mouse M A Young
2010-07-21 20:40 ` Pasi Kärkkäinen
2010-07-21 21:16 ` M A Young
2010-07-21 21:41 ` Pasi Kärkkäinen
2010-07-21 22:10 ` M A Young
2010-07-22 17:51 ` Konrad Rzeszutek Wilk
2010-07-22 18:54 ` M A Young
2010-07-23 14:27 ` Konrad Rzeszutek Wilk
2010-08-08 18:50 ` M A Young
2010-08-08 20:16 ` M A Young
2010-08-09 4:42 ` Konrad Rzeszutek Wilk
2010-08-16 15:46 ` Konrad Rzeszutek Wilk
2010-08-16 21:05 ` M A Young
2010-08-16 22:33 ` Konrad Rzeszutek Wilk [this message]
2010-08-18 23:25 ` Konrad Rzeszutek Wilk
2010-08-20 21:59 ` M A Young
2010-08-22 20:03 ` M A Young
2010-08-23 15:18 ` Konrad Rzeszutek Wilk
2010-08-23 19:34 ` M A Young
2010-08-23 20:37 ` M A Young
2010-08-24 17:10 ` Konrad Rzeszutek Wilk
2010-08-24 19:06 ` M A Young
2010-08-24 19:47 ` Keir Fraser
2010-08-24 20:31 ` M A Young
2010-08-24 21:16 ` Konrad Rzeszutek Wilk
2010-08-24 22:40 ` M A Young
2010-08-25 14:28 ` Konrad Rzeszutek Wilk
2010-08-25 21:32 ` M A Young
2010-08-26 14:04 ` Konrad Rzeszutek Wilk
2010-08-26 14:08 ` Keir Fraser
2010-08-26 20:53 ` M A Young
2010-08-26 22:15 ` M A Young
2010-08-26 22:24 ` M A Young
2010-08-27 7:34 ` Keir Fraser
2010-08-31 15:00 ` Konrad Rzeszutek Wilk
2010-09-03 18:50 ` M A Young
2010-09-08 15:44 ` Konrad Rzeszutek Wilk
2010-09-08 21:36 ` M A Young
2010-09-08 23:17 ` Konrad Rzeszutek Wilk
2010-09-17 22:49 ` M A Young
2010-09-20 14:51 ` Konrad Rzeszutek Wilk
2010-09-20 15:05 ` xen 4 only seeing one keyboard and mouse, fixed in xen 4.0.2-rc-pre Pasi Kärkkäinen
2010-08-21 21:00 ` xen 4 only seeing one keyboard and mouse M A Young
2010-08-23 14:24 ` Konrad Rzeszutek Wilk
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=20100816223354.GA4237@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xensource.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).