From: Michal Privoznik <mprivozn@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2] qga: Don't require 'time' argument in guest-set-time command
Date: Thu, 13 Feb 2014 18:33:55 +0100 [thread overview]
Message-ID: <52FD0203.3010500@redhat.com> (raw)
In-Reply-To: <52EBE77E.2080507@redhat.com>
On 31.01.2014 19:12, Eric Blake wrote:
> On 01/31/2014 03:29 AM, Michal Privoznik wrote:
>> As the description to the guest-set-time states, the command is
>> there to ease time synchronization after resume. If guest was
>> suspended for longer period of time, its system time can go off
>> so badly, that even NTP refuses to set it. That's why the command
>> was invented: to give users chance to set the time (not
>> necessarily 100% correct). However, there's is no real need for
>> us to require users to pass an arbitrary time. Especially if we
>> can read the correct value from RTC (boiling down to reading
>> host's time). Hence this commit enables logic:
>>
>> guest-set-time() == guest-set-time($now_from_rtc)
>>
>> Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
>> ---
>> diff to v1:
>> -Fix checkpatch.pl warnings
>>
>> qga/commands-posix.c | 41 +++++++++++++++++++++++++----------------
>> qga/commands-win32.c | 34 +++++++++++++++++++++++-----------
>> qga/qapi-schema.json | 9 +++++----
>> 3 files changed, 53 insertions(+), 31 deletions(-)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
May I kindly ask somebody to merge this? Or is 3ACKs required for the
guest agent too? Thanks in advance!
Michal
next prev parent reply other threads:[~2014-02-13 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 10:29 [Qemu-devel] [PATCH v2] qga: Don't require 'time' argument in guest-set-time command Michal Privoznik
2014-01-31 18:12 ` Eric Blake
2014-02-13 17:33 ` Michal Privoznik [this message]
2014-02-24 1:00 ` Michael Roth
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=52FD0203.3010500@redhat.com \
--to=mprivozn@redhat.com \
--cc=eblake@redhat.com \
--cc=lersek@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mtosatti@redhat.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).