linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Nick Hennenfent <nhennenfent@egtinc.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: I need help with L2 cache on 440GX rev C
Date: Thu, 21 Jul 2005 06:18:09 -0700	[thread overview]
Message-ID: <20050721131809.GA13216@gate.ebshome.net> (raw)
In-Reply-To: <A3008858EC44C34382A7E3935C24615E01074D3B@egtf001.egt.intra>

On Thu, Jul 21, 2005 at 08:44:46AM -0400, Nick Hennenfent wrote:
> 
> I have an embedded 440GX rev C runnng at about 500Mhz.
> I am using a 2.4.20 linux kernel.
> I borrowed Matt Porter's code from the 2.6 kernels in
> order to enable the L2 cache. The code compiles and
> runs ok, but the cache does not seem to be enabled!!!
> I ran some tests with/without the L2 cache code and 
> there is no difference.
> (A qsort of 1 million random integers takes 2 seconds).
> Is there some other magic trick to enable that cache????

No, there is no magic involved. 2.6 code (ibm440gx_l2c_enable()) 
works just fine.

Make sure your firmware doesn't enable L2C itself, in this case kernel 
enable code isn't needed at all, and you won't see any difference if 
you remove it.

2.6 has /proc/cpuinfo has a 440GX-specific handler 
(ibm440gx_show_cpuinfo()), you can put something similar into your 2.4 
kernel to see actual L2C state.

-- 
Eugene

      reply	other threads:[~2005-07-21 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 12:44 I need help with L2 cache on 440GX rev C Nick Hennenfent
2005-07-21 13:18 ` Eugene Surovegin [this message]

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=20050721131809.GA13216@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=nhennenfent@egtinc.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).