From: john stultz <johnstul@us.ibm.com>
To: Thomas Schlichter <thomas.schlichter@web.de>
Cc: Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.6.2-rc1-mm2
Date: Fri, 23 Jan 2004 09:59:28 -0800 [thread overview]
Message-ID: <1074880768.12442.22.camel@localhost> (raw)
In-Reply-To: <200401231430.35014.thomas.schlichter@web.de>
On Fri, 2004-01-23 at 05:30, Thomas Schlichter wrote:
> Hi,
>
> Am Freitag, 23. Januar 2004 10:37 schrieb Andrew Morton:
> > +use-pmtmr-for-delay_pmtmr.patch
> >
> > Fix a boot-time crash which occurs when testing the APIC timer when using
> > the ACPI PM timer. This causes bogomips to be reported at 50% of what it
> > used to be.
>
> I don't know which Oops this fixes, but with this patch my bogomips value is
> 8.19 (!!!) instead of ~1300. With clock=pit I get about 1300 bogomips, and
> with clock=tsc I get about 2600 bogomips. The CPU is a 1300MHz AMD Duron.
I know it feels like a kick in the pants when your BogoMIPS drops to
leves not seen since the 80s, but the value you are getting is expected.
Since the patch above uses the pmtmr for __delay(), loops_per_jiffies is
then calibrated to the ACPI PM timer's frequency instead of aproximately
the cpu's freq.
This was necessary, because on some systems calibrate_dealy()
incorrectly calibrates delays. Your system shows this, but its your
cycle based delay (clock=tsc) which is overestimated, so you see no
problem. The case Andrew describes above is when the loop based delay
(clock=pit or clock=pmtmr w/o this patch) is under estimated causing
problems when we initialize the APIC timer.
Additionally, since we're no longer dependent on the cpu speed,
speedstep like changes to the cpu freqency no longer affects time.
thanks
-john
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-01-23 17:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 9:37 2.6.2-rc1-mm2 Andrew Morton
2004-01-23 13:30 ` 2.6.2-rc1-mm2 Thomas Schlichter
2004-01-23 17:59 ` john stultz [this message]
2004-01-23 15:12 ` 2.6.2-rc1-mm2 Ed Tomlinson
2004-01-23 18:43 ` 2.6.2-rc1-mm2 Andrew Morton
2004-01-24 0:46 ` 2.6.2-rc1-mm2 Ed Tomlinson
2004-01-23 16:01 ` keyboard and USB problems (Re: 2.6.2-rc1-mm2) Rudo Thomas
2004-01-23 16:19 ` Vojtech Pavlik
2004-01-23 18:46 ` Andrew Morton
2004-01-23 22:16 ` More timer/bogomip damage (was " Valdis.Kletnieks
2004-01-23 19:27 ` john stultz
2004-01-23 19:54 ` Vojtech Pavlik
2004-01-23 20:15 ` john stultz
2004-01-23 21:10 ` Vojtech Pavlik
2004-01-24 0:26 ` [PATCH] use-tsc-for-delay_pmtmr.patch john stultz
2004-01-23 17:08 ` 2.6.2-rc1-mm2 (compile stats) John Cherry
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=1074880768.12442.22.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=thomas.schlichter@web.de \
/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