From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EphP9-0004Pj-Ak for qemu-devel@nongnu.org; Fri, 23 Dec 2005 02:31:55 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EphP5-0004Oo-1U for qemu-devel@nongnu.org; Fri, 23 Dec 2005 02:31:54 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EphP4-0004OV-0B for qemu-devel@nongnu.org; Fri, 23 Dec 2005 02:31:50 -0500 Received: from [211.5.2.73] (helo=nm01omta015.dion.ne.jp) by monty-python.gnu.org with smtp (Exim 4.34) id 1EphOJ-0004ML-Ky for qemu-devel@nongnu.org; Fri, 23 Dec 2005 02:31:03 -0500 Message-ID: <001601c60792$cc8e8630$0464a8c0@athlon> From: "Kazu" References: <001e01c60780$e8a36af0$0464a8c0@athlon> Subject: Re: [Qemu-devel] HT problem Date: Fri, 23 Dec 2005 16:30:50 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit 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, marc. Friday, December 23, 2005 marc wrote: > No the problem is unique to Windows hosts (running SMP or HT), and is due > to the fact that QEMU is not MT safe and the fact that MM callback is > called on the separate thread. The fact it worked at all (and works on > UP now) is a simple luck. None of the attempts to hack around the issue > was successful so far. TODO lists this as short term item. > > P.S. The increased frequency in the call of timeSetEvent (1 now was 10 > before) is what's causing this. > Thanks. Now I got it. Regards, Kazu