From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Anton Blanchard <anton@samba.org>
Cc: Andrew Morton <akpm@osdl.org>, Paul Mackerras <paulus@samba.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ppc64: xtime <-> gettimeofday can get out of sync
Date: Thu, 13 Jan 2005 14:40:55 +1100 [thread overview]
Message-ID: <1105587656.27435.10.camel@gaston> (raw)
In-Reply-To: <20050110132429.GS14239@krispykreme.ozlabs.ibm.com>
> Note that the time_sync_xtime check only stops the seconds from going
> backwards, the ns component still could couldnt it? Considering this
> is hard to get right, should we switch to the time interpolator stuff?
> The only problem there is it might be trouble for systemcfg (which
> exports stuff to do userspace gettimeofday).
My userland implementation in the vDSO also relies on our current
algorithm. It's not merged yet and could be changed of course, but I
ended up quite liking our current code ;)
The interesting thing with it is we are basically lock-less
(and even barrier-less on reads).
Ben.
prev parent reply other threads:[~2005-01-13 3:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 13:24 Anton Blanchard
2005-01-13 3:40 ` Benjamin Herrenschmidt [this message]
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=1105587656.27435.10.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®