linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stef Simoens <stef.simoens@pi.be>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] align.c
Date: Fri, 16 Jul 2004 19:42:39 +0200	[thread overview]
Message-ID: <40F8138F.8090004@pi.be> (raw)
In-Reply-To: <69A5B0EA-D669-11D8-A9B5-000393DBC2E8@freescale.com>


Kumar Gala wrote:
> Do you really see string ops and alignment exceptions?  I was under the
> impression they did byte accesses.

Yes, but i've only seen alignment exceptions with stswi/lswi
instructions though.

(On the MPC601, stswi/lswi has better timings than a series of stw/lwz;
that's why I'm probably the only one seeing them...)

While I was at it, Paulus asked me to handle stmw/lmw and stswx/lswx as
well...

Stef

> On Jul 14, 2004, at 1:36 PM, Stef Simoens wrote:
>
>> This is an (updated) diff to arch/ppc/kernel/align.c of the 2.6.8-rc1
>> kernel.
>> The patch adds support for the handling of alignment exceptions of
>> multiple (lmw/stmw) and string (lswi/lswx/stswi/stswx) instructions.
>> Stef
>>
>> diff -ur linux-2.6.8-rc1/arch/ppc/kernel/align.c
>> linux-2.6.8-rc1-mq/arch/ppc/kernel/align.c
>> --- linux-2.6.8-rc1/arch/ppc/kernel/align.c    2004-07-12
>> 17:46:42.525695737 +0200
>> +++ linux-2.6.8-rc1-mq/arch/ppc/kernel/align.c    2004-07-12
>> 20:25:24.390989048 +0200
(snip)

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-07-16 17:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 18:36 [PATCH] align.c Stef Simoens
2004-07-15 14:15 ` Kumar Gala
2004-07-16 17:42   ` Stef Simoens [this message]
2004-07-22 22:49     ` Kumar Gala
2004-07-23 13:10       ` Segher Boessenkool
2004-08-03  8:00     ` Gabriel Paubert
2004-08-04 11:36       ` Segher Boessenkool

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=40F8138F.8090004@pi.be \
    --to=stef.simoens@pi.be \
    --cc=kumar.gala@freescale.com \
    --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).