From: Dan Malek <dmalek@jlc.net>
To: Grant Erickson <grant@lcse.umn.edu>
Cc: linuxppc-embedded@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: PPC Cache Flush and Invalidate Routines
Date: Wed, 08 Dec 1999 19:12:01 -0500 [thread overview]
Message-ID: <384EF3D1.DFC1D281@jlc.net> (raw)
In-Reply-To: Pine.SGI.4.10.9912081623090.145056-100000@brule.borg.umn.edu
Grant Erickson wrote:
>
> In trying to accomodate the 4xx-based code into the Linux kernel, I've
> encountered an issue which relates to the cache flushing and invalidation
> routines in misc.S.
> Thoughts, opinions?
We could simply create a configuration #define for the cache line size
that is assigned in the 'make config' scripts when the processor type
is chosen.
A further, and more challenging, problem arises in the library
relocation functions. When writing instructions to memory, the data
caches have to be pushed, instruction caches invalidated, and the
functions assume a 32 byte cache line. This doesn't work well on the
16 byte line processors. We discussed this a long time ago without
resolution. The old C libraries on the ppc.kernel.org server that I
built for the 8xx have this corrected.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-09 0:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-08 22:45 PPC Cache Flush and Invalidate Routines Grant Erickson
1999-12-08 23:02 ` Gary Thomas
1999-12-08 23:58 ` Daniel L. Taylor
1999-12-09 0:12 ` Dan Malek [this message]
1999-12-08 23:25 ` Grant Erickson
1999-12-08 23:46 ` Dan Malek
1999-12-12 19:56 ` Noah Misch
1999-12-13 19:51 ` Dan Malek
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=384EF3D1.DFC1D281@jlc.net \
--to=dmalek@jlc.net \
--cc=grant@lcse.umn.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.