public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: John Stultz <john.stultz@linaro.org>
Cc: David Vrabel <david.vrabel@citrix.com>,
	xen-devel@lists.xen.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/xen: sync the CMOS RTC as well as the Xen wallclock
Date: Tue, 28 May 2013 15:05:30 -0400	[thread overview]
Message-ID: <20130528190530.GA24303@phenom.dumpdata.com> (raw)
In-Reply-To: <51A4FF25.8040908@linaro.org>

On Tue, May 28, 2013 at 12:01:57PM -0700, John Stultz wrote:
> On 05/28/2013 11:22 AM, David Vrabel wrote:
> >From: David Vrabel <david.vrabel@citrix.com>
> >
> >Adjustments to Xen's persistent_clock via update_persistent_clock()
> >don't actually persist, as the xen_set_walltime() just notifies other
> >domN guests that it has been updated, and does not modify the
> >underlying CMOS clock.
> >
> >Thus, this patch modifies xen_set_wallclock() so it will set the
> >underlying CMOS clock when called from dom0, ensuring the
> >persistent_clock will be correct on the next hardware boot.
> >
> >Dom0 does not support accessing EFI runtime services and Xen does not
> >run on Moorsetown platforms so the CMOS RTC is the only supported
> >hardware clock.
> >
> >Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> >Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> 
> Ok, I've queued this for 3.11.

Thanks.
> 
> thanks
> -john
> 

  reply	other threads:[~2013-05-28 19:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 18:22 [PATCHv2 0/2] xen: maintain an accurate persistent clock in more cases David Vrabel
2013-05-28 18:22 ` [PATCH 1/2] x86/xen: sync the CMOS RTC as well as the Xen wallclock David Vrabel
2013-05-28 19:01   ` John Stultz
2013-05-28 19:05     ` Konrad Rzeszutek Wilk [this message]
2013-05-28 18:22 ` [PATCH 2/2] x86/xen: sync the wallclock when the system time changes David Vrabel
2013-05-28 18:53   ` John Stultz
2013-05-29  7:42     ` [Xen-devel] " Jan Beulich
2013-05-29  9:42     ` David Vrabel
2013-06-04  1:22       ` Marcelo Tosatti
2013-05-29  7:39   ` [Xen-devel] " Jan Beulich
2013-05-29  9:48     ` David Vrabel
2013-05-29  7:47   ` Jan Beulich
2013-05-29  9:37     ` David Vrabel
2013-05-29 19:58       ` John Stultz

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=20130528190530.GA24303@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox