From: linas@austin.ibm.com (Linas Vepstas)
To: Kim Phillips <kim.phillips@freescale.com>
Cc: sfr@canb.auug.org.au, paulus@samba.org, linuxppc-dev@ozlabs.org
Subject: Re: [POWERPC] convert string i/o operations to C
Date: Tue, 19 Sep 2006 14:04:25 -0500 [thread overview]
Message-ID: <20060919190425.GM29167@austin.ibm.com> (raw)
In-Reply-To: <20060919135259.303706d3.kim.phillips@freescale.com>
On Tue, Sep 19, 2006 at 01:52:59PM -0500, Kim Phillips wrote:
> On Tue, 19 Sep 2006 13:29:53 -0500
> linas@austin.ibm.com (Linas Vepstas) wrote:
>
> >
> > What does this twi do? According to my powerpc docs, this would be a
> > no-op. Does this have some magic synchronizing powers on certain
> > implementations? If so, there should be at least a comment card added
> > about why the twi is there. (This special ability of twi might be
> > well-known to some, but still, this is not immediately obvious,
> > and not immedately documented in e.g. the PEM.)
>
> include/asm-p[ower]pc/io.h sheds some light on the matter:
>
> * With the sequence below (twi; isync; nop), we have found that
> * the machine check occurs on one of the three instructions on
> * all PPC implementations tested so far. The twi and isync are
> * needed on the 601 (in fact twi; sync works too), the isync and
> * nop are needed on 604[e|r], and any of twi, sync or isync will
> * work on 603[e], 750, 74xx.
> * The twi creates an explicit data dependency on the returned
> * value which seems to be needed to make the 601 wait for the
> * load to finish.
Thanks. I notice that this commentary appears in asm-ppc/io.h
but not in asm-powerpc/io.h -- Perhaps a patch is in order ...
I'm creating such a patch now ...
--linas
next prev parent reply other threads:[~2006-09-19 19:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 12:23 [POWERPC] convert string i/o operations to C Stephen Rothwell
2006-09-19 12:42 ` David Howells
2006-09-19 23:07 ` Stephen Rothwell
2006-09-19 18:29 ` Linas Vepstas
2006-09-19 18:52 ` Kim Phillips
2006-09-19 18:58 ` Matt Sealey
2006-09-19 19:10 ` Segher Boessenkool
2006-09-19 19:20 ` Matt Sealey
2006-09-19 19:47 ` Segher Boessenkool
2006-09-19 23:17 ` Benjamin Herrenschmidt
2006-09-19 23:14 ` Benjamin Herrenschmidt
2006-09-19 19:04 ` Linas Vepstas [this message]
2006-09-19 19:06 ` Segher Boessenkool
2006-09-19 23:12 ` Benjamin Herrenschmidt
2006-09-20 0:03 ` Segher Boessenkool
2006-09-20 0:08 ` Benjamin Herrenschmidt
2006-09-20 0:29 ` Segher Boessenkool
2006-09-20 3:35 ` Stephen Rothwell
2006-09-20 4:38 ` Michael Ellerman
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=20060919190425.GM29167@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=kim.phillips@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).