From: Brian Waite <linwoes@gmail.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: Adrian Cox <adrian@humboldt.co.uk>, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] Workaround for 745x data corruption bug
Date: Tue, 3 Aug 2004 09:17:49 -0400 [thread overview]
Message-ID: <36b714c804080306175c5dc3f6@mail.gmail.com> (raw)
In-Reply-To: <410E85EE.8050707@mvista.com>
> Well that sucks (the bug, not the patch :). Many people like to turn
> off coherency when using Marvell host bridges b/c they struggle
> performance-wise with coherency on (at least on some versions).
>
> One change to the patch, though. According to the 7447/7457 errata doc,
> rev 1.2 doesn't have the bug. The attached patch accounts for that.
>
> Mark
> --
Mark,
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.
Thanks
Brian
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-03 13:17 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 [this message]
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
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=36b714c804080306175c5dc3f6@mail.gmail.com \
--to=linwoes@gmail.com \
--cc=adrian@humboldt.co.uk \
--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 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).