[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <476294D3.4060609@keyaccess.nl>
Date: Fri, 14 Dec 2007 15:36:03 +0100
From: Rene Herman <rene.herman@...il.com>
To: Ingo Molnar <mingo@...e.hu>
CC: Rene Herman <rene.herman@...il.com>,
"David P. Reed" <dpreed@...d.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Pavel Machek <pavel@....cz>
Subject: Re: [PATCH] x86_64: fix problems due to use of "outb" to port 80
on some AMD64x2 laptops, etc.
On 14-12-07 15:23, Ingo Molnar wrote:
> * Rene Herman <rene.herman@...il.com> wrote:
>
>> --- a/init/main.c
>> +++ b/init/main.c
>> @@ -229,10 +229,9 @@ static int __init obsolete_checksetup(char *line)
>> }
>>
>> /*
>> - * This should be approx 2 Bo*oMips to start (note initial shift), and will
>> - * still work even if initially too large, it will just take slightly longer
>> + * Initial value roughly corresponds to a 1 GHz CPU
>> */
>> -unsigned long loops_per_jiffy = (1<<12);
>> +unsigned long loops_per_jiffy = 1000000000 / HZ;
>>
>> EXPORT_SYMBOL(loops_per_jiffy);
>
> this is a factor of ~2400 increase - this will take an eternity to boot
> on any older CPU.
Only any outb_p's used before loops_per_jiffy is calibrated are affected.
This pre-calibation thing is what's historically held this change back (it's
been discussed dozens of times before). At 4096, not any machine is going to
have an appreciable delay before calibration when switching from the outb to
0x80.
Rene.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists