From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56612) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YNhAB-0001cI-HC for qemu-devel@nongnu.org; Tue, 17 Feb 2015 07:22:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YNhA6-0000wp-JA for qemu-devel@nongnu.org; Tue, 17 Feb 2015 07:22:03 -0500 Received: from mx1.redhat.com ([209.132.183.28]:47132) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YNhA6-0000wh-BE for qemu-devel@nongnu.org; Tue, 17 Feb 2015 07:21:58 -0500 Message-ID: <54E3325A.2070602@redhat.com> Date: Tue, 17 Feb 2015 13:21:46 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <20150122085127.5276.53895.stgit@PASHA-ISP.def.inno> <20150122085215.5276.8878.stgit@PASHA-ISP.def.inno> <54C9FE31.4090404@redhat.com> <001801d03ee3$c8cb7660$5a626320$@Dovgaluk@ispras.ru> <54CF6FA9.7090600@redhat.com> <28583.7738695138$1422880978@news.gmane.org> <54CF793D.6070404@redhat.com> <6071.25815372473$1424089600@news.gmane.org> <54E1E9B1.7090900@redhat.com> <8198.56250095672$1424093273@news.gmane.org> <54E1F14E.3000107@redhat.com> <39577.5216319182$1424093895@news.gmane.org> <54E1F650.5080508@redhat.com> <000001d04a8d$d65fc870$831f5950$@Dovgaluk@ispras.ru> <54E31EE1.2090809@redhat.com> <000401d04aa5$dba0c470$92e24d50$@Dovgaluk@ispras.ru> In-Reply-To: <000401d04aa5$dba0c470$92e24d50$@Dovgaluk@ispras.ru> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v8 08/21] cpu: replay instructions sequence List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pavel Dovgaluk , qemu-devel@nongnu.org Cc: peter.maydell@linaro.org, peter.crosthwaite@xilinx.com, mark.burton@greensocs.com, real@ispras.ru, batuzovk@ispras.ru, maria.klimushenkova@ispras.ru, alex.bennee@linaro.org, afaerber@suse.de, fred.konrad@greensocs.com On 17/02/2015 12:35, Pavel Dovgaluk wrote: > How can I wake up iothread if there are no pending timers? > deadline will (almost) never become zero in my case, because there is > another kind of event in the log (not the timer one). > Should I fetch the event and call qemu_notify_event() from replay module? Yes, a few mails ago I suggested that (maybe I got the wrong function in the replay module). Paolo