From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LV4me-0000Wk-AR for qemu-devel@nongnu.org; Thu, 05 Feb 2009 09:00:48 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LV4mZ-0000Vw-K0 for qemu-devel@nongnu.org; Thu, 05 Feb 2009 09:00:46 -0500 Received: from [199.232.76.173] (port=52264 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LV4mY-0000Vk-1O for qemu-devel@nongnu.org; Thu, 05 Feb 2009 09:00:42 -0500 Received: from mx20.gnu.org ([199.232.41.8]:2780) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LV4mX-0002FC-Ls for qemu-devel@nongnu.org; Thu, 05 Feb 2009 09:00:41 -0500 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LV4mW-000641-08 for qemu-devel@nongnu.org; Thu, 05 Feb 2009 09:00:40 -0500 From: Paul Brook Subject: Re: [Qemu-devel] wfi in qemu-system-arm (v6) on a Mac host locks up qemu Date: Thu, 5 Feb 2009 14:00:37 +0000 References: <4097E2B0-C5E8-4165-939D-0265DC189CDF@lemkeville.org> In-Reply-To: <4097E2B0-C5E8-4165-939D-0265DC189CDF@lemkeville.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902051400.37985.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 Cc: Steve Lemke On Thursday 05 February 2009, Steve Lemke wrote: > Is anyone running an ARM v6 kernel in qemu-system-arm on a Mac built > from recent qemu trunk? > > When the target issues a "wfi" (wait for interrupt) instruction, the > select timeout gets set to 5000 which appears to cause the entire app > to block in select for 5 seconds at a time and Mac OS doesn't seem to > be too thrilled about that. What exactly is OSX expecting qemu to do in that time? GUI updates (which generally involves polling the OS for GUI events) should be driven off the gui timer. If the GUI isn't active then why shouldn't we sleep for a long period of time? Paul