From: Steven Rostedt <rostedt@goodmis.org>
To: john stultz <johnstul@us.ibm.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, art@usfltd.com
Subject: Re: kernel-2.6.14-rc5-rt7 - 604.62 BogoMIPS (2.6.14-rc5 - 6024.43 BogoMIPS) problem with bogometer ?
Date: Fri, 28 Oct 2005 20:10:32 -0400 [thread overview]
Message-ID: <1130544632.6169.63.camel@localhost.localdomain> (raw)
In-Reply-To: <1130542935.27168.431.camel@cog.beaverton.ibm.com>
On Fri, 2005-10-28 at 16:42 -0700, john stultz wrote:
> On Fri, 2005-10-28 at 18:28 -0500, art wrote:
> > kernel-2.6.14-rc5-rt7 - 604.62 BogoMIPS (2.6.14-rc5 - 6024.43 BogoMIPS) problem with bogometer ?
> >
> > kernel-2.6.14-rc5-rt7 -- Calibrating delay using timer specific routine.. 604.62 BogoMIPS (lpj=302311)
> >
> > kernel-2.6.14-rc5 -- Calibrating delay using timer specific routine.. 6024.43 BogoMIPS (lpj=12048877)
>
> Assuming this is an i386 kernel, in the timeofday patches, the __delay
> function has been converted to be a simple loop based delay instead of
> TSC based, since the TSC has too many potential problems.
>
> That should explain a differing lpj value, although 10x smaller is a
> little strange, so I'll dig into this on my system and see if I find
> anything.
>
> Do let me know if you see any actual changes in behavior (drivers acting
> funny, etc).
John,
Don't waste any time on this. This was caused by a brain fart on
Thomas' part :-) Some legacy code in ktimer_interrupt returned a enum
that was being used to update the ticks. So before high-res was
activated, the jiffies would be incremented 7 times instead of just
once. It's already been fixed. Just waiting for Ingo to release his new
patch.
-- Steve
next prev parent reply other threads:[~2005-10-29 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 23:28 art
2005-10-28 23:42 ` john stultz
2005-10-29 0:10 ` Steven Rostedt [this message]
2005-10-29 0:37 ` Steven Rostedt
2005-10-29 0:47 ` john stultz
2005-10-29 0:05 ` Steven Rostedt
2005-10-30 13:41 ` Ingo Molnar
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=1130544632.6169.63.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=art@usfltd.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®