From: Benjamin Herrenschmidt <bh40@calva.net>
To: Paul.Mackerras@cs.anu.edu.au, linuxppc-dev@lists.linuxppc.org
Subject: Re: Thoughts about DBDMA and cache coherency
Date: Fri, 19 Mar 1999 00:41:54 +0100 [thread overview]
Message-ID: <19990319004154.018461@mail.mipsys.com> (raw)
In-Reply-To: <199903182331.KAA23199@tango.anu.edu.au>
On Fri, Mar 19, 1999, Paul Mackerras <paulus@cs.anu.edu.au> wrote:
>No, what happens (on the 60x bus) is that the read is snooped by the
>cache controller, which asserts a `backoff and retry' signal. The
>PCI bridge then terminates the transaction, the cache controller gets
>the 60x bus and writes the cache line out to memory, then the PCI
>bridge retries the read and gets the right data from memory.
Ok, thanks for the clarification.
>One small wrinkle is that for all this to work, the bridge has to
>assert the GBL (global) signal for all its accesses. On some
>Starmaxes, we weren't getting the cache coherency maintained, but
>someone (Harry Eaton, from memory) found a bit to set in the bridge's
>configuration space which turned on the cache coherency - most likely
>this bit controlled whether the GBL signal was asserted or not.
I beleive MacOS can run without it (MacOS probably assumes cache coherency
is not here since it makes DMA space uncachable).
>> That would mean that we need to flush the range occupied by DBDMA
>> descriptors, but also any buffers used by DBDMA when outputing via a
>> DBDMA channel.
>
>Fortunately we don't need to, on PCI powermacs at least. As I said,
>nubus powermacs are a whole 'nother can of worms, as are 68k macs.
Hum, asun will have fun making them work... and I too since I promised I would
help fixing head.S and kernel mappings...
>> Either I missed something big, either linux fails to do so and may have
>> unreliable writes to DBDMA devices all the time (looks like it would
>> crash a lot more often than it does, I must be wrong somewhere).
>
>It would crash a lot more often. Things just basically wouldn't work.
Yep
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-18 23:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-18 23:16 Thoughts about DBDMA and cache coherency Benjamin Herrenschmidt
1999-03-18 23:31 ` Paul Mackerras
1999-03-18 23:41 ` Benjamin Herrenschmidt [this message]
1999-03-20 17:02 ` egcs 1.1.2 big improvement over egcs 1.1.1 ! Kevin B. Hendricks
1999-03-22 17:59 ` Franz Sirl
1999-03-22 19:38 ` smbfs and smbmount and Paul's 2.2.1 kernel Kevin B. Hendricks
1999-03-23 12:27 ` 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=19990319004154.018461@mail.mipsys.com \
--to=bh40@calva.net \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=linuxppc-dev@lists.linuxppc.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 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.