From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] pdp11 UNIX memory allocation.
Date: Tue, 6 Jan 2015 17:00:20 -0500 [thread overview]
Message-ID: <CAC20D2M3s76LGqj77kH8bhmyUZ4E9b79iza45Q-O9m+CnJrwcQ@mail.gmail.com> (raw)
In-Reply-To: <5E62DDAA-0055-46FB-8077-92DB856DEEE0@ronnatalie.com>
Right - that's how the kernel set up the page tables for the user processes.
On Tue, Jan 6, 2015 at 4:57 PM, Ronald Natalie <ron at ronnatalie.com> wrote:
>
> > On Jan 6, 2015, at 3:33 PM, random832 at fastmail.us wrote:
> >
> > Was it possible to read/write to the instruction space, or execute the
> > data space?
>
> In split I/D mode (411) magic number. It is imposible to execute in D
> space or use regular data access instructions to access i-space. The
> addresses are in completely different spaces (i.e, 0 in data is mapped to
> different memory than 0 in instruction space). Some access at the kernel
> level can be done with MFPI and MPFD instructions.
>
> In write protected, non-split more (410 magic), you could read the I space
> and you could jump in to D space. You were prohibited to write the i
> space.
>
> In non protected mode (407 magic) everything was fair game.
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150106/2c5538dc/attachment.html>
next prev parent reply other threads:[~2015-01-06 22:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.147.1420574271.3354.tuhs@minnie.tuhs.org>
2015-01-06 20:20 ` Johnny Billquist
2015-01-06 20:33 ` random832
2015-01-06 21:57 ` Ronald Natalie
2015-01-06 22:00 ` Clem Cole [this message]
2015-01-06 22:04 ` Ronald Natalie
2015-01-07 1:46 ` Dave Horsfall
2015-01-07 2:00 ` Ronald Natalie
2015-01-07 6:29 ` Dave Horsfall
2015-01-07 6:39 ` Warren Toomey
2015-01-07 10:06 ` Brantley Coile
2015-01-07 13:29 ` Jacob Ritorto
[not found] ` <CAC20D2PP1hGyYsep1yNtj9KO55a-V02+QHS+S7bX-4joJy222g@mail.gmail.com>
[not found] ` <1420583703.863814.210431037.61D6C6EC@webmail.messagingengine.com>
2015-01-06 22:36 ` random832
[not found] <mailman.149.1420581544.3354.tuhs@minnie.tuhs.org>
2015-01-06 22:20 ` Johnny Billquist
2015-01-06 22:36 ` Ronald Natalie
2015-01-06 23:14 ` Johnny Billquist
2015-01-07 2:39 ` John Cowan
2015-01-07 2:59 ` Johnny Billquist
2015-01-06 22:45 Noel Chiappa
2015-01-06 22:55 ` Clem Cole
[not found] <mailman.151.1420584979.3354.tuhs@minnie.tuhs.org>
2015-01-06 23:34 ` Johnny Billquist
2015-01-06 23:52 ` scj
2015-01-07 16:14 ` Clem Cole
2015-01-07 17:27 ` Dave Horsfall
2015-01-07 2:18 Noel Chiappa
2015-01-07 16:17 ` Clem Cole
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=CAC20D2M3s76LGqj77kH8bhmyUZ4E9b79iza45Q-O9m+CnJrwcQ@mail.gmail.com \
--to=clemc@ccc.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 NNTP newsgroup(s).