From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55892) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyLrf-0006sl-Fb for qemu-devel@nongnu.org; Fri, 29 May 2015 11:06:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YyLrb-0004lE-Fs for qemu-devel@nongnu.org; Fri, 29 May 2015 11:06:27 -0400 Received: from zimbra3.corp.accelance.fr ([2001:4080:204::2:8]:53312) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyLrb-0004l7-9G for qemu-devel@nongnu.org; Fri, 29 May 2015 11:06:23 -0400 Date: Fri, 29 May 2015 17:06:18 +0200 (CEST) From: Victor Clement Message-ID: <1749470008.763543.1432911978684.JavaMail.root@openwide.fr> In-Reply-To: <55684A1E.5070306@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 0/3] implement a new icount_no_rt mode List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: =?utf-8?Q?fran=C3=A7ois?= Guerret , Paolo Bonzini , Julien Viard de Galbert ----- Mail original ----- > De: "Paolo Bonzini" > =C3=80: "Victor Clement" , qemu-devel@nongnu.= org > Cc: "fran=C3=A7ois Guerret" , "Julien Viard = de Galbert" > Envoy=C3=A9: Vendredi 29 Mai 2015 13:14:38 > Objet: Re: [Qemu-devel] [PATCH 0/3] implement a new icount_no_rt mode >=20 >=20 >=20 > On 29/05/2015 10:54, Victor Clement wrote: > > ----- Mail original ----- > >> De: "Paolo Bonzini" > >> =C3=80: "Victor CLEMENT" , > >> qemu-devel@nongnu.org > >> Cc: "francois guerret" > >> Envoy=C3=A9: Mercredi 27 Mai 2015 14:52:55 > >> Objet: Re: [Qemu-devel] [PATCH 0/3] implement a new icount_no_rt > >> mode > >> > >> [...] Or are there other cases besides RTC devices? > >=20 > > The scenario engine and the trace recorder will need to use the > > virtual > > clock, so that all dates are based on the same clock. >=20 > Right, but there is no reason for these to use any other clock than > the > virtual clock. >=20 > > I hope this enlighten you on our motivations. >=20 > I understood your motivations; I'm still not really sure what other > modifications you need in order to achieve determinism. >=20 > Paolo >=20 Normally none for determinism. The only modification we need for our use case is to add some interfaces wi= th the scenario engine=20 and the trace recorder. Victor