From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H9SIs-0004Wf-LZ for qemu-devel@nongnu.org; Tue, 23 Jan 2007 15:31:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H9SIr-0004WJ-CN for qemu-devel@nongnu.org; Tue, 23 Jan 2007 15:31:38 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H9SIr-0004W4-1M for qemu-devel@nongnu.org; Tue, 23 Jan 2007 15:31:37 -0500 Received: from [84.96.92.55] (helo=smtP.neuf.fr) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H9SIq-0007Zk-F6 for qemu-devel@nongnu.org; Tue, 23 Jan 2007 15:31:36 -0500 Received: from [84.102.211.142] by sp604004mt.gpm.neuf.ld (Sun Java System Messaging Server 6.2-5.05 (built Feb 16 2006)) with ESMTP id <0JCC00HM28LOR810@sp604004mt.gpm.neuf.ld> for qemu-devel@nongnu.org; Tue, 23 Jan 2007 21:22:37 +0100 (CET) Date: Tue, 23 Jan 2007 21:22:51 +0100 From: Fabrice Bellard Subject: Re: [Qemu-devel] [RFC] IRQ acknowledge on MIPS In-reply-to: <200701231540.52240.paul@codesourcery.com> Message-id: <45B66E9B.20100@bellard.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT References: <20070123004819.GA10927@amd64.aurel32.net> <45B5CED0.7020807@aurel32.net> <00f801c73f03$0b552650$e90d11ac@spb.in.rosprint.ru> <200701231540.52240.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Paul Brook wrote: >>It should be good to have a well-defined modular IRQ routing >>architecture in the Qemu. > > > We've got most of one for the ARM targets (see hw/arm_pic.h). This file > contains both the target independent bits and the ARM specific bits for > emulating the CPU IRQ/FIQ pins. > > Annother possibility to abstract this to use a single interrupt line object > rather than an {object,index} pair. This simplifies code that that raises > interrupts, at the expense of some complication in the code to create > interrupt controllers. I prefer to have a new type 'QEMUBoolSignal' which can be used for any boolean signal. A function could be called to change its level and several clients could set a callback ("listener") to be informed that its level changes. Regards, Fabrice.