[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] Have xen dom0 still handle time of 1970


  • To: Steven Rostedt <srostedt@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Wed, 17 Jan 2007 16:16:01 +0000
  • Delivery-date: Wed, 17 Jan 2007 08:15:38 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acc6UsdfBjWco6ZGEduIGwAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH] Have xen dom0 still handle time of 1970

On 17/1/07 15:50, "Steven Rostedt" <srostedt@xxxxxxxxxx> wrote:

> Here's what you get without the patch:
> 
> # date -u 010100011970
> Thu Jan  1 00:01:00 UTC 1970
> # date
> Mon Feb 22 16:42:30 EST 2010
> 
> Here's what you get with the patch:
> 
> # date -u 010100011970
> Thu Jan  1 00:01:00 UTC 1970
> # date
> Wed Dec 31 19:01:01 EST 1969

The Xen interface is defined relative to UTC, not local time zone, so
negative numbers shuld not be involved if you are setting a time value after
the epoch (which you are). Perhaps our assumption that xtime is a UTC
variable is broken? If that's the case, is there a way to translate between
local time zone and UTC inside the kernel? If not we have a bit of a problem
since it really makes sense for Xen to work in UTC and let each guest apply
its own time-zone transformation.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.