From: Derek Fawcus <dfawcus@cisco.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pathetic
Date: Thu, 26 Feb 2004 15:37:36 +0000 [thread overview]
Message-ID: <20040226153735.A20891@edinburgh.cisco.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402250822260.9147-100000@maxroach.lanl.gov>; from rminnich@lanl.gov on Wed, Feb 25, 2004 at 08:26:01AM -0700
On Wed, Feb 25, 2004 at 08:26:01AM -0700, ron minnich wrote:
>
> golly. seperate I&D space. Which is an idea that is only about 40 or so
> years old (Burroughs 5500 ... or am I late even with that).
Back to the point... It would be possible to implement seperate I&D on
existing x86, but only for a limited set of programs: those without
(certain types of) shared libraries.
Set a code segment to have the required length, base 0.
Set a decending data segment to the required length, top ffffffff
Mind one then has to fiddle with segment descriptors, which may mean
LDTs or 'interesting' set's entries in the GDT.
DF
prev parent reply other threads:[~2004-02-26 15:37 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 15:26 ron minnich
2004-02-25 15:41 ` Derek Fawcus
2004-02-25 16:02 ` ron minnich
2004-02-26 1:15 ` Derek Fawcus
2004-02-26 3:45 ` ron minnich
2004-02-26 4:12 ` Derek Fawcus
2004-02-26 6:48 ` boyd, rounin
2004-02-26 6:41 ` boyd, rounin
2004-02-25 16:26 ` Aharon Robbins
2004-02-26 6:02 ` boyd, rounin
2004-02-26 10:41 ` Douglas A. Gwyn
2004-02-26 11:32 ` Charles Forsyth
2004-02-26 11:33 ` Geoff Collyer
2004-02-26 12:39 ` Dave Lukes
2004-02-26 12:11 ` boyd, rounin
2004-02-26 13:42 ` dbailey27
2004-02-26 14:36 ` ron minnich
2004-02-26 14:41 ` David Presotto
2004-02-26 14:40 ` dbailey27
2004-02-26 14:47 ` ron minnich
2004-02-26 14:44 ` dbailey27
2004-02-26 15:28 ` ron minnich
2004-02-26 15:38 ` George Michaelson
2004-02-26 16:16 ` ron minnich
2004-02-26 17:32 ` [9fans] SPF+SMTP C H Forsyth
2004-03-01 10:34 ` [9fans] pathetic Vin McLellan
2004-02-26 15:38 ` dbailey27
2004-02-26 14:58 ` andrey mirtchovski
2004-02-26 15:53 ` dbailey27
2004-02-27 9:01 ` boyd, rounin
2004-02-27 10:52 ` Geoff Collyer
2004-02-27 13:07 ` David Presotto
2004-02-27 20:26 ` Lyndon Nerenberg
2004-02-27 22:22 ` Tristan Seligmann
2004-02-27 23:36 ` Geoff Collyer
2004-02-27 13:42 ` Dave Lukes
2004-02-27 15:42 ` a
2004-02-27 17:45 ` 9nut
2004-02-27 23:10 ` boyd, rounin
2004-02-29 21:11 ` boyd, rounin
2004-02-26 15:16 ` C H Forsyth
2004-02-26 15:37 ` Dave Lukes
2004-02-26 17:55 ` jmk
2004-02-26 19:23 ` Richard Miller
2004-02-26 19:35 ` jmk
2004-02-26 19:50 ` Richard Miller
2004-02-27 11:04 ` Dan Moniz
2004-02-26 20:46 ` boyd, rounin
2004-02-26 15:37 ` Derek Fawcus [this message]
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=20040226153735.A20891@edinburgh.cisco.com \
--to=dfawcus@cisco.com \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).