From: Csdncannon <csdncannon@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Continual reading from the PowerPc time base register is not stable
Date: Thu, 25 Mar 2010 23:00:54 +0800 [thread overview]
Message-ID: <43c137a81003250800n660195c5k42c8516068aeda8d@mail.gmail.com> (raw)
In-Reply-To: <201003251105.10033.arnd@arndb.de>
[-- Attachment #1.1: Type: text/plain, Size: 1832 bytes --]
I am really sorry that the previously attached code is wrong, this one
"timebase.c" is the right one, and the "log_timebase" file is the right log.
We are using FreeScale PowerPc 8378, kernel 2.6.28 and compiled as 32-bit.
Thanks
Gino
2010/3/25 Arnd Bergmann <arnd@arndb.de>
> On Thursday 25 March 2010, Benjamin Herrenschmidt wrote:
> > On Thu, 2010-03-25 at 10:41 +0800, Csdncannon wrote:
> > > 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.
> >
> > This is a concern, it should definitely not happen. What machine is
> > that ? is the code compiled 32-bit or 64-bit ? What kernel version ?
> >
> > Arnd, any chance that could relate to the bug you've been chasing on
> > Cell ?
>
> We're still busy with the problem analysis on Cell, waiting for a time
> slot to run the next test kernel. So far it seems like the timebase
> is actually synchronized at a significant accuracy on QS22 to never
> cause this problem with correct code, however it is possible to
> observe incorrect timebase values on Cell whenever the mftb instruction
> is not serialized with memory accesses, e.g. by using an isync in front
> of the mftb. On Power6 and other CPUs, that problem will not happen.
>
> Arnd
>
[-- Attachment #1.2: Type: text/html, Size: 2319 bytes --]
[-- Attachment #2: timebase.c --]
[-- Type: application/octet-stream, Size: 1604 bytes --]
/* TSC sync test
* by: john stultz (johnstul@us.ibm.com)
* (C) Copyright IBM 2003, 2005
* Licensed under the GPL
*/
#include <stdio.h>
#include <sys/time.h>
#include <stdlib.h>
#define CALLS_PER_LOOP 64
volatile unsigned long long getTimeBase()
{
unsigned long upper,lower,upper2;
do {
asm volatile("sync; isync":::"memory");
asm volatile("mftbu %0" : "=r" (upper));
asm volatile("sync; isync":::"memory");
asm volatile("mftbl %0" : "=r" (lower));
asm volatile("sync; isync":::"memory");
asm volatile("mftbu %0" : "=r" (upper2));
asm volatile("sync; isync":::"memory");
}while(upper2!=upper);
return (upper<<32)|lower;
}
int main(int argc, char *argv[])
{
volatile unsigned long long list[CALLS_PER_LOOP];
bool bad[CALLS_PER_LOOP];
int i, inconsistent;
/* timestamp start of test */
system("date");
while(1){
inconsistent = 0;
/* Fill list */
for(i=0; i < CALLS_PER_LOOP; i++)
list[i] = getTimeBase();
/* Check for inconsistencies */
for(i=0; i < CALLS_PER_LOOP-1; i++)
{
if(list[i] > list[i+1])
{
inconsistent = i+1;
bad[i] = true;
}
else{
bad[i] = false;
}
}
/* display inconsistency */
if(inconsistent){
inconsistent--;
for(i=0; i < CALLS_PER_LOOP; i++){
if(bad[i] == true)
printf("--------------------\n");
printf("0x%llx\n",list[i]);
if(bad[i-1] == true && bad[i] == false )
printf("--------------------\n");
}
fflush(0);
/* timestamp inconsistency*/
system("date");
}
}
return 0;
}
next prev parent reply other threads:[~2010-03-25 15:00 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 [this message]
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
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=43c137a81003250800n660195c5k42c8516068aeda8d@mail.gmail.com \
--to=csdncannon@gmail.com \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).