From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LPbeI-0001ge-4j for qemu-devel@nongnu.org; Wed, 21 Jan 2009 06:53:35 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LPbeF-0001fo-Gm for qemu-devel@nongnu.org; Wed, 21 Jan 2009 06:53:32 -0500 Received: from [199.232.76.173] (port=49454 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPbeE-0001fg-Dn for qemu-devel@nongnu.org; Wed, 21 Jan 2009 06:53:30 -0500 Received: from smtp.eu.citrix.com ([62.200.22.115]:55731) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LPbeE-0007ef-1H for qemu-devel@nongnu.org; Wed, 21 Jan 2009 06:53:30 -0500 Message-ID: <49770BB6.9050707@eu.citrix.com> Date: Wed, 21 Jan 2009 11:49:10 +0000 From: Stefano Stabellini MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] ppc emulation and interrupts 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 Hi all, one of the recent problems, noticed after the displaystate change, affects ppc emulation only and is due to the fact that none on ppc emulation is issuing any interrupt request of the CPU_INTERRUPT_EXIT kind if the gui timer is disabled. Hence qemu never leaves the loop in cpu-exec.c:cpu_exec. If the gui timer is enabled qemu is able to leave the loop because the condition (interrupt_request & CPU_INTERRUPT_EXIT) is true when the timer is triggered. I think this is a problem with the ppc emulation but if you ppc guys need the gui timer to be always on, I can arrange for it to be. Regards, Stefano Stabellini