Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: rwhaley@cs.utk.edu, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: atlas3 on hppa: unexpected reloc type
Date: Mon, 14 Jun 2004 08:51:18 -0700	[thread overview]
Message-ID: <20040614155118.GL19250@tausq.org> (raw)
In-Reply-To: <200406140232.i5E2W5Bg003075@hiauly1.hia.nrc.ca>

> > Cool! Be aware that, if atlas relies on being able to prefetch invalid
> > addresses and have that not fault, then it will only work on some PA 
> > processors (mostly pa20) and not all of them.
> 
> Are you sure this doesn't apply to all pa20 processors?  See page 6-11
> in PA-RISC 2.0 Architecture book.

It does work on all pa20 processors, afaik. Let me rephrase:

"Be aware that, if atlas relies on being able to prefetch invalid
addresses and have that not fault, then it will only work on some PA 
processors but not all of them. All pa20 processors should work.
pa11 processors will not."

We ran into this while trying to get PA7300LC to do prefetching in the
kernel.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-06-14 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040613162317.E51E44F24E@enterprise.cs.utk.edu>
2004-06-13 22:33 ` [parisc-linux] Re: atlas3 on hppa: unexpected reloc type Randolph Chung
2004-06-14  2:32   ` John David Anglin
2004-06-14 15:51     ` Randolph Chung [this message]
2004-06-14 20:53 R Clint Whaley
2004-06-14 21:06 ` Matthew Wilcox

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=20040614155118.GL19250@tausq.org \
    --to=tausq@debian.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=rwhaley@cs.utk.edu \
    /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