From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] [PVOPS] dom0 sync xen wallclock
Date: Fri, 19 Feb 2010 15:05:04 -0800 [thread overview]
Message-ID: <4B7F1920.2060908@goop.org> (raw)
In-Reply-To: <1266570650.10261.6998.camel@zakaz.uk.xensource.com>
On 02/19/2010 01:10 AM, Ian Campbell wrote:
> Unfortunately there is an existing large installed base of guests which
> use the dependent wallclock mode since it is the default in oldstyle Xen
> kernels.
>
Sure. I'm not suggesting that we remove the existing hypercall. I just
don't think we should extend it or encourage its use.
>> * HVM domains similarly get an emulated CMOS implemented in qemu
>>
> Isn't this currently emulated within the hypervisor using the wallclock
> time within Xen? I assume that it was pulled into the h/v for a specific
> reason? I'm not sure what reason though, the emulated RTC doesn't seem
> especially performance critical...
>
It is? I wonder why we bothered adding a pvop for it then...
J
next prev parent reply other threads:[~2010-02-19 23:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 18:12 [PATCH] [PVOPS] dom0 sync xen wallclock Stefano Stabellini
2010-02-09 18:20 ` Stefano Stabellini
2010-02-10 23:09 ` Jeremy Fitzhardinge
2010-02-11 0:06 ` Keir Fraser
2010-02-11 0:47 ` Jeremy Fitzhardinge
2010-02-11 8:03 ` Keir Fraser
2010-02-11 19:16 ` Jeremy Fitzhardinge
2010-02-11 11:24 ` Stefano Stabellini
2010-02-11 11:36 ` Ian Campbell
2010-02-18 23:43 ` Jeremy Fitzhardinge
2010-02-19 1:02 ` Dan Magenheimer
2010-02-19 9:10 ` Ian Campbell
2010-02-19 9:39 ` Keir Fraser
2010-02-23 12:13 ` Stefano Stabellini
2010-02-23 14:25 ` Ian Campbell
2010-02-19 23:05 ` Jeremy Fitzhardinge [this message]
2010-02-23 14:25 ` Ian Campbell
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=4B7F1920.2060908@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.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.