[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Re: [PATCH 06/11] QMP: Introduce asynchronous events in
Re: [Qemu-devel] Re: [PATCH 06/11] QMP: Introduce asynchronous events infrastructure
Tue, 23 Jun 2009 15:46:27 +0100
KMail/1.11.4 (Linux/2.6.29-2-amd64; KDE/4.2.4; x86_64; ; )
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
Also, should the timestamps be real time or virtual time?