linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>,
	<yellowdog-devel@lists.yellowdoglinux.com>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: some questions on new dual 1Gig G4's support?
Date: Sun, 3 Feb 2002 13:04:26 +0100	[thread overview]
Message-ID: <20020203120426.22252@smtp.wanadoo.fr> (raw)
In-Reply-To: <20020202201734.KLTB18463.tomts7-srv.bellnexxia.net@there>


>Thanks!  I see you have hit the big time!  The /. inerview article was
>great!  Now I can say I actually know someone famous!  ;-)
>
>One last question:
>
>The 7455 errata basically says to disable the L2 hardware prefetch engine
>(MSSCR0[L2PFE] = 0 when disabling the L1 data cache.
>
>It goes on to say that the L1 data cache may be disabled during cache
>flushing on some systems or be disabled upon startup.
>
>Do we disable L1 cache's during cache flushing?  If so were should I be
>looking for this code to get the workaround in place?

I don't think we disable L1 except when changing L2CR value or when
going to sleep.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-02-03 12:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-02 14:50 some questions on new dual 1Gig G4's support? Kevin B. Hendricks
2002-02-02 20:11 ` Benjamin Herrenschmidt
2002-02-02 20:21   ` Kevin B. Hendricks
2002-02-03 12:04     ` Benjamin Herrenschmidt [this message]
2002-02-03 19:02   ` Kevin B. Hendricks
2002-02-03 22:39     ` Timothy A. Seufert
2002-02-04 18:15     ` benh
2002-02-04 18:27       ` Kevin B. Hendricks
2002-02-05 13:23         ` benh
2002-02-04 17:57   ` Kevin B. Hendricks
2002-02-04 18:23     ` benh

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=20020203120426.22252@smtp.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=kevin.hendricks@sympatico.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=yellowdog-devel@lists.yellowdoglinux.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).