linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Cox <adrian@humboldt.co.uk>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Remove CPU_FTR_NEED_COHERENT for 7448.
Date: Thu, 03 May 2007 17:07:06 +0000	[thread overview]
Message-ID: <1178212026.5586.17.camel@localhost.localdomain> (raw)
In-Reply-To: <1178208838.17201.52.camel@ld0161-tx32>

On Thu, 2007-05-03 at 11:13 -0500, Jon Loeliger wrote:
> > The problem is that many 32-bit PowerPC machines needed
> > CPU_FTR_NEED_COHERENT set for a second reason: compatibility with the
> > cache in the MPC107. This was handled by CPU_FTR_COMMON in cputable.h
> > before the L2 prefetch bug was known.  There may be other host bridges
> > that cache, but nobody will have noticed because all the CPUs had
> > CPU_FTR_NEED_COHERENT set already.

> Yes, you are correct and your concern is valid.  However,
> this case is still being handled by CONFIG_MPC10X_BRIDGE
> to deal with the MPC106/MPC107/etc north bridges.

My only concern here is that some other Northbridges may have a similar
cache issue to the MPC107, but that we haven't noticed because the
cputable entry has been a crutch for them. If we remove the entry, will
some other 7448 designs quietly stop working?  I think the Tsi108/109
are probably safe, but I don't know about other bridges.

> The CPU doesn't impose this requirement, the north bridge does.
> It might even better be named something like
>     CPU_FTR_NORTHBRDIGE_NEEDS_COHERENT.

Yes - we end up turning on coherency for multiple reasons - SMP, the L2
prefetch bug, or the cache in the MPC107. I quite like Ben H's idea of
doing this in machine_probe().

-- 
Adrian Cox <adrian@humboldt.co.uk>

  reply	other threads:[~2007-05-03 17:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 21:34 [PATCH] Remove CPU_FTR_NEED_COHERENT for 7448 Jon Loeliger
2007-05-03 10:17 ` Adrian Cox
2007-05-03 10:53   ` Benjamin Herrenschmidt
2007-05-03 16:13   ` Jon Loeliger
2007-05-03 17:07     ` Adrian Cox [this message]
2007-05-03 17:38       ` Jon Loeliger
2007-05-03 21:36     ` Benjamin Herrenschmidt
2007-05-04 15:16       ` Jon Loeliger
2007-05-04 22:25         ` Benjamin Herrenschmidt
2007-05-05 13:25           ` Adrian Cox
2007-05-07 17:31           ` Loeliger Jon-LOELIGER
2007-05-04 20:19   ` Kumar Gala
2007-05-03 11:02 ` Paul Mackerras
2007-05-03 16:04   ` Jon Loeliger
2007-05-03 23:34     ` Paul Mackerras
2007-05-04 15:13       ` Jon Loeliger
2007-05-10 16:17 ` Kumar Gala
2007-05-10 16:44   ` Jon Loeliger

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=1178212026.5586.17.camel@localhost.localdomain \
    --to=adrian@humboldt.co.uk \
    --cc=jdl@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).