From: Dan Malek <dan@mvista.com>
To: Magnus Damm <damm@opensource.se>
Cc: linuxppc-embedded@lists.linuxppc.org, mlocke@mvista.com
Subject: Re: runtime check of cacheline size.
Date: Wed, 04 Apr 2001 11:17:32 -0400 [thread overview]
Message-ID: <3ACB3B0C.294FC788@mvista.com> (raw)
In-Reply-To: 3ACAE9C5.6077A4E2@opensource.se
Magnus Damm wrote:
> Wouldn't it be nice with a glibc that works for all of us?
I think the MVista glibc distribution is headed that way, and
the patches are in the pipeline to the maintainers. There is
more than just cache line size that is processor dependent, and
all of these things have to be taken into consideration.
I know people are working on it, and are testing a variety of
implementations.
We also have to be careful about the 'dcbz' instruction. For
some reason, the behavior of this instruction changes depending
upon the silicon revision of the MPC8xx parts. This behavior is
more than just the way it may zero a cache line, and recently has
been trouble for the TLB handler (the 'morvek' as we now affectionately
call it :-). Sometimes it faults, sometimes not, sometimes alignment
faults, and you may not get the proper VA when recovering the
information from the registers. It is consistent for a particular
part, but not across the parts. For MPC8xx, I have removed the
use of this instruction from the kernel, and we may want to consider
doing that in the library as well. To complicate the exception
handlers (the 'morvek') to accomodate all of these different
conditions doesn't seem appropriate, and we may not be able to
catch all conditions.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-04-04 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 9:30 runtime check of cacheline size Magnus Damm
2001-04-04 15:17 ` Dan Malek [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=3ACB3B0C.294FC788@mvista.com \
--to=dan@mvista.com \
--cc=damm@opensource.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mlocke@mvista.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).