From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Daniel Walker <dwalker@mvista.com>
Cc: mbligh@google.com, linux-kernel@vger.kernel.org, johnstul@us.ibm.com
Subject: Re: [RFC] Fast assurate clock readable from user space and NMI handler
Date: Mon, 26 Feb 2007 15:53:05 -0500 [thread overview]
Message-ID: <20070226205304.GA30800@Krystal> (raw)
In-Reply-To: <1172340369.24216.31.camel@imap.mvista.com>
* Daniel Walker (dwalker@mvista.com) wrote:
> On Sat, 2007-02-24 at 11:19 -0500, Mathieu Desnoyers wrote:
> > Hi,
> >
> > I am trying to improve the Linux kernel time source so it can be read
> > without seqlock from NMI handlers. I have also seen some interest for
> > such an accurate monotonic clock readable from user space. It mainly
> > implies an atomic update of the time value. I am also trying to figure a
> > way to support architectures with multiple CPUs with non-synchronized
> > TSCs.
> >
> > I would like to have your comments on the following idea.
> >
> > Thanks in advance,
> >
> > Mathieu
> >
> >
> > Monotonic accurate time
> >
> > The goal of this design is to provide a monotonic time :
> >
> > Readable from userspace without a system call
> > Readable from NMI handler
> > Readable without disabling interrupts
> > Readable without disabling preemption
> > Only one clock source (most precise available : tsc)
> > Support architectures with variable TSC frequency.
>
> I don't think you could use only the tsc. From reviewing John, and
> Thomas work it's pretty clear the TSC isn't going to work correctly all
> the time.
>
Ok, if there are other high precision timers we can use, I guess it may
be better to fall back on them.
> > /* On frequency change event */
> > /* In irq context */
> > void freq_change_cb(unsigned int new_freq)
> > {
>
> It's possible for the TSC to change frequencies without notification. It
> can also completely stop when the system goes idle.
>
Hrm, I see. I though those freq change without notification would happen
rarely and could be dealt by resynchronizing the CPUs. I guess I was
wrong.
> > /* Userspace */
> > /* Export all this data to user space through the vsyscall page. Use a function
> > * like read_time to read the walltime. This function can be implemented as-is
> > * because it doesn't need to disable preemption. */
>
> What would be the benefit of using this over the vsyscall gettimeofday()
> from userspace ?
>
So we can get a monotonic, non NTP corrected timestamp quickly from user
space without going through a system call. Are there other alternatives ?
Thanks,
Mathieu
--
Mathieu Desnoyers
Computer Engineering Ph.D. Candidate, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2007-02-26 20:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 21:59 [PATCH 8/16] LTTng 0.6.36 for 2.6.18 : Timestamp Mathieu Desnoyers
[not found] ` <1164475747.5196.5.camel@localhost.localdomain>
[not found] ` <20061126170542.GA30771@Krystal>
[not found] ` <1164561427.16871.14.camel@localhost.localdomain>
[not found] ` <20061126231833.GA22241@Krystal>
[not found] ` <1164585589.16871.52.camel@localhost.localdomain>
2007-02-24 16:19 ` [RFC] Fast assurate clock readable from user space and NMI handler Mathieu Desnoyers
2007-02-24 18:06 ` Daniel Walker
2007-02-26 20:53 ` Mathieu Desnoyers [this message]
2007-02-26 21:27 ` Daniel Walker
2007-02-26 22:14 ` Mathieu Desnoyers
2007-02-26 23:12 ` Daniel Walker
2007-02-27 3:54 ` Mathieu Desnoyers
2007-02-27 4:22 ` Daniel Walker
2007-02-27 4:47 ` Mathieu Desnoyers
2007-02-27 6:29 ` Ingo Molnar
2007-02-27 7:38 ` Mathieu Desnoyers
2007-02-27 8:48 ` Thomas Gleixner
2007-02-27 10:18 ` Daniel Walker
2007-02-27 16:02 ` Mathieu Desnoyers
2007-02-27 17:24 ` Daniel Walker
2007-02-27 19:04 ` Mathieu Desnoyers
2007-02-27 19:40 ` john stultz
2007-02-27 20:09 ` Daniel Walker
2007-02-27 9:59 ` Daniel Walker
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=20070226205304.GA30800@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=dwalker@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.