From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Steve Deiters <SteveDeiters@BASLER.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] arch/powerpc/lib/copy_32.S: Use alternate memcpy for MPC512x and MPC52xx
Date: Thu, 08 Jul 2010 15:10:45 +1000 [thread overview]
Message-ID: <1278565845.28659.75.camel@pasglop> (raw)
In-Reply-To: <181804936ABC2349BE503168465576460F272CA4@exchserver.basler.com>
On Tue, 2010-06-29 at 11:04 -0500, Steve Deiters wrote:
> These processors will corrupt data if accessing the local bus with
> unaligned
> addresses. This version fixes the typical case of copying from Flash on
> the
> local bus by keeping the source address always aligned.
Shouldn't this be solved by using memcpy_to/fromio ?
Cheers,
Ben.
> Signed-off-by: Steve Deiters <SteveDeiters@basler.com>
> ---
> arch/powerpc/lib/copy_32.S | 56
> ++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 56 insertions(+), 0 deletions(-)
>
> diff --git a/arch/powerpc/lib/copy_32.S b/arch/powerpc/lib/copy_32.S
> index 74a7f41..42e7df5 100644
> --- a/arch/powerpc/lib/copy_32.S
> +++ b/arch/powerpc/lib/copy_32.S
> @@ -226,6 +226,60 @@ _GLOBAL(memmove)
> bgt backwards_memcpy
> /* fall through */
>
> +#if defined(CONFIG_PPC_MPC512x) || defined(CONFIG_PPC_MPC52xx)
> +
> +/*
> + * Alternate memcpy for MPC512x and MPC52xx to guarantee source
> + * address is always aligned to prevent corruption issues when
> + * copying unaligned from the local bus. This only fixes the usage
> + * when copying from the local bus (e.g. Flash) and will not fix
> + * issues copying to the local bus
> + */
> +_GLOBAL(memcpy)
> + srwi. r7,r5,3
> + addi r6,r3,-4
> + addi r4,r4,-4
> + beq 2f /* if less than 8 bytes to do */
> + andi. r0,r4,3 /* get src word aligned */
> + mtctr r7
> + bne 5f
> +1: lwz r7,4(r4)
> + lwzu r8,8(r4)
> + stw r7,4(r6)
> + stwu r8,8(r6)
> + bdnz 1b
> + andi. r5,r5,7
> +2: cmplwi 0,r5,4
> + blt 3f
> + andi. r0,r4,3
> + bne 3f
> + lwzu r0,4(r4)
> + addi r5,r5,-4
> + stwu r0,4(r6)
> +3: cmpwi 0,r5,0
> + beqlr
> + mtctr r5
> + addi r4,r4,3
> + addi r6,r6,3
> +4: lbzu r0,1(r4)
> + stbu r0,1(r6)
> + bdnz 4b
> + blr
> +5: subfic r0,r0,4
> + mtctr r0
> +6: lbz r7,4(r4)
> + addi r4,r4,1
> + stb r7,4(r6)
> + addi r6,r6,1
> + bdnz 6b
> + subf r5,r0,r5
> + rlwinm. r7,r5,32-3,3,31
> + beq 2b
> + mtctr r7
> + b 1b
> +
> +#else
> +
> _GLOBAL(memcpy)
> srwi. r7,r5,3
> addi r6,r3,-4
> @@ -267,6 +321,8 @@ _GLOBAL(memcpy)
> mtctr r7
> b 1b
>
> +#endif
> +
> _GLOBAL(backwards_memcpy)
> rlwinm. r7,r5,32-3,3,31 /* r0 = r5 >> 3 */
> add r6,r3,r5
next prev parent reply other threads:[~2010-07-08 5:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 16:04 [PATCH] arch/powerpc/lib/copy_32.S: Use alternate memcpy for MPC512x and MPC52xx Steve Deiters
2010-06-29 16:58 ` Segher Boessenkool
2010-07-08 5:10 ` Benjamin Herrenschmidt [this message]
2010-07-08 5:38 ` Grant Likely
2010-07-08 14:38 ` Steve Deiters
2010-07-08 15:22 ` Grant Likely
2010-07-08 18:40 ` Albrecht Dreß
2010-07-08 19:30 ` Segher Boessenkool
2010-07-08 20:09 ` Scott Wood
2010-07-09 12:59 ` Segher Boessenkool
2010-07-09 16:18 ` Scott Wood
2010-07-08 20:09 ` Albrecht Dreß
2010-07-09 13:03 ` Segher Boessenkool
2010-07-11 7:40 ` Milton Miller
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=1278565845.28659.75.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=SteveDeiters@BASLER.com \
--cc=linuxppc-dev@lists.ozlabs.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).