From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GfPYg-0006qn-J9
	for qemu-devel@nongnu.org; Wed, 01 Nov 2006 18:31:46 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GfPYd-0006kn-Ou
	for qemu-devel@nongnu.org; Wed, 01 Nov 2006 18:31:46 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GfPYd-0006kS-Jr
	for qemu-devel@nongnu.org; Wed, 01 Nov 2006 18:31:43 -0500
Received: from [65.74.133.4] (helo=mail.codesourcery.com)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GfPYd-0003zW-Df
	for qemu-devel@nongnu.org; Wed, 01 Nov 2006 18:31:43 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Interrupt request info
Date: Wed, 1 Nov 2006 23:31:36 +0000
References: <200611011205.1gFjwA1qs3Nl3pX2@cave.mail.atl.earthlink.net>
	<002e01c6fe0d$0d434460$7e00a8c0@DELL3G>
In-Reply-To: <002e01c6fe0d$0d434460$7e00a8c0@DELL3G>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200611012331.38312.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Roger Lathrop <ratchetr@sprynet.com>

On Wednesday 01 November 2006 23:25, Roger Lathrop wrote:
> Alessandro,
>
> All you should need to do to raise an IRQ in your code is:
> pic_set_irq(s->irq,1);
>
> When the irq is serviced (in one of your ioport traps, I would assume),
> knock the irq down:
> pic_set_irq(s->irq,0);

No. You should use pic_set_irq_new. Otherwise your code will break on machines 
with multiple interrupt controllers.

Paul