From: John Stultz <john.stultz@linaro.org>
To: Scot Salmon <scot.salmon@ni.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Detecting shift of CLOCK_REALTIME with clock_nanosleep (again)
Date: Mon, 21 Jan 2013 18:42:41 -0800 [thread overview]
Message-ID: <50FDFCA1.8090703@linaro.org> (raw)
In-Reply-To: <50FD9226.6020206@linaro.org>
On 01/21/2013 11:08 AM, John Stultz wrote:
> On 01/21/2013 07:36 AM, Scot Salmon wrote:
>> As a side note, Richard mentioned that the idea of a CLOCK_TAI has been
>> thrown around before. I agree with him that it would be a useful
>> addition
>> for test & measurement applications.
> Yea, I've had some CLOCK_TAI patches in my tree for awhile now.
> However, its sort of half done, as I need to still integrate CLOCK_TAI
> hrtimer support before it can properly be merged. I've not had the
> time recently to finish this, but I'm hoping to get to it before too
> long (or so I've said for the last few releases).
So I figured I'd spend a few minutes and try to get some progress on this.
My current tree can be found here:
http://git.linaro.org/gitweb?p=people/jstultz/linux.git;a=shortlog;h=refs/heads/fortglx/3.10/time
There's still some issues around notifying the hrtimer when the
tai_offset changes that have to be dealt with, but if folks want to play
around with it, I'd appreciate any feedback.
thanks
-john
next prev parent reply other threads:[~2013-01-22 2:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 15:54 Detecting shift of CLOCK_REALTIME with clock_nanosleep (again) Scot Salmon
2012-10-31 20:08 ` Thomas Gleixner
2012-11-15 19:28 ` Scot Salmon
2012-11-15 20:53 ` John Stultz
2012-11-15 21:01 ` Thomas Gleixner
2012-11-15 22:25 ` John Stultz
2012-11-19 18:27 ` Thomas Gleixner
2012-12-19 20:43 ` Scot Salmon
2012-12-19 20:57 ` John Stultz
2013-01-05 4:09 ` Richard Cochran
2013-01-21 15:36 ` Scot Salmon
2013-01-21 19:08 ` John Stultz
2013-01-22 2:42 ` John Stultz [this message]
2013-01-21 19:12 ` Richard Cochran
2013-01-23 15:14 ` Scot Salmon
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=50FDFCA1.8090703@linaro.org \
--to=john.stultz@linaro.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=scot.salmon@ni.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).