From: "David S. Miller" <davem@jenolan.rutgers.edu>
To: law@cygnus.com
Cc: burley@gnu.ai.mit.edu, egcs@cygnus.com
Subject: Re: Some Haifa scheduler bugs
Date: Thu, 04 Sep 1997 11:33:00 -0000 [thread overview]
Message-ID: <199709041832.OAA10124@jenolan.rutgers.edu> (raw)
In-Reply-To: <27136.873396735@hurl.cygnus.com>
Date: Thu, 04 Sep 1997 12:12:15 -0600
From: Jeffrey A Law <law@hurl.cygnus.com>
I'm less familiar with how this works under aix or with
ultrasparcs/solaris, but I assume they both do something relatively
reasonable.
On the UltraSparc normal load/store instructions still trap on bogus
pointers like they always have.
The compiler must emit a special load instruction (with an address
space specifier for the "no-fault" address space) when it wants a
speculative load. The chip will not fault on a NULL pointer if page 0
of the process has the "allow non-faulting load" attribute set, when
you use these special load instructions. Non-faulting stores do not
exist.
Naturally, this depends upon OS support, and I think Solaris does map
page 0 in this special way, or they check the load instruction which
was executed by the user once the fault handling call chain determines
that the access was in outer space.
I lack the support currently on sparc64-linux, but it will be added
should a native compiler out there begin to emit the instructions ;-)
Later,
David "Sparc" Miller
davem@caip.rutgers.edu
next prev parent reply other threads:[~1997-09-04 11:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOL.3.90.970826140826.2901J-100000@maigret.informatik.rwth-aachen.de>
1997-09-01 20:33 ` Jeffrey A Law
1997-09-03 9:30 ` Bernd Schmidt
1997-09-03 9:37 ` Jeffrey A Law
1997-09-03 9:44 ` Bernd Schmidt
1997-09-03 10:07 ` Jeffrey A Law
1997-09-05 7:15 ` Bernd Schmidt
1997-09-05 7:55 ` Jeffrey A Law
1997-09-05 8:33 ` Ian Lance Taylor
1997-09-03 11:58 ` Jim Wilson
1997-09-04 1:16 ` regparm & other gcc bug Martynas Kunigelis
1997-09-05 9:29 ` Kamil Iskra
1997-09-06 5:19 ` Martynas Kunigelis
1997-09-03 11:39 ` Some Haifa scheduler bugs Paul Koning
1997-09-03 11:50 ` David Edelsohn
1997-09-03 13:13 ` Richard Henderson
1997-09-03 13:19 ` Jeffrey A Law
1997-09-04 9:33 ` Craig Burley
1997-09-04 11:12 ` Jeffrey A Law
1997-09-04 11:33 ` David S. Miller [this message]
1997-09-04 14:38 ` David Edelsohn
1997-09-04 11:27 meissner
[not found] <Pine.SOL.3.90.970826141030.2901K-100000@maigret.informatik.rwth-aachen.de>
1997-09-01 20:42 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1997-08-26 14:34 Bernd Schmidt
1997-08-22 13:53 Building of generated parser files Andreas Schwab
1997-08-22 15:02 ` Some Haifa scheduler bugs Jeffrey A Law
1997-08-22 15:24 ` Jeffrey A Law
1997-08-22 10:48 Building of generated parser files Niklas Hallqvist
1997-08-22 13:28 ` Some Haifa scheduler bugs Bernd Schmidt
1997-08-21 16:51 Problems on PowerPC David Edelsohn
1997-08-21 17:43 ` Some Haifa scheduler bugs Jeffrey A Law
1997-08-21 15:20 egcs repository Joel Sherrill
1997-08-21 15:47 ` Some Haifa scheduler bugs Bernd Schmidt
1997-08-19 19:00 Jeffrey A Law
1997-08-19 17:54 Jeffrey A Law
1997-08-19 7:36 egcs: A new compiler project to merge the existing GCC forks (fwd) Robert Wilhelm
1997-08-19 9:34 ` Some Haifa scheduler bugs Bernd Schmidt
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=199709041832.OAA10124@jenolan.rutgers.edu \
--to=davem@jenolan.rutgers.edu \
--cc=burley@gnu.ai.mit.edu \
--cc=egcs@cygnus.com \
--cc=law@cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).