From: Dan Malek <dan@netx4.com>
To: daniel.marmier@lightning.ch
Cc: Dan Malek <dan@netx4.com>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Help with string.S
Date: Thu, 13 Jul 2000 14:52:01 -0400 [thread overview]
Message-ID: <396E0FD1.B43AC724@embeddededge.com> (raw)
In-Reply-To: 396AB595.DC926132@lightning.ch
Daniel Marmier wrote:
>
> Dan Malek wrote:
> > These are becoming a pain in the ass instructions.
> I have seen this happen on cacheable memory with copyback enabled.
> The dcbz-memcpy caused the destination to be zeroed, IIRC.
OK, I think I am bailing out here. For some reason, if I remove
the 'dcbz' instructions on the MPC8xx processor the world is just
a better place. I don't know why, maybe because of some of the
TLB mapping, but I can't find a reason.
I am going to put #ifdef CONFIG_8xx around the dcbz instructions,
and where they are actually used to zero-fill memory I will use
store operations. The other option is to make the changes at a
higher level (like make 'clear_page' call 'memset' with 0), but I
think the direct assembly changes are preferable. Suggestions welcome.
I'll keep looking for a better solution, but I can't hold up others
trying to use this kernel.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-13 18:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-08 22:57 Help with string.S Dan Malek
2000-07-08 23:57 ` Dan Malek
2000-07-10 6:14 ` Daniel Marmier
2000-07-10 15:17 ` David Edelsohn
2000-07-10 22:42 ` Dan Malek
2000-07-11 5:50 ` Daniel Marmier
2000-07-13 18:52 ` Dan Malek [this message]
2000-07-11 10:06 ` Adrian Cox
2000-07-11 15:53 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-08-16 7:26 Graham Stoney
2000-08-16 16:22 ` tom_gall
2000-08-17 0:50 ` Graham Stoney
2000-08-17 19:28 ` 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=396E0FD1.B43AC724@embeddededge.com \
--to=dan@netx4.com \
--cc=daniel.marmier@lightning.ch \
--cc=linuxppc-dev@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 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).