From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andy Burns <lists.xensource.com@adslpipe.co.uk>
Subject: Re: MMIO ioremap() error with PCI passthrough
Date: Tue, 01 Jul 2008 20:24:19 +0100
Message-ID: <486A8463.7060805@adslpipe.co.uk>
References: <C49024D0.1A470%keir.fraser@eu.citrix.com>
	<486A7C8D.7090709@adslpipe.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <486A7C8D.7090709@adslpipe.co.uk>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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?