Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] PA8800/ZX1 support committed to 2.6.7-rc2-pa2
Date: 11 Jun 2004 10:02:29 -0400	[thread overview]
Message-ID: <1086962549.1949.23.camel@mulgrave> (raw)
In-Reply-To: <20040611055819.GA32005@colo.lackof.org>

> Changing "4 + cnf.cc_shift" (stride=128) to "3 + cnf.cc_shift"
> (stride=64) didn't help. This implies the stride is not the problem.

The stride in the rest of the PA architecture is either 16 or 32; I'd be
surprised if the L1 stide in the 8800 were bigger (smaller stride is
actually more efficient since it gives finer control over caching).

Could you just hard code it to 32 to make assureances certain that the
stride value isn't the source of the segv's?

Thanks,

James


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

  reply	other threads:[~2004-06-11 14:02 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
2004-06-11  5:58         ` Grant Grundler
2004-06-11 14:02           ` James Bottomley [this message]
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=1086962549.1949.23.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=grundler@parisc-linux.org \
    --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