* dom0, guests, pci hardware and interrupts...
@ 2007-08-10 16:15 Mike Carney
2007-08-10 16:32 ` Keir Fraser
0 siblings, 1 reply; 3+ messages in thread
From: Mike Carney @ 2007-08-10 16:15 UTC (permalink / raw)
To: xen-devel
Greetings,
I configured my dom0 to hand a 3com NIC through to a guest:
# Unbind a PCI network card from its network driver
echo -n 0000:04:0d.0 > /sys/bus/pci/drivers/3c59x/unbind
# and now tell PCI Backend to watch the slot.
modprobe pciback
sleep 5
echo -n 0000:04:0d.0 > /sys/bus/pci/drivers/pciback/new_slot
# Now that the backend is watching for the slot, bind to it
echo -n 0000:04:0d.0 > /sys/bus/pci/drivers/pciback/bind
This works fine; the guest sees the NIC after the guest's py file is updated
appropriately:
pci = [ '04:0d.0' ]
What happens:
This setup works for awhile.
The interrupt for the NIC is shared with another device used by dom0. In the
best case, dom0 and the guest are running on separate CPUS, and the
interrupt driver in dom0 is called whenever a packet comes in the guest,
which is unnecessary work, imho. In the worst case, when dom0 and the guest
are sharing a CPU, and the dom0 device sharing the interrupt is something
like the disk subsystem, dom0 and the guest appear to steal interrupts from
one another, and dom0 and all the guests grind to a halt (no disk I/O in
this example).
I've tried various techniques (kernel parameters in dom0) to ensure that the
interrupt assigned to the guest's NIC is *not* shared in order to avoid
this problem, to no avail.
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:
CPU0
1: 2 Phys-irq-level i8042
6: 5 Phys-irq-level floppy
8: 1 Phys-irq-level rtc
9: 0 Phys-irq-level acpi
14: 89901 Phys-irq-level libata
15: 9347 Phys-irq-level libata
16: 0 Phys-irq-level uhci_hcd:usb1
17: 682628 Phys-irq-level uhci_hcd:usb2, peth0
18: 96245 Phys-irq-level aic7xxx
19: 356 Phys-irq-level Intel 82801BA-ICH2, eth1
256: 263502 Dynamic-irq-level timer0
257: 0 Dynamic-irq-level resched0
258: 0 Dynamic-irq-level callfunc0
259: 3823 Dynamic-irq-level xenbus
260: 180 Dynamic-irq-level console
261: 18936 Dynamic-irq-level blkif-backend
262: 9431 Dynamic-irq-level blkif-backend
263: 20035 Dynamic-irq-level blkif-backend
264: 44080 Dynamic-irq-level vif1.0
265: 12878 Dynamic-irq-level blkif-backend
266: 1071 Dynamic-irq-level vif4.0
267: 3352 Dynamic-irq-level vif2.0
268: 17074 Dynamic-irq-level blkif-backend
269: 5598 Dynamic-irq-level vif5.0
270: 118463 Dynamic-irq-level vif3.0
One would think that if the physical interrupts are available, and the
device can be configured to use them, that no sharing would occur until the
system allocated all the physical interrupts..
TIA,
Mike
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: dom0, guests, pci hardware and interrupts...
2007-08-10 16:15 dom0, guests, pci hardware and interrupts Mike Carney
@ 2007-08-10 16:32 ` Keir Fraser
2007-08-10 18:59 ` Mike Carney
0 siblings, 1 reply; 3+ messages in thread
From: Keir Fraser @ 2007-08-10 16:32 UTC (permalink / raw)
To: Mike Carney, xen-devel
On 10/8/07 17:15, "Mike Carney" <mc-al34luc@sbcglobal.net> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: dom0, guests, pci hardware and interrupts...
2007-08-10 16:32 ` Keir Fraser
@ 2007-08-10 18:59 ` Mike Carney
0 siblings, 0 replies; 3+ messages in thread
From: Mike Carney @ 2007-08-10 18:59 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Hi Keir,
Thanks for your response.
Keir Fraser wrote:
> On 10/8/07 17:15, "Mike Carney" <mc-al34luc@sbcglobal.net> 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.
Thanks,
Mike
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: dmesg --]
[-- Type: text/x-diff; name="dmesg", Size: 14918 bytes --]
__ __ _____ _ ___ _____ __ _____
\ \/ /___ _ __ |___ / / | / _ \ _ __ __|___ |/ _| __|___ |
\ // _ \ \047_ \ |_ \ | || | | |__| \047__/ __| / /| |_ / __| / /
/ \ __/ | | | ___) || || |_| |__| | | (__ / /_| _| (__ / /
/_/\_\___|_| |_| |____(_)_(_)___/ |_| \___/_/(_)_| \___/_/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.1.0-rc7-2925.13NO_PAE.fc7 (build@blacktabbysystems.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) Tue Jul 31 20:33:44 PDT 2007
Latest ChangeSet: unavailable
(XEN) Command line: /xen.gz-2.6.20-2925.13NO_PAE.fc7 dom0_mem=224M dom0_max_mem=256M dom0_max_vcpus=1 conswitch=g com1=38400,8n1 console=com1
(XEN) 0000000000000000 - 00000000000a0000 (usable)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000003ff77000 (usable)
(XEN) 000000003ff77000 - 000000003ff79000 (ACPI NVS)
(XEN) 000000003ff79000 - 0000000040000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee10000 (reserved)
(XEN) 00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 1023MB (1047644kB)
(XEN) Xen heap: 10MB (10300kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) PAE disabled.
(XEN) Processor #0 15:2 APIC version 20
(XEN) Processor #2 15:2 APIC version 20
(XEN) Processor #1 15:2 APIC version 20
(XEN) Processor #3 15:2 APIC version 20
(XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 1994.002 MHz processor.
(XEN) CPU0: Intel(R) Xeon(TM) CPU 2.00GHz stepping 07
(XEN) Mapping cpu 0 to node 255
(XEN) Booting processor 1/2 eip 90000
(XEN) Mapping cpu 1 to node 255
(XEN) CPU1: Intel(R) Xeon(TM) CPU 2.00GHz stepping 07
(XEN) Booting processor 2/1 eip 90000
(XEN) Mapping cpu 2 to node 255
(XEN) CPU2: Intel(R) Xeon(TM) CPU 2.00GHz stepping 07
(XEN) Booting processor 3/3 eip 90000
(XEN) Mapping cpu 3 to node 255
(XEN) CPU3: Intel(R) Xeon(TM) CPU 2.00GHz stepping 07
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 4 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0xc0400000 memsz=0x2b4c54
(XEN) elf_parse_binary: phdr: paddr=0xc06b5000 memsz=0x2df000
(XEN) elf_parse_binary: memory: 0xc0400000 -> 0xc0994000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xc0000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0xc0000000
(XEN) elf_xen_parse_note: ENTRY = 0xc0400000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xc0401000
(XEN) elf_xen_parse_note: HV_START_LOW = 0xfc000000
(XEN) elf_xen_parse_note: FEATURES = "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel"
(XEN) elf_xen_parse_note: PAE_MODE = "no"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xc0000000
(XEN) elf_paddr_offset = 0xc0000000
(XEN) virt_offset = 0x0
(XEN) virt_kstart = 0xc0400000
(XEN) virt_kend = 0xc0994000
(XEN) virt_entry = 0xc0400000
(XEN) Xen kernel: 32-bit, lsb
(XEN) Dom0 kernel: 32-bit, lsb, paddr 0xc0400000 -> 0xc0994000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 3c000000->3e000000 (49152 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0400000->c0994000
(XEN) Init. ramdisk: c0994000->c10c2000
(XEN) Phys-Mach map: c10c2000->c10fa000
(XEN) Start info: c10fa000->c10fa46c
(XEN) Page tables: c10fb000->c1101000
(XEN) Boot stack: c1101000->c1102000
(XEN) TOTAL: c0000000->c1400000
(XEN) ENTRY ADDRESS: c0400000
(XEN) Dom0 has maximum 1 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xc0400000 -> 0xc06b4c54
(XEN) elf_load_binary: phdr 1 at 0xc06b5000 -> 0xc0723b64
(XEN) Initrd len 0x72e000, start at 0xc0994000
(XEN) Scrubbing Free RAM: .......done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type \047CTRL-g\047 three times to switch input to Xen).
(XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4
(XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000109f1
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) mm.c:612:d2 Non-privileged (2) attempt to map I/O space 00000000
(XEN) mm.c:612:d2 Non-privileged (2) attempt to map I/O space 00000000
(XEN) mm.c:612:d1 Non-privileged (1) attempt to map I/O space 000000f0
(XEN) mm.c:612:d3 Non-privileged (3) attempt to map I/O space 000000f8
(XEN) number of MP IRQ sources: 15.
(XEN) number of IO-APIC #4 registers: 24.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #4......
(XEN) .... register #00: 00000000
(XEN) ....... : physical APIC id: 00
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00178020
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0020
(XEN) .... register #02: 00000000
(XEN) ....... : arbitration: 00
(XEN) .... register #03: 00000001
(XEN) ....... : Boot DT : 1
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 001 01 0 0 0 0 0 1 1 28
(XEN) 02 00F 0F 0 0 0 0 0 1 1 F0
(XEN) 03 00F 0F 0 0 0 0 0 1 1 30
(XEN) 04 00F 0F 0 0 0 0 0 1 1 F1
(XEN) 05 00F 0F 0 0 0 0 0 1 1 38
(XEN) 06 001 01 0 0 0 0 0 1 1 40
(XEN) 07 00F 0F 0 0 0 0 0 1 1 48
(XEN) 08 001 01 0 0 0 0 0 1 1 50
(XEN) 09 001 01 0 1 0 0 0 1 1 58
(XEN) 0a 00F 0F 0 0 0 0 0 1 1 60
(XEN) 0b 00F 0F 0 0 0 0 0 1 1 68
(XEN) 0c 00F 0F 0 0 0 0 0 1 1 70
(XEN) 0d 00F 0F 0 0 0 0 0 1 1 78
(XEN) 0e 001 01 0 0 0 0 0 1 1 88
(XEN) 0f 001 01 0 0 0 0 0 1 1 90
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 001 01 0 1 0 1 0 1 1 B0
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 001 01 0 1 0 1 0 1 1 98
(XEN) 14 001 01 0 1 0 1 0 1 1 A8
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 001 01 0 1 0 1 0 1 1 A0
(XEN) Using vector-based indexing
(XEN) IRQ to pin mappings:
(XEN) IRQ240 -> 0:2
(XEN) IRQ40 -> 0:1
(XEN) IRQ48 -> 0:3
(XEN) IRQ241 -> 0:4
(XEN) IRQ56 -> 0:5
(XEN) IRQ64 -> 0:6
(XEN) IRQ72 -> 0:7
(XEN) IRQ80 -> 0:8
(XEN) IRQ88 -> 0:9
(XEN) IRQ96 -> 0:10
(XEN) IRQ104 -> 0:11
(XEN) IRQ112 -> 0:12
(XEN) IRQ120 -> 0:13
(XEN) IRQ136 -> 0:14
(XEN) IRQ144 -> 0:15
(XEN) IRQ152 -> 0:19
(XEN) IRQ160 -> 0:23
(XEN) IRQ168 -> 0:20
(XEN) IRQ176 -> 0:17
(XEN) .................................... done.
(XEN) number of MP IRQ sources: 15.
(XEN) number of IO-APIC #4 registers: 24.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #4......
(XEN) .... register #00: 00000000
(XEN) ....... : physical APIC id: 00
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00178020
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0020
(XEN) .... register #02: 00000000
(XEN) ....... : arbitration: 00
(XEN) .... register #03: 00000001
(XEN) ....... : Boot DT : 1
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 001 01 0 0 0 0 0 1 1 28
(XEN) 02 00F 0F 0 0 0 0 0 1 1 F0
(XEN) 03 00F 0F 0 0 0 0 0 1 1 30
(XEN) 04 00F 0F 0 0 0 0 0 1 1 F1
(XEN) 05 00F 0F 0 0 0 0 0 1 1 38
(XEN) 06 001 01 0 0 0 0 0 1 1 40
(XEN) 07 00F 0F 0 0 0 0 0 1 1 48
(XEN) 08 001 01 0 0 0 0 0 1 1 50
(XEN) 09 001 01 0 1 0 0 0 1 1 58
(XEN) 0a 00F 0F 0 0 0 0 0 1 1 60
(XEN) 0b 00F 0F 0 0 0 0 0 1 1 68
(XEN) 0c 00F 0F 0 0 0 0 0 1 1 70
(XEN) 0d 00F 0F 0 0 0 0 0 1 1 78
(XEN) 0e 001 01 0 0 0 0 0 1 1 88
(XEN) 0f 001 01 0 0 0 0 0 1 1 90
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 001 01 0 1 0 1 0 1 1 B0
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 001 01 0 1 0 1 0 1 1 98
(XEN) 14 001 01 0 1 0 1 0 1 1 A8
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 001 01 0 1 0 1 0 1 1 A0
(XEN) Using vector-based indexing
(XEN) IRQ to pin mappings:
(XEN) IRQ240 -> 0:2
(XEN) IRQ40 -> 0:1
(XEN) IRQ48 -> 0:3
(XEN) IRQ241 -> 0:4
(XEN) IRQ56 -> 0:5
(XEN) IRQ64 -> 0:6
(XEN) IRQ72 -> 0:7
(XEN) IRQ80 -> 0:8
(XEN) IRQ88 -> 0:9
(XEN) IRQ96 -> 0:10
(XEN) IRQ104 -> 0:11
(XEN) IRQ112 -> 0:12
(XEN) IRQ120 -> 0:13
(XEN) IRQ136 -> 0:14
(XEN) IRQ144 -> 0:15
(XEN) IRQ152 -> 0:19
(XEN) IRQ160 -> 0:23
(XEN) IRQ168 -> 0:20
(XEN) IRQ176 -> 0:17
(XEN) .................................... done.
(XEN) number of MP IRQ sources: 15.
(XEN) number of IO-APIC #4 registers: 24.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #4......
(XEN) .... register #00: 00000000
(XEN) ....... : physical APIC id: 00
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00178020
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0020
(XEN) .... register #02: 00000000
(XEN) ....... : arbitration: 00
(XEN) .... register #03: 00000001
(XEN) ....... : Boot DT : 1
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 001 01 0 0 0 0 0 1 1 28
(XEN) 02 00F 0F 0 0 0 0 0 1 1 F0
(XEN) 03 00F 0F 0 0 0 0 0 1 1 30
(XEN) 04 00F 0F 0 0 0 0 0 1 1 F1
(XEN) 05 00F 0F 0 0 0 0 0 1 1 38
(XEN) 06 001 01 0 0 0 0 0 1 1 40
(XEN) 07 00F 0F 0 0 0 0 0 1 1 48
(XEN) 08 001 01 0 0 0 0 0 1 1 50
(XEN) 09 001 01 0 1 0 0 0 1 1 58
(XEN) 0a 00F 0F 0 0 0 0 0 1 1 60
(XEN) 0b 00F 0F 0 0 0 0 0 1 1 68
(XEN) 0c 00F 0F 0 0 0 0 0 1 1 70
(XEN) 0d 00F 0F 0 0 0 0 0 1 1 78
(XEN) 0e 001 01 0 0 0 0 0 1 1 88
(XEN) 0f 001 01 0 0 0 0 0 1 1 90
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 001 01 0 1 0 1 0 1 1 B0
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 001 01 0 1 0 1 0 1 1 98
(XEN) 14 001 01 0 1 0 1 0 1 1 A8
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 001 01 0 1 0 1 0 1 1 A0
(XEN) Using vector-based indexing
(XEN) IRQ to pin mappings:
(XEN) IRQ240 -> 0:2
(XEN) IRQ40 -> 0:1
(XEN) IRQ48 -> 0:3
(XEN) IRQ241 -> 0:4
(XEN) IRQ56 -> 0:5
(XEN) IRQ64 -> 0:6
(XEN) IRQ72 -> 0:7
(XEN) IRQ80 -> 0:8
(XEN) IRQ88 -> 0:9
(XEN) IRQ96 -> 0:10
(XEN) IRQ104 -> 0:11
(XEN) IRQ112 -> 0:12
(XEN) IRQ120 -> 0:13
(XEN) IRQ136 -> 0:14
(XEN) IRQ144 -> 0:15
(XEN) IRQ152 -> 0:19
(XEN) IRQ160 -> 0:23
(XEN) IRQ168 -> 0:20
(XEN) IRQ176 -> 0:17
(XEN) .................................... done.
(XEN) number of MP IRQ sources: 15.
(XEN) number of IO-APIC #4 registers: 24.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #4......
(XEN) .... register #00: 00000000
(XEN) ....... : physical APIC id: 00
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00178020
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0020
(XEN) .... register #02: 00000000
(XEN) ....... : arbitration: 00
(XEN) .... register #03: 00000001
(XEN) ....... : Boot DT : 1
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 001 01 0 0 0 0 0 1 1 28
(XEN) 02 00F 0F 0 0 0 0 0 1 1 F0
(XEN) 03 00F 0F 0 0 0 0 0 1 1 30
(XEN) 04 00F 0F 0 0 0 0 0 1 1 F1
(XEN) 05 00F 0F 0 0 0 0 0 1 1 38
(XEN) 06 001 01 0 0 0 0 0 1 1 40
(XEN) 07 00F 0F 0 0 0 0 0 1 1 48
(XEN) 08 001 01 0 0 0 0 0 1 1 50
(XEN) 09 001 01 0 1 0 0 0 1 1 58
(XEN) 0a 00F 0F 0 0 0 0 0 1 1 60
(XEN) 0b 00F 0F 0 0 0 0 0 1 1 68
(XEN) 0c 00F 0F 0 0 0 0 0 1 1 70
(XEN) 0d 00F 0F 0 0 0 0 0 1 1 78
(XEN) 0e 001 01 0 0 0 0 0 1 1 88
(XEN) 0f 001 01 0 0 0 0 0 1 1 90
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 001 01 0 1 0 1 0 1 1 B0
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 001 01 0 1 0 1 0 1 1 98
(XEN) 14 001 01 0 1 0 1 0 1 1 A8
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 001 01 0 1 0 1 0 1 1 A0
(XEN) Using vector-based indexing
(XEN) IRQ to pin mappings:
(XEN) IRQ240 -> 0:2
(XEN) IRQ40 -> 0:1
(XEN) IRQ48 -> 0:3
(XEN) IRQ241 -> 0:4
(XEN) IRQ56 -> 0:5
(XEN) IRQ64 -> 0:6
(XEN) IRQ72 -> 0:7
(XEN) IRQ80 -> 0:8
(XEN) IRQ88 -> 0:9
(XEN) IRQ96 -> 0:10
(XEN) IRQ104 -> 0:11
(XEN) IRQ112 -> 0:12
(XEN) IRQ120 -> 0:13
(XEN) IRQ136 -> 0:14
(XEN) IRQ144 -> 0:15
(XEN) IRQ152 -> 0:19
(XEN) IRQ160 -> 0:23
(XEN) IRQ168 -> 0:20
(XEN) IRQ176 -> 0:17
(XEN) .................................... done.
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-08-10 18:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-10 16:15 dom0, guests, pci hardware and interrupts Mike Carney
2007-08-10 16:32 ` Keir Fraser
2007-08-10 18:59 ` Mike Carney
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.