From: Eric Blake <eblake@redhat.com>
To: Lei Li <lilei@linux.vnet.ibm.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 1/3] qga: add support to get host time
Date: Mon, 07 Jan 2013 14:52:46 -0700 [thread overview]
Message-ID: <50EB43AE.5000608@redhat.com> (raw)
In-Reply-To: <1357466820-12860-2-git-send-email-lilei@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]
On 01/06/2013 03:06 AM, Lei Li wrote:
> Signed-off-by: Lei Li <lilei@linux.vnet.ibm.com>
> ---
> qga/commands-posix.c | 18 ++++++++++++++++++
> qga/qapi-schema.json | 17 +++++++++++++++++
> 2 files changed, 35 insertions(+), 0 deletions(-)
>
> diff --git a/qga/commands-posix.c b/qga/commands-posix.c
> index a657201..26b0fa0 100644
> --- a/qga/commands-posix.c
> +++ b/qga/commands-posix.c
> @@ -91,6 +91,24 @@ exit_err:
> error_set(err, QERR_UNDEFINED_ERROR);
> }
>
> +static HostTimeInfo *get_host_time(void)
> +{
> + host_time = g_malloc0(sizeof(HostTimeInfo));
> + host_time->seconds = tq.tv_sec;
> + host_time->microseconds = tq.tv_usec;
Why usec? struct timespec with nanoseconds might be a nicer unit, even
if for the initial implementation, you use
qemu_gettimeofday().tv_usec*1000 rather than dragging in a realtime
library for full ns resolution. If nothing else, the lesson that ought
to be learned from the proliferation of time types is that any time you
don't report lots of precision, someone comes along later on having to
add yet another interface adding more precision.
> +++ b/qga/qapi-schema.json
> @@ -83,6 +83,23 @@
> { 'command': 'guest-ping' }
>
> ##
> +# @HostTimeInfo
> +#
> +# Information about host time.
> +#
> +# @seconds: "seconds" time from the host.
Document that this is relative to the Epoch of 1970-01-01 (no matter
what the host uses for its internal reference point).
> +#
> +# @microseconds: "microseconds" time from the host.
Again, nanoseconds (struct timespec) might be nicer.
> +#
> +# @utc-offset: information about utc offset.
In what format? Minutes away from UTC, a 4-digit decimal value, or
something else (that is, is a one-hour offset represented as 60 or 100)?
Are negative values east or west of UTC?
> +#
> +# Since: 1.4
> +##
> +{ 'type': 'HostTimeInfo',
> + 'data': { 'seconds': 'int', 'microseconds': 'int',
> + 'utc-offset': 'int' } }
Indentation seems inconsistent.
Ah, here you made them mandatory - only your cover letter implied that
they were optional.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2013-01-07 21:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 10:06 [Qemu-devel] [RFC PATCH 0/3] Time resync support by qemu-ga Lei Li
2013-01-06 10:06 ` [Qemu-devel] [PATCH 1/3] qga: add support to get host time Lei Li
2013-01-07 21:52 ` Eric Blake [this message]
2013-01-11 7:18 ` Lei Li
2013-01-11 15:37 ` Eric Blake
2013-01-14 3:17 ` Lei Li
2013-01-14 14:23 ` Eric Blake
2013-01-09 13:32 ` Luiz Capitulino
2013-01-11 7:19 ` Lei Li
2013-01-11 11:14 ` Luiz Capitulino
2013-01-09 15:36 ` mdroth
2013-01-11 7:20 ` Lei Li
2013-01-06 10:06 ` [Qemu-devel] [PATCH 2/3] qga: add guest-get-time command Lei Li
2013-01-07 22:04 ` Eric Blake
2013-01-11 7:37 ` Lei Li
2013-01-11 17:28 ` mdroth
2013-01-09 13:33 ` Luiz Capitulino
2013-01-11 7:50 ` Lei Li
2013-01-06 10:07 ` [Qemu-devel] [PATCH 3/3] qga: add guest-set-time command Lei Li
2013-01-07 22:26 ` Eric Blake
2013-01-11 8:00 ` Lei Li
2013-01-09 13:40 ` Luiz Capitulino
2013-01-11 8:03 ` Lei Li
2013-01-07 19:01 ` [Qemu-devel] [RFC PATCH 0/3] Time resync support by qemu-ga Eric Blake
2013-01-11 7:36 ` Lei Li
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=50EB43AE.5000608@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=lilei@linux.vnet.ibm.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).