qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lei Li <lilei@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 1/2] qga: add guest-get-time command
Date: Mon, 04 Mar 2013 15:39:12 +0800	[thread overview]
Message-ID: <51344FA0.60103@linux.vnet.ibm.com> (raw)
In-Reply-To: <5130DF3F.9080507@redhat.com>

On 03/02/2013 01:02 AM, Eric Blake wrote:
> On 03/01/2013 02:32 AM, Lei Li wrote:
>> Signed-off-by: Lei Li <lilei@linux.vnet.ibm.com>
>> ---
>>   qga/commands-posix.c | 16 ++++++++++++++++
>>   qga/qapi-schema.json | 16 ++++++++++++++++
>>   2 files changed, 32 insertions(+)
>>
>> diff --git a/qga/commands-posix.c b/qga/commands-posix.c
>> index 0ad73f3..f159e25 100644
>> --- a/qga/commands-posix.c
>> +++ b/qga/commands-posix.c
>> @@ -119,6 +119,22 @@ void qmp_guest_shutdown(bool has_mode, const char *mode, Error **err)
>>       /* succeded */
>>   }
>>   
>> +int64_t qmp_guest_get_time(Error **errp)
>> +{
>> +   int ret;
>> +   qemu_timeval tq;
>> +   int64_t time_ns;
>> +
>> +   ret = qemu_gettimeofday(&tq);
>> +   if (ret < 0) {
>> +       error_setg_errno(errp, errno, "Failed to get time");
>> +       return -1;
>> +   }
>> +
>> +   time_ns = tq.tv_sec * 1000000000LL + tq.tv_usec * 1000;
> Is it worth a sanity check that the tv_sec scaling doesn't overflow?  Of
> course, that won't happen until far into the future (well beyond the
> 2038 overflow of 32-bit seconds since Epoch), so it won't hit in OUR
> lifetime, so I can look the other way.
>>   
>>   ##
>> +# @guest-get-time:
>> +#
>> +# Get the information about guest time relative to the Epoch
>> +# of 1970-01-01 in UTC/GMT.
> UTC and GMT are not the same thing.  I'd drop the '/GMT'.
> http://www.diffen.com/difference/GMT_vs_UTC

Oh, good to know! :)
Thanks.

>> +#
>> +# This command try to get the guest's notion of the current
>> +# time.
> This sentence is redundant with the first one, and has grammar issues.
> Drop it.

Sure.

>
>> +#
>> +# Returns: Time in nanoseconds on success.
>> +#
>> +# Since 1.5
>> +##
>> +{ 'command': 'guest-get-time',
>> +  'returns': 'int' }
>> +
>> +##
>>   # @GuestAgentCommandInfo:
>>   #
>>   # Information about guest agent commands.
>>


-- 
Lei

  reply	other threads:[~2013-03-04  7:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01  9:32 [Qemu-devel] [PATCH 0/2 v3] Time resync support by qemu-ga Lei Li
2013-03-01  9:32 ` [Qemu-devel] [PATCH 1/2] qga: add guest-get-time command Lei Li
2013-03-01 17:02   ` Eric Blake
2013-03-04  7:39     ` Lei Li [this message]
2013-03-01  9:33 ` [Qemu-devel] [PATCH 2/2] qga: add guest-set-time command Lei Li
2013-03-01 17:38   ` Eric Blake
2013-03-01 17:50     ` Eric Blake
2013-03-04  8:25     ` Lei Li
  -- strict thread matches above, loose matches on Subject: below --
2013-03-04  9:16 [Qemu-devel] [PATCH 0/2 v4] Time resync support by qemu-ga Lei Li
2013-03-04  9:16 ` [Qemu-devel] [PATCH 1/2] qga: add guest-get-time command Lei Li
2013-03-04 18:04   ` mdroth
2013-03-04 19:02   ` Eric Blake
2013-03-05  9:39 [Qemu-devel] [PATCH 0/2 v5] Time resync support by qemu-ga Lei Li
2013-03-05  9:39 ` [Qemu-devel] [PATCH 1/2] qga: add guest-get-time command 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=51344FA0.60103@linux.vnet.ibm.com \
    --to=lilei@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=eblake@redhat.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).