All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Waite <linwoes@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Mark A. Greer" <mgreer@mvista.com>,
	Adrian Cox <adrian@humboldt.co.uk>,
	linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] Workaround for 745x data corruption bug
Date: Wed, 4 Aug 2004 13:38:38 -0400	[thread overview]
Message-ID: <36b714c8040804103826917da1@mail.gmail.com> (raw)
In-Reply-To: <1091580331.1922.42.camel@gaston>


Ben,

So what kind of aliasing issues do you forsee uner 2.4?
Thanks
Brian
On Wed, 04 Aug 2004 10:45:32 +1000, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
>
> > Looking at this errata, I don't think poeple using Marvell chips will
> > be affected by this errata.
> > I don't see this as impacting the IO subsystem only the internal MPX system. IE
> > using a 2 74xx system and not using the M bit. This race can also
> > occur on a single processor system with the M disabled, as it is in
> > Linux, but it has nothing to do with the memory controller mapping its
> > PCI<->mem windows as non cacheable. You should be able to boost the IO
> > throughput using non coherency without this errata impacting you any
> > more than it already is.
> >
> > Anyone please correct me if I am wrong because I need to know.
>
> Note that I feel obligated to re-state again that doing non-coherent
> DMA on a 6xx/7xx/7xxx CPU is a big no brainer and is asking for all sorts
> of cache aliasing issues because of the way the kernel linear mapping of
> memory is BAT mapped... (Note that 2.6 should be able to deal with the
> DBAT beeing disabled, at the expense of perfs, though I'm pretty sure we
> need the IBAT still set).
>
> Ben.
>
>

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-08-04 17:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-31 16:27 [PATCH] Workaround for 745x data corruption bug Adrian Cox
2004-08-01  2:53 ` Benjamin Herrenschmidt
2004-08-02 15:20   ` Kumar Gala
2004-08-02 21:40     ` Benjamin Herrenschmidt
2004-08-02 18:20 ` Mark A. Greer
2004-08-02 21:47   ` Sven Luther
2004-08-03 13:17   ` Brian Waite
2004-08-03 21:55     ` Mark A. Greer
2004-08-04 14:37       ` Brian Waite
2004-08-04 17:55         ` Mark A. Greer
2004-08-04 20:39           ` Adrian Cox
2004-08-04  0:45     ` Benjamin Herrenschmidt
2004-08-04 17:38       ` Brian Waite [this message]
2004-08-04 22:43         ` Benjamin Herrenschmidt

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=36b714c8040804103826917da1@mail.gmail.com \
    --to=linwoes@gmail.com \
    --cc=adrian@humboldt.co.uk \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mgreer@mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.