This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: dom0, guests, pci hardware and interrupts...

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: dom0, guests, pci hardware and interrupts...
From: Mike Carney <mc-al34luc@xxxxxxxxxxxxx>
Date: Fri, 10 Aug 2007 11:59:39 -0700
Delivery-date: Fri, 10 Aug 2007 11:59:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Followup-to: gmane.comp.emulators.xen.devel
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <f9i2tk$ra0$1@xxxxxxxxxxxxx> <C2E251A8.14054%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KNode/0.10.5
Hi Keir,

Thanks for your response.

Keir Fraser wrote:

> On 10/8/07 17:15, "Mike Carney" <mc-al34luc@xxxxxxxxxxxxx> wrote:
>> Any suggestions for how to influence the interrupts that are assigned to
>> devices in dom0? It seems that there are a number of physical interrupts
>> that are not used, and some are shared:
> If the device interrupts are aliasing then that is because the physical
> interrupt lines are physically wired together. There's nothing you can do
> about that, except try moving PCI cards to different slots (if one of your
> devices is not built in to the mobo chipset) and hence use a different
> physical interrupt line for that PCI card.
> Which interrupt number is shared? If you 'xm debug-key z' and then 'xm
> dmesg', a bunch of IO-APIC related debug output should be printed. This
> might yield some interesting info (probably just confirming that your
> devices really are wired to the same interrupt line).
>  -- Keir

Attached please find the output of xm dmesg after xm debug-key z. Any
help in parsing this would be appreciated.



Attachment: dmesg
Description: Text Data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>