Re: [PATCH RFC 0/3] Improve stability of system clock

2017-06-08 Thread John Stultz
On Thu, Jun 8, 2017 at 9:17 AM, Miroslav Lichvar wrote: > On Fri, May 19, 2017 at 05:35:38PM -0700, John Stultz wrote: >> >> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar >> >> wrote: >> >> > Is there a better way to run the timekeeping code in an

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-06-08 Thread John Stultz
On Thu, Jun 8, 2017 at 9:17 AM, Miroslav Lichvar wrote: > On Fri, May 19, 2017 at 05:35:38PM -0700, John Stultz wrote: >> >> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar >> >> wrote: >> >> > Is there a better way to run the timekeeping code in an userspace >> >> > application? I suspect

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-06-08 Thread Miroslav Lichvar
On Fri, May 19, 2017 at 05:35:38PM -0700, John Stultz wrote: > >> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar > >> wrote: > >> > Is there a better way to run the timekeeping code in an userspace > >> > application? I suspect it would need something like the Linux

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-06-08 Thread Miroslav Lichvar
On Fri, May 19, 2017 at 05:35:38PM -0700, John Stultz wrote: > >> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar > >> wrote: > >> > Is there a better way to run the timekeeping code in an userspace > >> > application? I suspect it would need something like the Linux Kernel > >> > Library

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-21 Thread Rusty Russell
John Stultz writes: > On Wed, May 17, 2017 at 9:54 PM, Richard Cochran > wrote: >> On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote: >>> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar >>> wrote: >>> > Is

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-21 Thread Rusty Russell
John Stultz writes: > On Wed, May 17, 2017 at 9:54 PM, Richard Cochran > wrote: >> On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote: >>> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar >>> wrote: >>> > Is there a better way to run the timekeeping code in an userspace >>> >

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-19 Thread John Stultz
On Wed, May 17, 2017 at 9:54 PM, Richard Cochran wrote: > On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote: >> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar >> wrote: >> > Is there a better way to run the timekeeping code in an

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-19 Thread John Stultz
On Wed, May 17, 2017 at 9:54 PM, Richard Cochran wrote: > On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote: >> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar >> wrote: >> > Is there a better way to run the timekeeping code in an userspace >> > application? I suspect it would need

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread Richard Cochran
On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote: > On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar > wrote: > > Is there a better way to run the timekeeping code in an userspace > > application? I suspect it would need something like the Linux Kernel > >

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread Richard Cochran
On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote: > On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar > wrote: > > Is there a better way to run the timekeeping code in an userspace > > application? I suspect it would need something like the Linux Kernel > > Library project. > > I

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread John Stultz
On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar wrote: > On Wed, May 17, 2017 at 10:02:00AM -0700, John Stultz wrote: >> On Wed, May 17, 2017 at 9:57 AM, Miroslav Lichvar >> wrote: >> > On Wed, May 17, 2017 at 09:30:31AM -0700, John Stultz wrote: >>

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread John Stultz
On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar wrote: > On Wed, May 17, 2017 at 10:02:00AM -0700, John Stultz wrote: >> On Wed, May 17, 2017 at 9:57 AM, Miroslav Lichvar >> wrote: >> > On Wed, May 17, 2017 at 09:30:31AM -0700, John Stultz wrote: >> >> Could you submit your linux-tktest

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread Miroslav Lichvar
On Wed, May 17, 2017 at 10:02:00AM -0700, John Stultz wrote: > On Wed, May 17, 2017 at 9:57 AM, Miroslav Lichvar wrote: > > On Wed, May 17, 2017 at 09:30:31AM -0700, John Stultz wrote: > >> Could you submit your linux-tktest infrastructure to the kselftests dir? > > > > I

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread Miroslav Lichvar
On Wed, May 17, 2017 at 10:02:00AM -0700, John Stultz wrote: > On Wed, May 17, 2017 at 9:57 AM, Miroslav Lichvar wrote: > > On Wed, May 17, 2017 at 09:30:31AM -0700, John Stultz wrote: > >> Could you submit your linux-tktest infrastructure to the kselftests dir? > > > > I can, but it's a mess

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread John Stultz
On Wed, May 17, 2017 at 9:57 AM, Miroslav Lichvar wrote: > On Wed, May 17, 2017 at 09:30:31AM -0700, John Stultz wrote: >> So thanks for sending these out. I still need to look them over in >> depth, but can I make another ask here? :) >> >> Could you submit your

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread John Stultz
On Wed, May 17, 2017 at 9:57 AM, Miroslav Lichvar wrote: > On Wed, May 17, 2017 at 09:30:31AM -0700, John Stultz wrote: >> So thanks for sending these out. I still need to look them over in >> depth, but can I make another ask here? :) >> >> Could you submit your linux-tktest infrastructure to

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread Miroslav Lichvar
On Wed, May 17, 2017 at 09:30:31AM -0700, John Stultz wrote: > So thanks for sending these out. I still need to look them over in > depth, but can I make another ask here? :) > > Could you submit your linux-tktest infrastructure to the kselftests dir? I can, but it's a mess that breaks

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread Miroslav Lichvar
On Wed, May 17, 2017 at 09:30:31AM -0700, John Stultz wrote: > So thanks for sending these out. I still need to look them over in > depth, but can I make another ask here? :) > > Could you submit your linux-tktest infrastructure to the kselftests dir? I can, but it's a mess that breaks

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread John Stultz
On Wed, May 17, 2017 at 9:13 AM, Miroslav Lichvar wrote: > This is an attempt to improve stability and accuracy of the system clock > with very accurate time sources like the new PTP KVM clock or NTP/PTP > using hardware timestamping. It affects mainly kernels running with >

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread John Stultz
On Wed, May 17, 2017 at 9:13 AM, Miroslav Lichvar wrote: > This is an attempt to improve stability and accuracy of the system clock > with very accurate time sources like the new PTP KVM clock or NTP/PTP > using hardware timestamping. It affects mainly kernels running with > NOHZ. It requires

[PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread Miroslav Lichvar
This is an attempt to improve stability and accuracy of the system clock with very accurate time sources like the new PTP KVM clock or NTP/PTP using hardware timestamping. It affects mainly kernels running with NOHZ. It requires updating of the old ia64 and powerpc vsyscalls. The main problem is

[PATCH RFC 0/3] Improve stability of system clock

2017-05-17 Thread Miroslav Lichvar
This is an attempt to improve stability and accuracy of the system clock with very accurate time sources like the new PTP KVM clock or NTP/PTP using hardware timestamping. It affects mainly kernels running with NOHZ. It requires updating of the old ia64 and powerpc vsyscalls. The main problem is