Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] PA8800/ZX1 support committed to 2.6.7-rc2-pa2
Date: Sat, 5 Jun 2004 16:21:37 -0600	[thread overview]
Message-ID: <20040605222137.GF8098@colo.lackof.org> (raw)
In-Reply-To: <1086470366.1999.36.camel@mulgrave>

On Sat, Jun 05, 2004 at 04:19:24PM -0500, James Bottomley wrote:
> On Sat, 2004-06-05 at 16:05, Grant Grundler wrote:
> The pa8800 only has a 750k/750k VIPT cache, that's smaller than my
> raven.  The 32M L2 cache is PIPT, which doesn't suffer from aliasing or
> address remapping effects---in fact, the PA engineers probably arranged
> for a fdc not to flush it because there's no point; the only coherency
> problems the PIPT cache has is with I/O, which is supposed to be fully
> coherent in the ZX1, isn't it.

Yes - especially since I haven't attempted to add any special support
for 64-bit cards. The "IOMMU Bypass" mode on ZX1 is worth implementing
for 64-bit cards and I might in fact require it for graphics and
infiniband support.


> Thus, we'd only pick up a caching
> problems like you describe from the VIPT caches.

ok.

> > Any good ideas on how to prove IO is coherent?
> 
> Well, yes, but not without driver magic.  You program a device to take a
> piece of data in and rewrite it to a different buffer, then you compare
> buffers (making sure the first had a pattern in it and the second was
> completely clear).

tg3 driver infact has such a test...let me think about that some more.
I might hack the test to be more exhaustive.

> Well, it could be an I/O coherency problem, but if you have one of
> those, I'm surprised it boots at all.

For that bug, one could occasionally end up with a stale IO TLB entry.
And I'm wondering if that's possible when "swapping in" different
parts of an executable binary. To date, I'm under the impression
only executable pages are seeing this problem.  If it were IO,
I should be seeing it with data too - ie .c file cause errors.
Maybe I just need to exercize it more to make that happen.

thanks,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-06-05 22:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 20:25 [parisc-linux] PA8800/ZX1 support committed to 2.6.7-rc2-pa2 Grant Grundler
2004-06-05  6:51 ` Grant Grundler
2004-06-05 14:10   ` James Bottomley
2004-06-05 21:05     ` Grant Grundler
2004-06-05 21:19       ` James Bottomley
2004-06-05 22:21         ` Grant Grundler [this message]
2004-06-11  5:58         ` Grant Grundler
2004-06-11 14:02           ` James Bottomley
2004-06-11 15:03             ` Grant Grundler
2004-06-11 15:27             ` Grant Grundler
2004-06-12  0:38           ` Jim Hull
2004-06-14 18:29             ` Grant Grundler
2004-06-14 22:45               ` Jim Hull
2004-06-14 23:42                 ` Grant Grundler

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=20040605222137.GF8098@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=parisc-linux@lists.parisc-linux.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