WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] MMIO ioremap() error with PCI passthrough

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] MMIO ioremap() error with PCI passthrough
From: Andy Burns <lists.xensource.com@xxxxxxxxxxxxxx>
Date: Tue, 01 Jul 2008 20:24:19 +0100
Delivery-date: Tue, 01 Jul 2008 12:24:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <486A7C8D.7090709@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C49024D0.1A470%keir.fraser@xxxxxxxxxxxxx> <486A7C8D.7090709@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.14) Gecko/20080421 Lightning/0.8 Thunderbird/2.0.0.14 Mnenhy/0.7.5.0
On 01/07/2008 19:50, Andy Burns wrote:

I can try to move the tuner card to the other PCI slot, but I suspect it will just share with something else instead

In the other PCI slot, the tuner shares with a USB controller and a SATA controller on the motherboard (instead of the PCI-X SATA card)

# lspci -vv| grep IRQ

        Interrupt: pin A routed to IRQ 16
        Interrupt: pin B routed to IRQ 21
        Interrupt: pin C routed to IRQ 18
        Interrupt: pin C routed to IRQ 18
        Interrupt: pin A routed to IRQ 22
        Interrupt: pin A routed to IRQ 23
        Interrupt: pin B routed to IRQ 19
        Interrupt: pin C routed to IRQ 18
        Interrupt: pin A routed to IRQ 23
        Interrupt: pin B routed to IRQ 22
        Interrupt: pin C routed to IRQ 18
        Interrupt: pin A routed to IRQ 11
        Interrupt: pin A routed to IRQ 16
        Interrupt: pin A routed to IRQ 19
        Interrupt: pin A routed to IRQ 18
        Interrupt: pin A routed to IRQ 17
        Interrupt: pin A routed to IRQ 16
        Interrupt: pin A routed to IRQ 15


# dmesg | grep -i apic
ACPI: APIC CFF80390, 0078 (r1 A_M_I_ OEMAPIC   4000828 MSFT       97)
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x05] address[0xfec10000] gsi_base[24])
IOAPIC[1]: apic_id 5, address 0xfec10000, GSI 24-279
Setting APIC routing to xen
ACPI: Using IOAPIC for interrupt routing

Is there any way to increase the number of "logical" interrupts to avoid (or give the impression of avoiding) sharing? When watching vmware servers boot, I remember they split devices into a huge number of interrupts numbering 100 upwards.

Can Xen make use of IRQ24 to 279?


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel