From: Steve Snyder <swsnyder@insightbb.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Where to call L2 cache enabling code from?
Date: Fri, 14 Apr 2006 12:49:49 -0400 [thread overview]
Message-ID: <200604141249.49366.swsnyder@insightbb.com> (raw)
In-Reply-To: <1145029574.17531.26.camel@localhost.localdomain>
On Friday 14 April 2006 11:46 am, Alan Cox wrote:
> On Gwe, 2006-04-14 at 11:05 -0400, Steve Snyder wrote:
> > I have a machine in which the BIOS does not enable the Pentium3's L2
> > cache at boot time. At what point in the kernel init process
> > can/should I call the code to enable the cache?
>
> What part of the cache setup is not done correctly ? The mtrr registers
> or other things ?
It's not that the kernel is failing in any respect. The BIOS simply does
not enable the on-CPU L2 cache at power-on. (The machine originally
shipped with a Pentium2, and doesn't know how to enable the L2 cache on
the Pentium3 that is now running in it.)
I've got a small device driver that enables the L2 cache. It works fine
when build as a module and loaded after booting has completed. My goal
is to move the code into the kernel so that it is run early in the kernel
init process. I expect that having the L2 cache go from "0KB" to 256KB
will improve boot time greatly, as well as informing the kernel from the
get-go of the true capabilities of this processor.
Getting the code into the kernel image is a no-brainer. But once it is
built into the kernel, at what point should I call it?
Thanks for the response.
next prev parent reply other threads:[~2006-04-14 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 15:05 Where to call L2 cache enabling code from? Steve Snyder
2006-04-14 15:46 ` Alan Cox
2006-04-14 16:49 ` Steve Snyder [this message]
2006-04-14 17:00 ` Dave Jones
2006-04-14 17:08 ` Zan Lynx
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=200604141249.49366.swsnyder@insightbb.com \
--to=swsnyder@insightbb.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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