From: John Stultz <john.stultz@linaro.org>
To: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xen.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] x86/xen: sync the wallclock when the system time changes
Date: Tue, 28 May 2013 11:53:59 -0700 [thread overview]
Message-ID: <51A4FD47.2030301@linaro.org> (raw)
In-Reply-To: <1369765368-10823-3-git-send-email-david.vrabel@citrix.com>
On 05/28/2013 11:22 AM, David Vrabel wrote:
> From: David Vrabel <david.vrabel@citrix.com>
>
> Currently the Xen wallclock is only updated every 11 minutes if NTP is
> synchronized to its clock source. If a guest is started before NTP is
> synchronized it may see an incorrect wallclock time.
>
> Use the pvclock_gtod notifier chain to receive a notification when the
> system time has changed and update the wallclock to match.
>
> This chain is called on every timer tick and we want to avoid an extra
> (expensive) hypercall on every tick. Because dom0 has historically
> never provided a very accurate wallclock and guests do not expect one,
> we can do this simply. The wallclock is only updated if the
> difference between now and the last update is more than 0.5 s.
>
> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> ---
> arch/x86/xen/time.c | 54 ++++++++++++++++++++++++++++++++++++++++++--------
> 1 files changed, 45 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
> index 4656165..81027b5 100644
> --- a/arch/x86/xen/time.c
> +++ b/arch/x86/xen/time.c
> @@ -15,6 +15,8 @@
> #include <linux/math64.h>
> #include <linux/gfp.h>
> #include <linux/mc146818rtc.h>
> +#include <linux/timekeeper_internal.h>
Nope. You shouldn't be including this.
> +#include <linux/pvclock_gtod.h>
>
> #include <asm/pvclock.h>
> #include <asm/xen/hypervisor.h>
> @@ -199,28 +201,59 @@ static void xen_get_wallclock(struct timespec *now)
>
> static int xen_set_wallclock(const struct timespec *now)
> {
> - struct xen_platform_op op;
> - int ret;
> -
> /* do nothing for domU */
> if (!xen_initial_domain())
> return -1;
>
> - /* Set the Xen wallclock. */
> + /* Set the hardware RTC. */
> + return mach_set_rtc_mmss(now);
> +
> +}
> +
> +static int xen_pvclock_gtod_notify(struct notifier_block *nb, unsigned long unused,
> + void *priv)
> +{
> + static struct timespec last, next;
> + struct timespec now;
> + struct timekeeper *tk = priv;
Noooo.. don't export the timekeeper like that.
> + struct xen_platform_op op;
> + int ret;
> +
> + /*
> + * Set the Xen wallclock from Linux system time.
> + *
> + * dom0 hasn't historically maintained a very accurate
> + * wallclock so guests don't expect it. We can therefore
> + * reduce the number of expensive hypercalls by only updating
> + * the wallclock every 0.5 s.
> + */
> +
> + now.tv_sec = tk->xtime_sec;
> + now.tv_nsec = tk->xtime_nsec >> tk->shift;
You probably want current_kernel_time() here.
> +
> + if (timespec_compare(&now, &last) > 0
> + && timespec_compare(&now, &next) < 0)
> + return 0;
> +
> op.cmd = XENPF_settime;
> - op.u.settime.secs = now->tv_sec;
> - op.u.settime.nsecs = now->tv_nsec;
> + op.u.settime.secs = now.tv_sec;
> + op.u.settime.nsecs = now.tv_nsec;
> op.u.settime.system_time = xen_clocksource_read();
>
> ret = HYPERVISOR_dom0_op(&op);
> if (ret)
> - return ret;
> + return 0;
>
> - /* Set the hardware RTC. */
> - return mach_set_rtc_mmss(now);
> + last = now;
> + next = timespec_add(now, ns_to_timespec(NSEC_PER_SEC / 2));
>
Am I missing the xen_set_wallclock hook here? Your previous patch wanted
to call the dom0 op and then set the hardware RTC.
And this notifier get called every timer tick? This seems out there...
thanks
-john
next prev parent reply other threads:[~2013-05-28 18:54 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
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 [this message]
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=51A4FD47.2030301@linaro.org \
--to=john.stultz@linaro.org \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--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