From: Dan Malek <dan@embeddededge.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] ppc32: Fix alignment exception checking on load/store multiple instructions
Date: Tue, 12 Apr 2005 12:20:12 -0400 [thread overview]
Message-ID: <014bd721f4bc5070a07e24fc4ac1c248@embeddededge.com> (raw)
In-Reply-To: <cb6c89fb776248d3a2ddbcd5d3d043ed@freescale.com>
On Apr 12, 2005, at 11:26 AM, Kumar Gala wrote:
> Upon further review, the PEM and PPC Arch spec, say that its ok to
> emulate lwarz as an lwz. From the spec:
Hmmm ... Seems weird. Since the emulation won't create the
reservation,
the subsequent stwcx will fail. If the stwcx to the same unaligned
address
will be a programming error.
Also, the EREF states that neither the lwarx nor stwcx should be
emulated,
and it's a programming error to have unaligned accesses with these.
I still don't like this "similar but different" Book-E architecture,
but I guess
we have to live with it ....
> The instructions lwz and lwarx give the same DSISR bits (all zero).
> But if lwarx causes an Alignment interrupt, it should not be emulated.
??? Those are nearly the same words from the EREF, I just didn't find
anything
like the following.
> ... It is adequate for the Alignment interrupt handler simply to treat
> the instruction as if it were lwz. The emulator
> must use the address in the DAR, rather than compute it from RA/RB/D,
> because lwz and lwarx have different instruction formats.
I guess it's done as lwz because it's not possible to actually emulate
an
unaligned lwarx?
> So we are handled lwarx according to the arch specs already.
If that's the way you read it :-) Probably not worth the discussion,
but
I brought it up since we are here and it will be soon forgotten.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-04-12 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 6:03 [PATCH] ppc32: Fix alignment exception checking on load/store multiple instructions Kumar Gala
2005-04-12 14:46 ` Dan Malek
2005-04-12 15:06 ` Kumar Gala
2005-04-12 15:26 ` Kumar Gala
2005-04-12 16:20 ` Dan Malek [this message]
2005-04-12 15:31 ` Dan Malek
2005-04-19 14:50 ` Kumar Gala
2005-04-20 1:26 ` Paul Mackerras
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=014bd721f4bc5070a07e24fc4ac1c248@embeddededge.com \
--to=dan@embeddededge.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-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).