[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: Rik van Riel <riel@xxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Wed, 17 Jan 2007 17:44:16 +0000
  • Cc: Steven Rostedt <srostedt@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 17 Jan 2007 09:43:55 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acc6XxtwWfeOkKZSEduIGwAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH] Have xen dom0 still handle time of 1970

On 17/1/07 17:36, "Rik van Riel" <riel@xxxxxxxxxx> wrote:

>> Oh, I see. But it kind of feels silly to work around a synthetic correctness
>> test. If we make wc_sec implicitly signed (which is pretty gross) then we
>> lose 1 bit of magnitude which also isn't great -- I'd rather be able to
>> represent years 2038 through 2106 than 1902 through 1970.
> Isn't unsigned long 64 bits on 64 bit systems anyway?
> That would give us a lot more time...

Yeah it is, but wc_sec in shared_info is uint32_t. Perhaps I wasn't
optimistic enough about Xen's longevity. :-) With tricks we could be good
out to about 2250 without needing to increase wc_sec's size.

 -- Keir

Xen-devel mailing list



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