From: Kumar Gala <kumar.gala@freescale•com>
To: Paul Mackerras <paulus@samba•org>
Cc: Linux/PPC Development <linuxppc-dev@lists•linuxppc.org>
Subject: Re: [PATCH] align.c
Date: Thu, 22 Jul 2004 17:49:31 -0500 [thread overview]
Message-ID: <6505FDD3-DC31-11D8-A541-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <40F8138F.8090004@pi.be>
Paul,
Can you explain to me why/when stswi/lswi would get alignment
exceptions. I think I'm missing something :) The reason I ask is we
are working on some emulation handlers but are not doing anything with
regards to alignment for e500.
- kumar
On Jul 16, 2004, at 12:42 PM, Stef Simoens wrote:
> 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/
next prev parent reply other threads:[~2004-07-22 22:49 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
2004-07-22 22:49 ` Kumar Gala [this message]
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=6505FDD3-DC31-11D8-A541-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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