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: Tue, 24 Aug 2010 13:10:19 -0400 [thread overview]
Message-ID: <20100824171019.GA18015@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1008232127180.26050@vega3.dur.ac.uk>
On Mon, Aug 23, 2010 at 09:37:31PM +0100, M A Young wrote:
> On Mon, 23 Aug 2010, M A Young wrote:
>
> >>We could hack it and make sure that in
> >>setup_IO_APIC_irqs for IRQ 12, we make it send to both CPUs.
> >>Something like this (compile tested only):
> >
> >I don't get any output from that modification!
>
> Which might be a 4.0.0 issue not in 4.0.1-rc6 or I might have messed
> up the test, because I do get the "hack" line segment with 4.0.1-rc6
What did the hack line say? Was the value 1, 2, something completly
random?
> though the mouse and keyboard still don't work.
I spoke with Keir a bit and he mentioned that there was a major
rework of the IRQs in 4.0, wherein we would store the IRQs per CPU
structure. That is instead of having a "globally" accessible irq structure
wherein CPUs might contend for it. The folks at Intel did this so they might
have a better idea - and I can dig up from the hg annotate logs who they
are and we can ask them. But before we go that route, the other idea was
try to disable the irq balance code. Try passing in 'noirqbalance' and see what happens
then.
next prev parent reply other threads:[~2010-08-24 17:10 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
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 [this message]
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=20100824171019.GA18015@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).