From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaRK3-00032e-Id for qemu-devel@nongnu.org; Mon, 10 Aug 2009 05:37:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaRJw-0002zq-Bu for qemu-devel@nongnu.org; Mon, 10 Aug 2009 05:37:40 -0400 Received: from [199.232.76.173] (port=43096 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaRJw-0002zi-0J for qemu-devel@nongnu.org; Mon, 10 Aug 2009 05:37:36 -0400 Received: from mx2.redhat.com ([66.187.237.31]:40518) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MaRJv-0005Fu-Fv for qemu-devel@nongnu.org; Mon, 10 Aug 2009 05:37:35 -0400 Message-ID: <4A7FEBC4.2070407@redhat.com> Date: Mon, 10 Aug 2009 12:43:32 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 1/2] Route PC irqs to ISA bus instead of i8259 directly References: <1249836296-13288-1-git-send-email-avi@redhat.com> <1249836296-13288-2-git-send-email-avi@redhat.com> <2202BB40-5CA5-462B-8A5A-A9657B370B6D@suse.de> In-Reply-To: <2202BB40-5CA5-462B-8A5A-A9657B370B6D@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: sassmann@redhat.com, "qemu-devel@nongnu.org" , Olaf Dabrunz On 08/10/2009 12:04 PM, Alexander Graf wrote: > > Am 09.08.2009 um 18:44 schrieb Avi Kivity : > >> A PC has its motherboard IRQ lines connected to both the PIC and IOAPIC. >> Currently, qemu routes IRQs to the PIC which then calls the IOAPIC, an >> incestuous arrangement. In order to clean this up, create a new ISA IRQ >> abstraction, and have devices raise ISA IRQs (which in turn raise the >> i8259 >> IRQs as usual). > > Is this really true? From my understanding the PIC in modern systems > is emulated through the IOAPIC, which is the reason we have legacy > interrupts. > For the PC emulated by qemu, it is certainly true. I don't know for sure about modern PCs, but I bet they do respond to the PIC io ports. -- error compiling committee.c: too many arguments to function