From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1G2XpB-0003Yx-Og
	for qemu-devel@nongnu.org; Mon, 17 Jul 2006 14:28:09 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1G2XpA-0003Yk-2T
	for qemu-devel@nongnu.org; Mon, 17 Jul 2006 14:28:09 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1G2Xp9-0003Yh-Qp
	for qemu-devel@nongnu.org; Mon, 17 Jul 2006 14:28:07 -0400
Received: from [64.233.182.184] (helo=nf-out-0910.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1G2Xrs-0003IE-C3
	for qemu-devel@nongnu.org; Mon, 17 Jul 2006 14:30:56 -0400
Received: by nf-out-0910.google.com with SMTP id b2so7577nfe
	for <qemu-devel@nongnu.org>; Mon, 17 Jul 2006 11:28:06 -0700 (PDT)
Message-ID: <b921df970607171128l5f62523ep37195dc00b5b676c@mail.gmail.com>
Date: Mon, 17 Jul 2006 20:28:06 +0200
From: "Alessandro Corradi" <ale.corradi@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_9611_20577527.1153160886366"
Subject: [Qemu-devel] Hardware interrupts
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 <qemu-devel@nongnu.org>

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

 <http://fabrice.bellard.free.fr/qemu/qemu-tech.html#TOC18>
<http://fabrice.bellard.free.fr/qemu/qemu-tech.html#TOC18>

Hi all,

In http://fabrice.bellard.free.fr/qemu/qemu-tech.html:

"In order to be faster, QEMU does not check at every basic block if an
hardware interrupt is pending. Instead, the user must asynchrously call a
specific function to tell that an interrupt is pending. This function resets
the chaining of the currently executing basic block. It ensures that the
execution will return soon in the main loop of the CPU emulator. Then the
main loop can test if the interrupt is pending and handle it."
What means "the user must asynchrously call a specific function..."?

In which sense "user must"?

Which "Specific function"?

How QEMU checks for hardware interrups?

Thanks

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

<h2><a name="SEC18" href="http://fabrice.bellard.free.fr/qemu/qemu-tech.html#TOC18"></a></h2>

<h2><a name="SEC18" href="http://fabrice.bellard.free.fr/qemu/qemu-tech.html#TOC18"></a></h2>

<p>Hi all,<br></p><p>In <a href="http://fabrice.bellard.free.fr/qemu/qemu-tech.html">http://fabrice.bellard.free.fr/qemu/qemu-tech.html</a>:<br>




</p><p>&quot;In order to be faster, QEMU does not check at every basic block if an
hardware interrupt is pending. Instead, the user must asynchrously
call a specific function to tell that an interrupt is pending. This
function resets the chaining of the currently executing basic
block. It ensures that the execution will return soon in the main loop
of the CPU emulator. Then the main loop can test if the interrupt is
pending and handle it.&quot;</p>What means &quot;the user  must asynchrously
call a specific function...&quot;?<br><br>In which sense &quot;user must&quot;?<br><br>Which &quot;Specific function&quot;?<br><br>How QEMU checks for hardware interrups?<br><br>Thanks<br>

------=_Part_9611_20577527.1153160886366--