From: Andy Burns <lists.xensource.com@adslpipe.co.uk>
To: xen-devel@lists.xensource.com
Subject: Re: MMIO ioremap() error with PCI passthrough
Date: Tue, 01 Jul 2008 20:24:19 +0100 [thread overview]
Message-ID: <486A8463.7060805@adslpipe.co.uk> (raw)
In-Reply-To: <486A7C8D.7090709@adslpipe.co.uk>
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?
next prev parent reply other threads:[~2008-07-01 19:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 8:17 MMIO ioremap() error with PCI passthrough Andy Burns
2008-07-01 8:30 ` Keir Fraser
2008-07-01 8:58 ` Andy Burns
2008-07-01 9:45 ` Keir Fraser
2008-07-01 13:16 ` Andy Burns
2008-07-01 13:31 ` Keir Fraser
2008-07-01 15:44 ` Andy Burns
2008-07-01 16:42 ` Andy Burns
2008-07-01 17:15 ` Keir Fraser
2008-07-01 18:50 ` Andy Burns
2008-07-01 19:24 ` Andy Burns [this message]
2008-07-01 19:57 ` Keir Fraser
2008-07-01 22:27 ` Andy Burns
2008-07-02 9:35 ` Andy Burns
2008-07-02 12:54 ` Andy Burns
2008-07-02 14:09 ` Andy Burns
2008-07-01 17:10 ` Keir Fraser
2008-07-01 18:52 ` Jeremy Fitzhardinge
2008-07-01 9:09 ` Andy Burns
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=486A8463.7060805@adslpipe.co.uk \
--to=lists.xensource.com@adslpipe.co.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.