From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Need testers: G3 @ G4 laptops (powerbooks & ibooks)
Date: Wed, 25 Feb 2004 09:39:12 +1100 [thread overview]
Message-ID: <1077662351.965.21.camel@gaston> (raw)
In-Reply-To: <20040224175409.GC1052@smtp.west.cox.net>
> Are you sure that you can get away with this, passed on how the manuals
> (745x) describe the sequence of flush/invalidating the L2 (and, L3) ?
Do they describe disabling the L1 at all ? I did that after looking at
Darwin place in the first place. But then, I discovered it broke the
wallstreet. I had people test the patch removing those L1 stuffs for
some time and it seems to work.
I think the proper sequence is still what Apple does, but that means
all caches are tied together. I don't have time to work on that, and
there's the issue of possible snoops that Apple addresses by using the
ROM space for the displacement flush, we need something different of
course.
A resume of Apple sequence is that they always tear down and re-enable
all 3 caches in one operation. Using the HW assist when available.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-24 22:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 3:21 Need testers: G3 @ G4 laptops (powerbooks & ibooks) Benjamin Herrenschmidt
2004-02-18 15:45 ` Kiko Piris
2004-02-18 22:30 ` Benjamin Herrenschmidt
2004-02-18 16:03 ` digger vermont
2004-02-18 16:09 ` Colin Leroy
2004-02-18 16:31 ` digger vermont
2004-02-18 22:31 ` Benjamin Herrenschmidt
2004-02-18 17:45 ` Greg Watson
2004-02-18 17:58 ` digger vermont
2004-02-18 18:04 ` Michael Schmitz
2004-02-18 22:14 ` Ira Weiny
2004-02-24 17:54 ` Tom Rini
2004-02-24 22:39 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 21:46 Mark A. Greer
2004-02-25 23:47 ` Benjamin Herrenschmidt
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=1077662351.965.21.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).