From: Keir Fraser <keir.fraser@eu.citrix.com>
To: M A Young <m.a.young@durham.ac.uk>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xen 4 only seeing one keyboard and mouse
Date: Fri, 27 Aug 2010 08:34:44 +0100 [thread overview]
Message-ID: <C89D2924.200C3%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1008262319280.7742@vega3.dur.ac.uk>
On 26/08/2010 23:24, "M A Young" <m.a.young@durham.ac.uk> wrote:
> or perhaps it should happen in io_apic_set_pci_routing from
> xen/arch/x86/io_apic.c where the higher IRQs are set (it doesn't because
> __assign_irq_vector sees the IRQ is already in use
> old_vector = irq_to_vector(irq);
> if (old_vector) {
> cpus_and(tmp_mask, mask, cpu_online_map);
> cpus_and(tmp_mask, cfg->domain, tmp_mask);
> if (!cpus_empty(tmp_mask)) {
> cfg->vector = old_vector;
> return 0;
> }
> }
> but seems to miss the fact that it is only actually configured for one
> cpu.
Setting up for one CPU only was the whole point of the per-cpu IDT patch. It
allows the same vector on different CPUs to be bound to different
interrupts, hence increasing the system-wide interrupt limit by a factor
equal to number of CPUs in the system. As long as the interrupt controller
is programmed to only interrupt the CPU which has the vector allocated, all
is good.
-- Keir
next prev parent reply other threads:[~2010-08-27 7:34 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
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 [this message]
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=C89D2924.200C3%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=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).