From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=50658 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PpQ71-0003OQ-AU for qemu-devel@nongnu.org; Tue, 15 Feb 2011 13:59:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PpQ70-0007Af-B3 for qemu-devel@nongnu.org; Tue, 15 Feb 2011 13:58:59 -0500 Received: from thoth.sbs.de ([192.35.17.2]:15036) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PpQ6z-0007A4-Uk for qemu-devel@nongnu.org; Tue, 15 Feb 2011 13:58:58 -0500 Message-ID: <4D5ACCED.1080906@siemens.com> Date: Tue, 15 Feb 2011 19:58:53 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <20110215175410.GA13487@amt.cnet> In-Reply-To: <20110215175410.GA13487@amt.cnet> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] fix halt emulation with icount and CONFIG_IOTHREAD List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marcelo Tosatti Cc: "Edgar E. Iglesias" , "qemu-devel@nongnu.org" , Paolo Bonzini On 2011-02-15 18:54, Marcelo Tosatti wrote: > > Note: to be applied to uq/master. > > In icount mode, halt emulation should take into account the nearest event when sleeping. > > Signed-off-by: Marcelo Tosatti > Reported-and-tested-by: "Edgar E. Iglesias" > > diff --git a/cpus.c b/cpus.c > index 468544c..21c3eba 100644 > --- a/cpus.c > +++ b/cpus.c > @@ -770,7 +770,7 @@ static void qemu_tcg_wait_io_event(void) > CPUState *env; > > while (all_cpu_threads_idle()) { > - qemu_cond_timedwait(tcg_halt_cond, &qemu_global_mutex, 1000); > + qemu_cond_timedwait(tcg_halt_cond, &qemu_global_mutex, qemu_calculate_timeout()); checkpatch.pl would complain here. More important: Paolo was proposing patches to eliminate all those fishy cond_wait timeouts. That's probably the better way to go. The timeouts only paper over missing signaling. > } > > qemu_mutex_unlock(&qemu_global_mutex); > diff --git a/vl.c b/vl.c > index b436952..8ba7e9d 100644 > --- a/vl.c > +++ b/vl.c > @@ -1335,7 +1335,7 @@ void main_loop_wait(int nonblocking) > if (nonblocking) > timeout = 0; > else { > - timeout = qemu_calculate_timeout(); > + timeout = 1000; > qemu_bh_update_timeout(&timeout); > } > Isn't this path also relevant for !IOTHREAD? What's the impact of this change for that configuration? Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux