From: John Stultz <john.stultz@linaro.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: David Vrabel <david.vrabel@citrix.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
Thomas Gleixner <tglx@linutronix.de>,
xen-devel@lists.xen.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH 3/3] x86/xen: sync the CMOS RTC as well as the Xen wallclock
Date: Tue, 14 May 2013 08:59:44 -0700 [thread overview]
Message-ID: <51925F70.5000309@linaro.org> (raw)
In-Reply-To: <51920A9502000078000D5D84@nat28.tlf.novell.com>
On 05/14/2013 12:57 AM, Jan Beulich wrote:
>>>> On 14.05.13 at 02:52, John Stultz <john.stultz@linaro.org> wrote:
>> Honestly, it seems a little strange to me. If you're running as dom0,
>> why does HYPERVISOR_dom0_op() not cause the hypervisor to set the cmos
>> its virtualizing? This seems to mess with the proper virtualization
>> layering.
> Thy hypervisor tries to control as little system and peripheral devices
> as possible, and the CMOS (including the clock) is among those not
> controlled by it, but by Dom0.
Huh. So what does calling HYPERVISOR_dom0_op do then?
Either way, I don't have the context to insightfully review this, so
I'll want this to get some Acked-bys from additional Xen folks before I
queue it.
thanks
-john
next prev parent reply other threads:[~2013-05-14 15:59 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 17:56 [PATCH 0/3] x86,time,xen: maintain an accurate persistent clock in more cases David Vrabel
2013-05-13 17:56 ` [PATCH 1/3] x86: increase precision of x86_platform.get/set_wallclock() David Vrabel
2013-05-14 0:57 ` John Stultz
2013-05-14 0:57 ` John Stultz
2013-05-14 17:52 ` John Stultz
2013-05-14 17:52 ` John Stultz
2013-05-29 0:18 ` John Stultz
2013-05-29 12:16 ` David Vrabel
2013-05-29 12:16 ` David Vrabel
2013-05-29 0:18 ` John Stultz
2013-05-13 17:56 ` David Vrabel
2013-05-13 17:56 ` [PATCH 2/3] timekeeping: sync persistent clock and RTC on system time step changes David Vrabel
2013-05-13 17:56 ` David Vrabel
2013-05-14 0:40 ` John Stultz
2013-05-14 9:47 ` David Vrabel
2013-05-14 17:15 ` John Stultz
2013-05-15 8:16 ` Jan Beulich
2013-05-15 8:16 ` [Xen-devel] " Jan Beulich
2013-05-15 18:10 ` John Stultz
2013-05-15 18:10 ` [Xen-devel] " John Stultz
2013-05-28 18:26 ` David Vrabel
2013-05-28 18:26 ` [Xen-devel] " David Vrabel
2013-05-28 18:31 ` Konrad Rzeszutek Wilk
2013-05-28 19:09 ` John Stultz
2013-05-28 19:09 ` [Xen-devel] " John Stultz
2013-05-28 19:48 ` Konrad Rzeszutek Wilk
2013-05-28 19:48 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-05-28 20:03 ` John Stultz
2013-05-28 20:03 ` [Xen-devel] " John Stultz
2013-05-28 20:11 ` John Stultz
2013-05-28 20:25 ` Konrad Rzeszutek Wilk
2013-05-28 20:25 ` Konrad Rzeszutek Wilk
2013-05-28 20:30 ` [Xen-devel] " John Stultz
2013-05-28 20:30 ` John Stultz
2013-05-28 20:11 ` John Stultz
2013-05-28 18:31 ` Konrad Rzeszutek Wilk
2013-05-28 19:06 ` John Stultz
2013-05-28 19:06 ` [Xen-devel] " John Stultz
2013-05-14 17:15 ` John Stultz
2013-05-14 9:47 ` David Vrabel
2013-05-14 0:40 ` John Stultz
2013-05-13 17:56 ` [PATCH 3/3] x86/xen: sync the CMOS RTC as well as the Xen wallclock David Vrabel
2013-05-14 0:52 ` John Stultz
2013-05-14 7:57 ` Jan Beulich
2013-05-14 7:57 ` [Xen-devel] " Jan Beulich
2013-05-14 15:59 ` John Stultz
2013-05-14 15:59 ` John Stultz [this message]
2013-05-14 16:14 ` [Xen-devel] " Jan Beulich
2013-05-14 16:17 ` John Stultz
2013-05-14 16:24 ` Konrad Rzeszutek Wilk
2013-05-14 16:24 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-05-14 16:28 ` John Stultz
2013-05-14 16:28 ` [Xen-devel] " John Stultz
2013-05-14 16:17 ` John Stultz
2013-05-14 16:14 ` Jan Beulich
2013-05-14 9:55 ` David Vrabel
2013-05-14 9:55 ` David Vrabel
2013-05-14 0:52 ` John Stultz
2013-05-14 17:24 ` John Stultz
2013-05-14 17:24 ` John Stultz
2013-05-14 18:00 ` David Vrabel
2013-05-14 18:00 ` David Vrabel
2013-05-14 18:03 ` John Stultz
2013-05-14 18:03 ` John Stultz
2013-05-15 8:19 ` Jan Beulich
2013-05-15 8:19 ` [Xen-devel] " Jan Beulich
2013-05-15 18:13 ` John Stultz
2013-05-15 18:13 ` John Stultz
2013-05-13 17:56 ` David Vrabel
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=51925F70.5000309@linaro.org \
--to=john.stultz@linaro.org \
--cc=JBeulich@suse.com \
--cc=david.vrabel@citrix.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xen.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 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.