From: Kim Phillips <kim.phillips@freescale.com>
To: Csdncannon <csdncannon@gmail.com>
Cc: linuxppc-dev@ozlabs.org, zhouminggang@hotmail.com
Subject: Re: Continual reading from the PowerPc time base register is not stable
Date: Wed, 21 Apr 2010 19:44:19 -0500 [thread overview]
Message-ID: <20100421194419.3edf2c80.kim.phillips@freescale.com> (raw)
In-Reply-To: <o2y43c137a81004092014z1511cecdxb7154825dc07b49f@mail.gmail.com>
On Sat, 10 Apr 2010 11:14:09 +0800
Csdncannon <csdncannon@gmail.com> wrote:
> Sorry, I attached the wrong log, this attachment is the right one.
>
> 2010/3/25 Csdncannon <csdncannon@gmail.com>
>
> > In my program, the value of the 64-bit time base register is read
> > out, and you will find the later value is even smaller than the earlier
> > value from the log “log_timebase”. While the kernel depends on the accuracy
> > of the timebase for the compensation of the lost PIT interrupt, the negative
> > value between two continual timebase reading will bring to the jump of the
> > jiffies. And this timebase problem will bring to the instability of the
> > gettimeofday system call.
> >
> > Do you have any idea about this problem, thanks for your any
> > advice. Attached is the code and log.
Hi, has this been resolved yet?
I took an 8377 rdb board, and let it run timebase.c (with the isync &
long long casts) all weekend, and have failed to reproduce the issue.
That was on linux 2.6.33, and I've got another machine running the same
thing under 2.6.28 for the last couple of hours, still unable to
reproduce the issue.
Can you please answer the "custom board or FSL reference board"
question, try duplicating with a newer kernel version, discuss other
time sources that may be running on your system (RTC_DRV, ntp service),
post a .config, ...
Kim
next prev parent reply other threads:[~2010-04-22 0:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 2:41 Continual reading from the PowerPc time base register is not stable Csdncannon
2010-03-25 8:21 ` Benjamin Herrenschmidt
2010-03-25 10:05 ` Arnd Bergmann
2010-03-25 15:00 ` Csdncannon
2010-03-25 20:38 ` Benjamin Herrenschmidt
2010-03-26 1:11 ` Csdncannon
2010-03-26 1:22 ` Segher Boessenkool
2010-03-26 2:01 ` Csdncannon
2010-03-26 8:52 ` Segher Boessenkool
2010-03-26 9:01 ` Segher Boessenkool
2010-03-26 12:14 ` Csdncannon
2010-04-06 8:02 ` Csdncannon
2010-03-26 1:55 ` Benjamin Herrenschmidt
2010-03-26 2:04 ` Csdncannon
2010-03-25 22:00 ` Chris Friesen
2010-03-25 22:57 ` Benjamin Herrenschmidt
2010-03-25 23:37 ` Kumar Gala
2010-03-25 21:37 ` Segher Boessenkool
2010-04-10 3:14 ` Csdncannon
2010-04-22 0:44 ` Kim Phillips [this message]
2010-04-22 0:50 ` Benjamin Herrenschmidt
2010-04-22 23:27 ` Kim Phillips
2010-04-23 10:57 ` Csdncannon
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=20100421194419.3edf2c80.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=csdncannon@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=zhouminggang@hotmail.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 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).