From: Becky Bruce <becky.bruce@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Merge align.c
Date: Tue, 15 Nov 2005 21:23:13 -0600 [thread overview]
Message-ID: <4ad202b87fa52d954e645b05fb45ca13@freescale.com> (raw)
In-Reply-To: <1132108490.5646.67.camel@gaston>
On Nov 15, 2005, at 8:34 PM, Benjamin Herrenschmidt wrote:
> >
> > BTW, Based on the pile of docs I have here, I think the list of
> > alignment-exception-causing events on FSL's current parts (603, 603e,
> > 750, 74x, 74xx, e500) is:
> >
> > - lmw/stmw (all procs, non-word aligned)
> > - single and double precision floating point ld/st ops (non-E500, non
> > data size aligned)
> > - dcbz to WT or CI memory (all procs)
> > - dcbz with cache disabled (all procs but 603e?)
> > - misaligned little endian accesses (603e)
> > - lwarx/stwcx (all procs)
> > - multiple/string with LE set (750, 603e, 7450, 7400)
> > - eciwx/ecowx (750, 7450, 7400)
> > - a couple of others related to vector processing
> >
> > If anybody knows offhand of something missing there, let me know.
>
> What about lwz/stw cropssing page boundaries ? Is this handled in HW ?
>
> Ben.
Apparently so, much to my surprise - I ran the testcase with those
instructions misaligned across a page boundary last night and got no
alignment exception. I was surprised, and asked my husband about it
(he worked on the load/store units for a bunch of our parts), and he
says these guys never cause an exception for any of FSL's current parts
as far as he knows. This is supported by our documentation as well -
the only place I see these listed is on 603e, where they can cause an
exception if the page is mapped little endian.
-B
next prev parent reply other threads:[~2005-11-16 3:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 8:00 [PATCH] powerpc: Merge align.c Benjamin Herrenschmidt
2005-11-14 19:53 ` Becky Bruce
2005-11-14 20:55 ` Benjamin Herrenschmidt
2005-11-15 5:10 ` Becky Bruce
2005-11-15 5:35 ` Benjamin Herrenschmidt
2005-11-16 2:19 ` Becky Bruce
2005-11-16 2:34 ` Benjamin Herrenschmidt
2005-11-16 3:23 ` Becky Bruce [this message]
2005-11-16 16:54 ` Andrey Volkov
2005-11-16 4:26 ` Dan Malek
2005-11-16 5:00 ` Benjamin Herrenschmidt
2005-11-16 5:35 ` Dan Malek
2005-11-16 6:13 ` Benjamin Herrenschmidt
2005-11-16 9:36 ` Gabriel Paubert
2005-11-16 15:15 ` Kumar Gala
2005-11-16 16:31 ` Becky Bruce
2005-11-16 19:24 ` Dan Malek
2005-11-16 19:20 ` Dan Malek
2005-11-16 19:45 ` Gabriel Paubert
2005-11-16 20:36 ` 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=4ad202b87fa52d954e645b05fb45ca13@freescale.com \
--to=becky.bruce@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@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).