From: Pasi Savolainen <pasi.savolainen@hut.fi>
To: Tony Lindgren <tony@atomide.com>
Cc: john stultz <johnstul@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
clepple@ghz.cc
Subject: Re: [PATCH] amd76x_pm on 2.6.0-test9 cleanup
Date: Fri, 14 Nov 2003 13:56:58 +0200 [thread overview]
Message-ID: <20031114115658.GD479040@kosh.hut.fi> (raw)
In-Reply-To: <20031104205547.GE1042@atomide.com>
* Tony Lindgren <tony@atomide.com> [031104 23:00]:
> * Pasi Savolainen <pasi.savolainen@hut.fi> [031104 12:21]:
> > * Tony Lindgren <tony@atomide.com> [031104 21:24]:
> > > * john stultz <johnstul@us.ibm.com> [031104 10:43]:
> > > > On Mon, 2003-11-03 at 16:22, Tony Lindgren wrote:
> > > > I've received some reports that this patch causes time problems.
> > > >
> > > > Have those issues been looked into further, or addressed?
> > >
> > > I've heard of timing problems if it's compiled in, but supposedly they don't
> > > happen when loaded as module.
> >
> > Not happening since 2.6.0-test9. Don't know what really fixed it, but
> > they're just not there anymore.
>
> Weird, John, is this true on your S2460 also?
Well I'll be damned. It took 18 days to show up. Though I've been
riding this baby heavy for about a week.
So I've gettimeofday() jumping backwards again.
# uname -a
Linux tienel 2.6.0-test9 #2 SMP Sun Oct 26 14:35:02 EET 2003 i686 GNU/Linux
It's this test I'm running (snipped from previous TSC desych
-conversation):
- -
#include <stdio.h>
#include <sys/types.h>
#include <sys/time.h>
int main( void )
{
int i = 0;
while( 1 )
{
struct timeval start;
struct timeval stop;
struct timeval diff;
int rc1;
int rc2;
if( i++ % 1000000 == 0 )
printf( "% 12d: Iterations so far\n", i );
rc1 = gettimeofday( &start, 0 );
rc2 = gettimeofday( &stop, 0 );
timersub( &stop, &start, &diff );
if( rc1 < 0 || rc2 < 0 )
printf( " %12d: rc1=%d rc2=%d. Failure!\n",
i,
rc1,
rc2
);
if( diff.tv_sec >= 0 && diff.tv_usec >= 0 )
continue;
printf( "% 12d: Time went backwards: %d:%06d\n",
i,
diff.tv_sec,
diff.tv_usec
);
}
}
- -
--
Psi -- <http://www.iki.fi/pasi.savolainen>
next prev parent reply other threads:[~2003-11-14 11:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 0:22 [PATCH] amd76x_pm on 2.6.0-test9 cleanup Tony Lindgren
2003-11-04 18:41 ` john stultz
2003-11-04 19:15 ` Tony Lindgren
2003-11-04 19:44 ` Charles Lepple
2003-11-04 20:05 ` Tony Lindgren
2003-11-04 20:52 ` Charles Lepple
2003-11-04 22:38 ` Charles Lepple
2003-11-04 23:11 ` Tony Lindgren
2003-11-04 23:46 ` Pasi Savolainen
2003-11-04 20:21 ` Pasi Savolainen
2003-11-04 20:55 ` Tony Lindgren
2003-11-04 20:57 ` john stultz
2003-11-04 21:14 ` Tony Lindgren
2003-11-14 11:56 ` Pasi Savolainen [this message]
2003-11-04 21:01 ` Charles Lepple
2003-11-04 21:17 ` Tony Lindgren
2003-11-05 19:42 ` Felix Maibaum
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=20031114115658.GD479040@kosh.hut.fi \
--to=pasi.savolainen@hut.fi \
--cc=clepple@ghz.cc \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.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).