From: Dan Malek <dan@embeddededge.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: wilhardt@synergymicro.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: MPC7455 and lwarx
Date: Wed, 27 Nov 2002 09:46:57 -0500 [thread overview]
Message-ID: <3DE4DAE1.9060602@embeddededge.com> (raw)
In-Reply-To: 3DE4C207.8020500@iram.es
Gabriel Paubert wrote:
> No, it is documented somewhere in Motorola docs that lwarx/stwcx. only
> work on writeback cacheable space. Earlier processors allow non-cacheable
> space, I believe that this restriction was introduced with the 7440/7450.
There are implementation options in the PowerPC specification that will
produce different "working" behavior when these instructions are not
used properly. As Gabriel mentioned, the programmer interface specifies
these instrucitons work properly only on cached, writeback data spaces.
This is because the finest granularity implementation is a cache line and
the synchronization information is stored in the cache tag. Processors
that aren't MP capable, like the 4xx, appear to operate as if they have
a single global flag to support lwarx/stwcx so the cache mode of the
desitination address (and the address itself) is irrelevant. This
"restriction" has been around forever, MP systems won't work properly
without it (and all 6xx and "bigger" cores are MP capable).
Why do you want to use these instructions on a data space that isn't
cached? Further, why are you running this class of processor with
uncached memory?
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-11-27 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 22:00 MPC7455 and lwarx Dave Wilhardt
2002-11-27 13:00 ` Gabriel Paubert
2002-11-27 14:46 ` Dan Malek [this message]
2002-11-27 17:11 ` Dave Wilhardt
2002-11-27 17:32 ` Gabriel Paubert
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=3DE4DAE1.9060602@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
--cc=wilhardt@synergymicro.com \
/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).