From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=46638 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pvv3h-0007zi-No for qemu-devel@nongnu.org; Sat, 05 Mar 2011 12:14:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pvv3g-0004RW-Hb for qemu-devel@nongnu.org; Sat, 05 Mar 2011 12:14:25 -0500 Received: from mail-qw0-f45.google.com ([209.85.216.45]:51587) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pvv3g-0004RM-Ep for qemu-devel@nongnu.org; Sat, 05 Mar 2011 12:14:24 -0500 Received: by qwj8 with SMTP id 8so2752140qwj.4 for ; Sat, 05 Mar 2011 09:14:23 -0800 (PST) Sender: Paolo Bonzini From: Paolo Bonzini Date: Sat, 5 Mar 2011 18:14:12 +0100 Message-Id: <1299345255-577-1-git-send-email-pbonzini@redhat.com> Subject: [Qemu-devel] [PATCH 0/3] really fix -icount with iothread List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: edgar.iglesias@gmail.com, mtosatti@redhat.com, jan.kiszka@web.de This is a "real" fix for -icount, real in the sense that it works in all cases including those that weren't fixed by my first attempt. Patch 1 is a sequel to my reorganization of qemu_next_deadline vs. qemu_next_alarm_deadline. Patch 2 reverts the past attempts, patch 3 is the three-line fix. Paolo Bonzini (3): qemu_next_deadline should not consider host-time timers Revert wrong fix for -icount in the iothread case really fix -icount in the iothread case cpus.c | 3 ++ qemu-timer.c | 73 +++++++++++++++++++++++++++++---------------------------- 2 files changed, 40 insertions(+), 36 deletions(-) -- 1.7.4