From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: "Eugene Surovegin" <ebs@ebshome.net>
Cc: <linux-mtd@lists.infradead.org>, "Marius Groeger" <mag@sysgo.de>
Subject: Re: PATCH: support for Arctic/Beech/Ebony
Date: Fri, 31 Jan 2003 01:31:39 +0100 [thread overview]
Message-ID: <008901c2c8c0$1ee8e250$020120b0@jockeXP> (raw)
In-Reply-To: 5.1.0.14.2.20030130154710.03813208@mail.ebshome.net
> At 02:37 PM 1/30/2003, Joakim Tjernlund wrote:
>
> > > > > > - You don't need mb() since ioremap will add the
> > > > > > GUARDED attribute to the mapping.
> > > > >
> > > > > Well, this is not quite correct.
> > > > >
> > > > > GUARDED attribute does _NOT_ prevent reordering of loads and stores
> > on PPC
> > > > > (on 4xx at least).
> > > > >
> > > > > See comments in asm-ppc/system.h and also IBM app note "Software
> > > > > consideration when migrating to the PowerPC 440GP from 405GP"
> > > > >
> > > >
> > > >hmm, maybe it's specific to the 8xx family. 860 and 862 does not do
> > > >speculative accesses on GUARDED memory.
> > >
> > > It does! But speculative accesses and access reordering are not the same
> > > thing :)
> >
> >what do you mean, does or does not do speculative accesses?
>
> Sorry for being unclear.
NP
>
> If I remember correctly, cache inhibited + guarded is enough for 8xx to
> prevent both speculative access and load/store reordering.
OK, thanks.
> But this is not true for ALL PPC processors, 440GP is an example when this
> is not enough
>
>
> > >
> > > There is a subtle difference.
> >
> >Yes I understand now, but I discussed this with my HW contact at Motorola
> >and he agreed
> >that it was OK to remove the mb(). Maybe he was wrong or perhaps non
> >speculative accesses
> >on mpc 860/862 also disables reorder? I can not find any statement that
> >confirms this.
> >
> >Howerver I have been running our boards without the mb()'s for months now,
> >no problem with
> >it so far.
>
> Well, patch we are discussing is for 4xx, not for 8xx.
Yes, so the mb()'s should be put back.
Marius, sorry for the noise.
Jocke
>
> Eugene.
next prev parent reply other threads:[~2003-01-31 0:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5.1.0.14.2.20030130021112.020b0628@mail.ebshome.net>
[not found] ` <IGEFJKJNHJDCBKALBJLLKEMCFJAA.joakim.tjernlund@lumentis.se>
2003-01-30 18:12 ` PATCH: support for Arctic/Beech/Ebony Eugene Surovegin
2003-01-30 22:37 ` Joakim Tjernlund
2003-01-30 23:56 ` Eugene Surovegin
2003-01-31 0:31 ` Joakim Tjernlund [this message]
2003-01-31 8:29 ` Marius Groeger
2003-01-28 17:00 Marius Groeger
2003-01-29 21:46 ` Joakim Tjernlund
2003-01-29 22:44 ` David Woodhouse
2003-01-29 23:00 ` Joakim Tjernlund
2003-01-29 23:01 ` David Woodhouse
2003-01-29 23:09 ` Joakim Tjernlund
2003-01-29 23:52 ` Joakim Tjernlund
2003-01-30 8:47 ` Marius Groeger
2003-01-30 10:42 ` David Woodhouse
2003-01-30 11:05 ` Marius Groeger
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='008901c2c8c0$1ee8e250$020120b0@jockeXP' \
--to=joakim.tjernlund@lumentis.se \
--cc=ebs@ebshome.net \
--cc=linux-mtd@lists.infradead.org \
--cc=mag@sysgo.de \
/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