From: "Bruce Rogers" <BROGERS@novell.com>
To: xen-devel@lists.xensource.com
Subject: wallclock time for paravirtualized guests
Date: Tue, 28 Mar 2006 10:17:36 -0500 [thread overview]
Message-ID: <4428F0FE.092E.0048.1@novell.com> (raw)
In-Reply-To: 44282079.092E.0048.1@novell.com
[-- Attachment #1.1: Type: text/plain, Size: 811 bytes --]
The paravirtualized guests are offered wallclock time referenced to UTC
only, while fully virtualized guests are given the option via the config
file (localtime parameter) of starting with UTC time or local time.
What would it take to optionally provide localtime to the
paravirtualized guests as well?
For a guest that launches assuming localtime as its time basis, then
later deriving UTC from it based on configuration files, this is
problematic, requiring some convolutions to how it handles time as it
boots.
Is there some place where we can insert a localtime offset into the
start-of-day structure, or perhaps change the sharedinfo wallclock time
to be either localtime or utc, depending on a localtime parameter in the
config file, similar to what is done for fully virtualized guests?
- Bruce Rogers
[-- Attachment #1.2: HTML --]
[-- Type: text/html, Size: 1104 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next parent reply other threads:[~2006-03-28 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4427F3EB.092E.0048.1@novell.com>
[not found] ` <44282079.092E.0048.1@novell.com>
2006-03-28 15:17 ` Bruce Rogers [this message]
2006-03-28 3:40 wallclock time for paravirtualized guests Ian Pratt
2006-03-28 15:28 ` Bruce Rogers
2006-03-28 15:33 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-03-28 2:44 Bruce Rogers
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=4428F0FE.092E.0048.1@novell.com \
--to=brogers@novell.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.