From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Roman Kagan <rvkagan@yandex-team.ru>,
Markus Armbruster <armbru@redhat.com>,
Denis Plotnikov <den-plotnikov@yandex-team.ru>,
qemu-devel@nongnu.org, yc-core@yandex-team.ru,
michael.roth@amd.com
Subject: Re: [patch v0] qapi/qmp: Add timestamps to qmp command responses.
Date: Wed, 28 Sep 2022 11:31:13 +0100 [thread overview]
Message-ID: <YzQicQM5mGnQwuD8@redhat.com> (raw)
In-Reply-To: <YzQg3R1yYFopabkQ@rvkaganb>
On Wed, Sep 28, 2022 at 04:24:29PM +0600, Roman Kagan wrote:
> On Tue, Sep 27, 2022 at 08:04:11AM +0200, Markus Armbruster wrote:
> > Daniel P. Berrangé <berrange@redhat.com> writes:
> > > On Mon, Sep 26, 2022 at 12:59:40PM +0300, Denis Plotnikov wrote:
> > >> Example of result:
> > >>
> > >> ./qemu/scripts/qmp/qmp-shell /tmp/qmp.socket
> > >>
> > >> (QEMU) query-status
> > >> {"end": {"seconds": 1650367305, "microseconds": 831032},
> > >> "start": {"seconds": 1650367305, "microseconds": 831012},
> > >> "return": {"status": "running", "singlestep": false, "running": true}}
> > >>
> > >> The responce of the qmp command contains the start & end time of
> > >> the qmp command processing.
> >
> > Seconds and microseconds since when? The update to qmp-spec.txt should
> > tell.
> >
> > Why split the time into seconds and microseconds?
>
> This is exactly how timestamps in QMP events are done, so we thought
> we'd just follow suit
Yes, I think its good to have consistency with the rest of the spec,
despite Markus' point that it could be simplified to one field.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2022-09-28 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 9:59 [patch v0] qapi/qmp: Add timestamps to qmp command responses Denis Plotnikov
2022-09-26 13:06 ` Vladimir Sementsov-Ogievskiy
2022-09-26 13:18 ` Daniel P. Berrangé
2022-09-27 6:04 ` Markus Armbruster
2022-09-27 11:59 ` Denis Plotnikov
2022-09-28 10:24 ` Roman Kagan
2022-09-28 10:31 ` Daniel P. Berrangé [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YzQicQM5mGnQwuD8@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=den-plotnikov@yandex-team.ru \
--cc=michael.roth@amd.com \
--cc=qemu-devel@nongnu.org \
--cc=rvkagan@yandex-team.ru \
--cc=yc-core@yandex-team.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.