From: David Vrabel <david.vrabel@citrix.com>
To: John Stultz <john.stultz@linaro.org>
Cc: <xen-devel@lists.xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] x86: increase precision of x86_platform.get/set_wallclock()
Date: Wed, 29 May 2013 13:16:38 +0100 [thread overview]
Message-ID: <51A5F1A6.6080204@citrix.com> (raw)
In-Reply-To: <51A54939.10905@linaro.org>
On 29/05/13 01:18, John Stultz wrote:
> On 05/13/2013 10:56 AM, David Vrabel wrote:
>> From: David Vrabel <david.vrabel@citrix.com>
>>
>> All the virtualized platforms (KVM, lguest and Xen) have persistent
>> wallclocks that have more than one second of precision.
>>
>> read_persistent_wallclock() and update_persistent_wallclock() allow
>> for nanosecond precision but their implementation on x86 with
>> x86_platform.get/set_wallclock() only allows for one second precision.
>> This means guests may see a wallclock time that is off by up to 1
>> second.
>>
>> Make set_wallclock() and get_wallclock() take a struct timespec
>> parameter (which allows for nanosecond precision) so KVM and Xen
>> guests may start with a more accurate wallclock time and a Xen dom0
>> can maintain a more accurate wallclock for guests.
>>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
>> ---
>> arch/x86/include/asm/mc146818rtc.h | 4 ++--
>> arch/x86/include/asm/x86_init.h | 6 ++++--
>> arch/x86/kernel/kvmclock.c | 9 +++------
>> arch/x86/kernel/rtc.c | 17 +++++++----------
>> arch/x86/lguest/boot.c | 4 ++--
>> arch/x86/platform/efi/efi.c | 10 ++++++----
>> arch/x86/xen/time.c | 19 ++++++-------------
>> include/linux/efi.h | 4 ++--
>
> Just FYI, David: You missed the vrtc code with this conversion.
>
> I finally got around to pushing my current queue to my public tree and
> the kbuild robot noticed the build failure (required INTEL_MID config to
> trigger).
>
> The fix I've queued is here:
> https://git.linaro.org/gitweb?p=people/jstultz/linux.git;a=commitdiff;h=52d8e9cc6718ae9e6c44b7723028e4717ba91c8b;hp=1dd5234774b33a17743ae62e8b46b5cd0059e1c7
Oops. Sorry about that. That fix looks fine.
David
next prev parent reply other threads:[~2013-05-29 12:16 UTC|newest]
Thread overview: 35+ 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 17:52 ` John Stultz
2013-05-29 0:18 ` John Stultz
2013-05-29 12:16 ` David Vrabel [this message]
2013-05-13 17:56 ` [PATCH 2/3] timekeeping: sync persistent clock and RTC on system time step changes 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 ` [Xen-devel] " Jan Beulich
2013-05-15 18:10 ` John Stultz
2013-05-28 18:26 ` David Vrabel
2013-05-28 18:31 ` Konrad Rzeszutek Wilk
2013-05-28 19:09 ` John Stultz
2013-05-28 19:48 ` Konrad Rzeszutek Wilk
2013-05-28 20:03 ` John Stultz
2013-05-28 20:11 ` John Stultz
2013-05-28 20:25 ` Konrad Rzeszutek Wilk
2013-05-28 20:30 ` John Stultz
2013-05-28 19:06 ` 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 ` [Xen-devel] " Jan Beulich
2013-05-14 15:59 ` John Stultz
2013-05-14 16:14 ` Jan Beulich
2013-05-14 16:17 ` John Stultz
2013-05-14 16:24 ` Konrad Rzeszutek Wilk
2013-05-14 16:28 ` John Stultz
2013-05-14 9:55 ` David Vrabel
2013-05-14 17:24 ` John Stultz
2013-05-14 18:00 ` David Vrabel
2013-05-14 18:03 ` John Stultz
2013-05-15 8:19 ` [Xen-devel] " Jan Beulich
2013-05-15 18:13 ` 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=51A5F1A6.6080204@citrix.com \
--to=david.vrabel@citrix.com \
--cc=john.stultz@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome