From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MJ7Gt-00033a-R9
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 10:46:52 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MJ7Gq-0002zO-4D
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 10:46:51 -0400
Received: from [199.232.76.173] (port=33729 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MJ7Gp-0002yz-Pb
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 10:46:47 -0400
Received: from mx20.gnu.org ([199.232.41.8]:13193)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1MJ7Gp-0002Y3-ES
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 10:46:47 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1MJ7Gn-0003Qh-Sg
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 10:46:46 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Re: [PATCH 06/11] QMP: Introduce asynchronous events
	infrastructure
Date: Tue, 23 Jun 2009 15:46:27 +0100
References: <cover.1245730845.git.lcapitulino@redhat.com>
	<20090623012911.16b8c4d5@doriath>
	<20090623100839.GF6881@redhat.com>
In-Reply-To: <20090623100839.GF6881@redhat.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200906231546.40616.paul@codesourcery.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org, "Daniel P. Berrange" <berrange@redhat.com>
Cc: aliguori@us.ibm.com, ehabkost@redhat.com, jan.kiszka@siemens.com, dlaor@redhat.com, Luiz Capitulino <lcapitulino@redhat.com>, avi@redhat.com

On Tuesday 23 June 2009, Daniel P. Berrange wrote:
> On Tue, Jun 23, 2009 at 01:29:11AM -0300, Luiz Capitulino wrote:
> > It is just an exported function that will be used by other subsystems
> > to print specific events to the output buffer.
>
> As per my mail to the lead message in this thread, I'm thinking it
> might be valuable to include a timestamp with all events, and command
> replies. A 64-bit seconds-since-epoch prefix on all replies, no need
> for a human-format timestamp

I'm reluctant to add timestamps just because they seem like a cool feature.  I 
think it's important to first understand why you want timestamps, and exactly 
where the timestamp comes from. What are you expecting to gain from recording 
the timestamp in qemu rather than the management application?

I'd expect nearest-second timestamps to be pretty much useless for any 
practical purpose.

Also, should the timestamps be real time or virtual time?

Paul