mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: adrian@humboldt.co.uk, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.linuxppc.org, paulus@samba.org
Subject: Re: [PATCH][2.4.27] PowerPC 745x data corruption bug fix
Date: Mon, 16 Aug 2004 10:05:34 -0700	[thread overview]
Message-ID: <20040816170534.GA7303@smtp.west.cox.net> (raw)
In-Reply-To: <200408161004.i7GA48fY002331@harpo.it.uu.se>

On Mon, Aug 16, 2004 at 12:04:08PM +0200, Mikael Pettersson wrote:
> On Mon, 16 Aug 2004 08:40:51 +0100, Adrian Cox wrote:
> >On Mon, 2004-08-16 at 03:54, Mikael Pettersson wrote:
> >> On Mon, 16 Aug 2004 08:13:59 +1000, Paul Mackerras wrote:
> >
> >> >Does CONFIG_MPC10X_BRIDGE mean just MPC107, or is it set for (e.g.)
> >> >systems with a MPC106 as well?
> >> 
> >> I just copied this part from 2.6.8. Currently it
> >> seems CONFIG_MPC10X_BRIDGE is set for some platforms
> >> (sandpoint and lopec), but it is definitely not set
> >> for MPC106 machines like my beige PowerMac G3.
> >
> >I don't understand how your patch can improve the stability of your
> >machine when CONFIG_MPC10X_BRIDGE isn't set. 
> 
> See below.
> 
> >Pages should be marked coherent for the MPC106 as well as the MPC107,
> >but the problem shouldn't be seen unless the processor supports the
> >shared cache line state. My original patch only set
> >CPU_FTR_NEED_COHERENT for the 745x family, as only 745x plus 604 have
> >the shared state, but Tom Rini extended it to cover all the other
> >processors. I'm not convinced that extending it was necessary, but the
> >performance impact should be low.
> 
> CPU_FTR_NEED_COHERENT gets set via two independent mechanisms:
> 
> 1. The old code base had #ifdef SMP blocks in hashtable.S
>    and ppc_mmu.c that enforced _PAGE_COHERENT. Since that's
>    now also required in some non-SMP cases, they were
>    changed to be controlled by CPU_FTR_NEED_COHERENT. That's
>    what CPU_FTR_COMMON is for: enforcing CPU_FTR_NEED_COHERENT
>    on SMP. (Ignore CONFIG_MPC10X_BRIDGE. It's noise.)
> 
> 2. For the 745x CPUs, CPU_FTR_NEED_COHERENT is explicitly
>    added to their cpu_features bit mask.
> 
> So previously a CPU got _PAGE_COHERENT on SMP.
> Now a CPU gets _PAGE_COHERENT on (SMP || 745x).
> 
> I suspect the CONFIG_MPC10X_BRIDGE is an attempt to enable
> the fix in some other cases too.

The reason CPU_FTR_NEED_COHERENT was added was to work around an MPC107
(now Tsi107) errata.  See
http://216.239.57.104/search?q=cache:1MDn1X8ieUUJ:www.geocrawler.com/archives/3/8358/2002/9/100/9559482/+%22Adrian+Cox%22+errata&hl=en
(original is conn refused right now).

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2004-08-16 17:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16 10:04 Mikael Pettersson
2004-08-16 17:05 ` Tom Rini [this message]
2004-08-18 11:10   ` Adrian Cox
  -- strict thread matches above, loose matches on Subject: below --
2004-08-16  2:54 Mikael Pettersson
2004-08-16  7:40 ` Adrian Cox
2004-08-16  9:06   ` Paul Mackerras
2004-08-16  9:15     ` Adrian Cox
2004-08-15 11:16 Mikael Pettersson
2004-08-15 22:13 ` 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=20040816170534.GA7303@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=adrian@humboldt.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mikpe@csd.uu.se \
    --cc=paulus@samba.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

all inboxes | Powered by JetHome®