qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	"Herongguang (Stephen)" <herongguang.he@huawei.com>
Subject: Re: [Qemu-devel] [RFC] Can we convert UTC time to local time in Qemu
Date: Wed, 20 May 2015 21:04:51 -0600	[thread overview]
Message-ID: <555D4B53.1010009@redhat.com> (raw)
In-Reply-To: <555C9DA1.7060204@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 809 bytes --]

On 05/20/2015 08:43 AM, Eric Blake wrote:

> 
> I'd rather stick with UTC in logs (but perhaps make it more obvious that
> the timestamp is UTC by actually sticking that string as part of the
> timestamp - libvirt is not currently doing that).

Actually, here's a libvirt log timestamp:
2015-05-17 02:29:06.931+0000: shutting down

which includes the timezone offset (so while it doesn't state "UTC", it
DOES state an unambiguous timezone, which happens to be UTC).

Compare that to a qemu timestamp:
   (qemu) 2015-05-21T02:07:43.695065Z qemu-system-x86_64: test....

which is ALSO unambiguous (the trailing "Z" _is_ the UTC timezone).
https://en.wikipedia.org/wiki/ISO_8601#UTC

-- 
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: 604 bytes --]

      parent reply	other threads:[~2015-05-21  3:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  6:29 [Qemu-devel] [RFC] Can we convert UTC time to local time in Qemu Gonglei (Arei)
2015-05-20  9:00 ` Daniel P. Berrange
2015-05-20  9:28   ` Gonglei
2015-05-20 14:43 ` Eric Blake
2015-05-21  2:10   ` Gonglei
2015-05-21  3:04   ` Eric Blake [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=555D4B53.1010009@redhat.com \
    --to=eblake@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=herongguang.he@huawei.com \
    --cc=peter.huangpeng@huawei.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).