From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M4swn-0006th-1C for qemu-devel@nongnu.org; Fri, 15 May 2009 04:39:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M4swi-0006tS-1i for qemu-devel@nongnu.org; Fri, 15 May 2009 04:39:16 -0400 Received: from [199.232.76.173] (port=38785 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M4swh-0006tP-V3 for qemu-devel@nongnu.org; Fri, 15 May 2009 04:39:11 -0400 Received: from mx2.redhat.com ([66.187.237.31]:47147) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M4swh-0002Ri-Bx for qemu-devel@nongnu.org; Fri, 15 May 2009 04:39:11 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n4F8dAej004085 for ; Fri, 15 May 2009 04:39:10 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n4F8d950020123 for ; Fri, 15 May 2009 04:39:10 -0400 Received: from zweiblum.home.kraxel.org (vpn-10-138.str.redhat.com [10.32.10.138]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n4F8d84P014958 for ; Fri, 15 May 2009 04:39:08 -0400 Message-ID: <4A0D2A2B.7050302@redhat.com> Date: Fri, 15 May 2009 10:39:07 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] pci irq confusion List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org" Hi, I've looked at the pci irqs for my virtual machine and figured it isn't consistent. Look: This is what the "info pci" monitor command prints (trimmed a bit for better readability): (qemu) info pci Bus 0, device 1, function 2: USB controller: PCI device 8086:7020 IRQ 9. Bus 0, device 1, function 3: Bridge: PCI device 8086:7113 IRQ 11. Bus 0, device 3, function 0: Class ff80: PCI device 5853:0001 IRQ 11. Bus 0, device 4, function 0: SCSI controller: PCI device 1000:0012 IRQ 9. Bus 0, device 5, function 0: Storage controller: PCI device 1af4:1001 IRQ 11. Bus 0, device 6, function 0: RAM controller: PCI device 1af4:1002 IRQ 9. This is what lspci says (also trimmed): 00:01.2 USB Controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) (prog-if 00 [UHCI]) Flags: bus master, fast devsel, latency 64, IRQ 9 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) Flags: medium devsel, IRQ 9 00:03.0 Class ff80: XenSource, Inc. Xen Platform Device (rev 01) Flags: fast devsel, IRQ 11 00:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a Flags: bus master, fast devsel, latency 255, IRQ 9 00:05.0 Mass storage controller: Qumranet, Inc. Virtio block device Flags: fast devsel, IRQ 10 00:06.0 RAM memory: Qumranet, Inc. Unknown device 1002 Flags: fast devsel, IRQ 9 And finally the output from /proc/interrupts (i.e. what irq the drivers are registered for): 9: 197541 IO-APIC-level uhci_hcd:usb1, virtio1, sym53c8xx 10: 224 IO-APIC-level virtio0 11: 2159 IO-APIC-level acpi, xen-platform-pci Putting the three info sources into a table gives this picture: | qemu | lspci | driver ------------------------+--------+---------+---------- 00:01.2 usb | 9 | 9 | 9 00:01.3 acpi | 11 | 9 | 11 00:03.0 xen-platform | 11 | 11 | 11 00:04.0 scsi | 9 | 9 | 9 00:05.0 virtio-blk | 11 | 10 | 10 00:06.0 virtio-baloon | 9 | 9 | 9 Note the inconsistencies for acpi and virtio-blk. Where do they come from? Is that normal? Or is that something which needs fixing? cheers, Gerd