From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GjHX3-0002Qo-9u
	for qemu-devel@nongnu.org; Sun, 12 Nov 2006 10:46:05 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GjHX1-0002PF-JG
	for qemu-devel@nongnu.org; Sun, 12 Nov 2006 10:46:04 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GjHX1-0002PB-9E
	for qemu-devel@nongnu.org; Sun, 12 Nov 2006 10:46:03 -0500
Received: from [64.233.162.201] (helo=nz-out-0102.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1GjHX1-000441-96
	for qemu-devel@nongnu.org; Sun, 12 Nov 2006 10:46:03 -0500
Received: by nz-out-0102.google.com with SMTP id i11so910857nzi
	for <qemu-devel@nongnu.org>; Sun, 12 Nov 2006 07:46:02 -0800 (PST)
Message-ID: <b921df970611120746h79a94c4dnb5faa6b09fdbd12b@mail.gmail.com>
Date: Sun, 12 Nov 2006 16:46:00 +0100
From: "Alessandro Corradi" <ale.corradi@gmail.com>
Subject: Re: [Qemu-devel] Interrupt request info
In-Reply-To: <200611012331.38312.paul@codesourcery.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_57131_14651230.1163346360150"
References: <200611011205.1gFjwA1qs3Nl3pX2@cave.mail.atl.earthlink.net>
	<002e01c6fe0d$0d434460$7e00a8c0@DELL3G>
	<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

------=_Part_57131_14651230.1163346360150
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I tried with both pic_set_irq and pic_set_irq_new but nothing happen (the
irq number is 13 and I verified with info irq in qemu monitor).
I tried also to hack i8259.c and the function is not called (I think).
What the first parameter of pic_set_irq_new is referred to?

Another question: why a new virtual device works anyway without interrupt
mechanism? isn't it essential?

Thanks

Ale

2006/11/2, Paul Brook <paul@codesourcery.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
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

------=_Part_57131_14651230.1163346360150
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I tried with both pic_set_irq and pic_set_irq_new but nothing happen
(the irq number is 13 and I verified with info irq in qemu monitor).<br>
I tried also to hack i8259.c and the function is not called (I think).<br>
What the first parameter of pic_set_irq_new is referred to?<br>
<br>
Another question: why a new virtual device works anyway without interrupt mechanism? isn't it essential?<br>
<br>
Thanks<br>
<br>
Ale<br><br><div><span class="gmail_quote">2006/11/2, Paul Brook &lt;<a href="mailto:paul@codesourcery.com">paul@codesourcery.com</a>&gt;:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday 01 November 2006 23:25, Roger Lathrop wrote:<br>&gt; Alessandro,<br>&gt;<br>&gt; All you should need to do to raise an IRQ in your code is:<br>&gt; pic_set_irq(s-&gt;irq,1);<br>&gt;<br>&gt; When the irq is serviced (in one of your ioport traps, I would assume),
<br>&gt; knock the irq down:<br>&gt; pic_set_irq(s-&gt;irq,0);<br><br>No. You should use pic_set_irq_new. Otherwise your code will break on machines<br>with multiple interrupt controllers.<br><br>Paul<br><br><br>_______________________________________________
<br>Qemu-devel mailing list<br><a href="mailto:Qemu-devel@nongnu.org">Qemu-devel@nongnu.org</a><br><a href="http://lists.nongnu.org/mailman/listinfo/qemu-devel">http://lists.nongnu.org/mailman/listinfo/qemu-devel</a><br></blockquote>
</div><br>

------=_Part_57131_14651230.1163346360150--