From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: "Tom Rini" <trini@kernel.crashing.org>
Cc: "Dan Malek" <dan@embeddededge.com>,
"Daniel Jacobowitz" <drow@false.org>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: Improved copy_page() function, about 30% speed up for mpc860!
Date: Wed, 5 Mar 2003 00:45:14 +0100 [thread overview]
Message-ID: <008201c2e2a8$1afc4a40$020120b0@jockeXP> (raw)
In-Reply-To: 20030304233558.GA17093@ip68-0-152-218.tc.ph.cox.net
> Which change in particular are you talking about?
This, in head_8xx.S:
* Addendum: The EA of a data TLB error is _supposed_ to be stored
* in DAR, but it seems that this doesn't happen in some cases, such
* as when the error is due to a dcbi instruction to a page with a
* TLB that doesn't have the changed bit set. In such cases, there
* does not appear to be any way to recover the EA of the error
* since it is neither in DAR nor MD_EPN. As a workaround, the
* _PAGE_HWWRITE bit is set for all kernel data pages when the PTEs
* are initialized in mapin_ram(). This will avoid the problem,
* assuming we only use the dcbi instruction on kernel addresses.
from http://lists.linuxppc.org/linuxppc-dev/200303/msg00022.html
> But I think as Dan
> has said, it's best to just accept this and move along. :) It's known
> to be horribly broken in some cases, but not admited to by Motorola, and
> distinguishing between 8xx's at runtime is not trivial.
Regarding dcbz on user space yes, but not kernel space. I will do some more digging/testing and
maybe something could go into 2.5 eventally
Jocke
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-04 23:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 17:50 Improved copy_page() function, about 30% speed up for mpc860! Joakim Tjernlund
2003-03-03 21:18 ` Dan Malek
2003-03-03 23:16 ` Joakim Tjernlund
2003-03-04 0:43 ` Dan Malek
2003-03-04 0:54 ` Daniel Jacobowitz
2003-03-04 3:38 ` Dan Malek
2003-03-04 8:29 ` Joakim Tjernlund
2003-03-04 13:33 ` Dan Malek
2003-03-04 15:24 ` Joakim Tjernlund
2003-03-04 17:00 ` Dan Malek
2003-03-04 22:01 ` Joakim Tjernlund
2003-03-04 22:41 ` Dan Malek
2003-03-04 23:20 ` Joakim Tjernlund
2003-03-04 23:35 ` Tom Rini
2003-03-04 23:45 ` Joakim Tjernlund [this message]
2003-03-05 0:05 ` Tom Rini
2003-03-05 0:19 ` Joakim Tjernlund
2003-03-05 17:12 ` Tom Rini
2003-03-05 17:50 ` Joakim Tjernlund
2003-03-05 17:15 ` Dan Malek
[not found] ` <1046737789.885.15.camel@zion.wanadoo.fr>
2003-03-04 0:51 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2003-02-27 13:08 Joakim Tjernlund
2003-02-27 15:45 ` Joakim Tjernlund
2003-02-28 17:31 ` Joakim Tjernlund
2003-03-03 21:28 ` Dan Malek
2003-03-04 0:09 ` Joakim Tjernlund
2003-03-04 0:19 ` Paul Mackerras
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='008201c2e2a8$1afc4a40$020120b0@jockeXP' \
--to=joakim.tjernlund@lumentis.se \
--cc=dan@embeddededge.com \
--cc=drow@false.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).