KS11 Memory Protection and Relocation option - Revision history

Jnc: /* External links */ Update Bell Labs URLs (blast Nokia)

2025-06-30T18:45:30Z

‎External links: Update Bell Labs URLs (blast Nokia)

Jnc: /* Hardware registers */ Retrieve some KSS bits

2024-02-29T15:58:02Z

‎Hardware registers: Retrieve some KSS bits

Larsbrinkhoff: Some information from MIMIC.

2024-02-29T11:17:23Z

Some information from MIMIC.

Jnc: More accurate description

2023-05-18T18:38:43Z

More accurate description

Jnc: Amazing how much soup one can make from two _small_ stones

2023-05-18T15:37:28Z

Amazing how much soup one can make from two _small_ stones

New page

The '''KS11 Memory Protection and Relocation option''' was a [[UNIBUS]] option which was apparently [[Digital Equipment Corporation|DEC]]'s first attempt at an add-on to provide [[memory management]] for the [[PDP-11/20]]. (Starting with the next [[PDP-11]] model, the [[PDP-11/45]], memory management was standard, so the KS11 became obsolete.) It was almost certainly produced by DEC's Computer Special Systems group.

All documentation on the KS11 has been lost, so other than the name (below), and an amusing story (ditto), almost nothing is known of it for certain. (The story does reveal that [[Bell Laboratories]]' KS11 must have been one of the first ones built; certainly the first one used with a [[KE11-A Extended Arithmetic Element|KE11-A]].) A very early [[assembly language]] version of [[UNIX]], probably [[UNIX Second Edition]] ([[UNIX Third Edition]] had apparently already moved on to the -11/45) used it, but unfortunately that version has been completely lost, otherwise it would be possible to work out from inspecting the [[source code]] much of how the KS11 worked.

From the story of the implementation error on handling the KE11-A (an ordinary UNIBUS device, in implementation), the KS11 was apparently not part of the [[Central Processing Unit|CPU]], but a UNIBUS active repeater, placed between the UNIBUS leaving the CPU, and the [[main memory]] and [[peripheral|devices]] on the rest of the the UNIBUS (in the same manner as the [[KT11-B Paging Option]]).

In addition, several other things about the KS11 can be deduced from what we do know. The name indicates that it proved both ''protection'' (i.e. it limited the bus [[address]]es to which the [[user]] could reference), and also ''relocation'' (i.e. the [[address space]] visible to the user was not just main memory, as visible to the CPU, but could be moved elsewhere in main memory).

It is not known whether the KS11 also allowed use of more than 56KB of main memory, the capacity of an ordinary -11/20, by mapping part of the UNIBUS address space which the -11/20 CPU ''can'' see (i.e. in the 0-56KB range) up to higher addresses, where 'extra' memory is configured. Such a capability would have been trivial to add to something with the KS11's known capabilities, but some one-time users think use of an [[MX11-A Memory Extension Control|MX11]] might have been needed to add extra main memory.

From memories of several people who worked with the KS11, apparently it did what the [[KA10]] MMU did, i.e. divide the user's address space into two [[segment]]s, which could be managed independently. The two segments apparently grew towards each other, in the address space, but were stored contiguously in main memory. In addition to mapping addresses around, the KS11 also definitely limited user access to so-called [[UNIBUS|I/O page]] addresses.

It also reportedly supported some sort of user/kernel mode distinction, which might have require a tie-in to the CPU. But not necessarily; if there was a [[flip-flop]] in the KS11 which stored the 'CPU mode' bit, it might be automatically cleared (if being set meant 'in user mode') on all [[interrupt]]s (which can be seen on the UNIBUS). It is not clear how such a thing would have handled [[trap]]s, though (for that, the KT11-B used a link to the [[KA11 CPU]], to which minor changes were made). The 'Option and Module List' indicates that the KS11 was only for the -11/20, which might indicate it did have such a tie-in.

==See also==

* [[MX11-A Memory Extension Control]]

==External links==

* [https://www.bell-labs.com/usr/dmr/www/odd.html Odd Comments and Strange Doings in Unix] - contains a story about an amusing KS11 bug (Section "A hardware story")
* [http://www.bitsavers.org/pdf/dec/modules/modulesAndOptions/Options_and_Modules_List_197503.pdf Option and Module List] - listed here, as "Mem Protect & Relocate"

[[Category: PDP-11 UNIBUS Processors]]

@@ Line 35: / Line 35: @@
 |-
 | KSRW || Relocation window
 |}

← Older revision		Revision as of 11:17, 29 February 2024
Line 12:		Line 12:

	It also reportedly supported some sort of user/kernel mode distinction, which might have require a tie-in to the CPU. But not necessarily; if there was a [[flip-flop]] in the KS11 which stored the 'CPU mode' bit, it might be automatically cleared (if being set meant 'in user mode') on all [[interrupt]]s (which can be seen on the UNIBUS). It is not clear how such a thing would have handled [[trap]]s, though (for that, the KT11-B used a link to the [[KA11 CPU]], to which minor changes were made). The 'Option and Module List' indicates that the KS11 was only for the -11/20, which might indicate it did have such a tie-in.		It also reportedly supported some sort of user/kernel mode distinction, which might have require a tie-in to the CPU. But not necessarily; if there was a [[flip-flop]] in the KS11 which stored the 'CPU mode' bit, it might be automatically cleared (if being set meant 'in user mode') on all [[interrupt]]s (which can be seen on the UNIBUS). It is not clear how such a thing would have handled [[trap]]s, though (for that, the KT11-B used a link to the [[KA11 CPU]], to which minor changes were made). The 'Option and Module List' indicates that the KS11 was only for the -11/20, which might indicate it did have such a tie-in.
		+
		+	==Hardware registers==
		+
		+	From definitions in [[MIMIC]], we gather the KS11 had eight 16-bit registers.
		+
		+	{\| class="wikitable"
		+	! Name \|\| Description
		+	\|-
		+	\| KSS \|\| Status
		+	\|-
		+	\| KSPL \|\| Low segment protection
		+	\|-
		+	\| KSRL \|\| Low segment relocation
		+	\|-
		+	\| KSPH \|\| High segment protection
		+	\|-
		+	\| KSRH \|\| High segment relocation
		+	\|-
		+	\| KSPC \|\| PC save
		+	\|-
		+	\| KSAD \|\| Relocation window address
		+	\|-
		+	\| KSRW \|\| Relocation window
		+	\|}
		+
		+	A "protection block" is 64 bytes. The "high segment" begins at address 100000 (octal).
		+
		+	In the protection registers, bit 0 means "write protect". Bit 1 in KSPL means "user trap select".

	==See also==		==See also==

@@ Line 59: / Line 59: @@
 ==External links==
-* [https://www.bell-labs.com/usr/dmr/www/odd.html Odd Comments and Strange Doings in Unix] - contains a story about an amusing KS11 bug (Section "A hardware story")
+* [https://www.nokia.com/bell-labs/about/dennis-m-ritchie/odd.html Odd Comments and Strange Doings in Unix] - contains a story about an amusing KS11 bug (Section "A hardware story")
 * [http://www.bitsavers.org/pdf/dec/modules/modulesAndOptions/Options_and_Modules_List_197503.pdf Option and Module List] - listed here, as "Mem Protect & Relocate"
 [[Category: PDP-11 UNIBUS Processors]]

@@ Line 3: / Line 3: @@
 All documentation on the KS11 has been lost, so other than the name (below), and an amusing story (ditto), almost nothing is known of it for certain. (The story does reveal that [[Bell Laboratories]]' KS11 must have been one of the first ones built; certainly the first one used with a [[KE11-A Extended Arithmetic Element|KE11-A]].) A very early [[assembly language]] version of [[UNIX]], probably [[UNIX Second Edition]] ([[UNIX Third Edition]] had apparently already moved on to the -11/45) used it, but unfortunately that version has been completely lost, otherwise it would be possible to work out from inspecting the [[source code]] much of how the KS11 worked.
-From the story of the implementation error on handling the KE11-A (an ordinary UNIBUS device, in implementation), the KS11 was apparently not part of the [[Central Processing Unit|CPU]], but a UNIBUS active repeater, placed between the UNIBUS leaving the CPU, and the [[main memory]] and [[peripheral|devices]] on the rest of the the UNIBUS (in the same manner as the [[KT11-B Paging Option]]).
+From the story of the implementation error on handling the KE11-A (an ordinary UNIBUS device, in implementation), the KS11 was apparently not part of the [[Central Processing Unit|CPU]], but a UNIBUS active repeater, placed in the UNIBUS between the CPU, and the [[main memory]] and [[peripheral|devices]] on the rest of the the UNIBUS (in the same manner as the [[KT11-B Paging Option]]).
-In addition, several other things about the KS11 can be deduced from what we do know. The name indicates that it proved both ''protection'' (i.e. it limited the bus [[address]]es to which the [[user]] could reference), and also ''relocation'' (i.e. the [[address space]] visible to the user was not just main memory, as visible to the CPU, but could be moved elsewhere in main memory).
+In addition, several other things about the KS11 can be deduced from what little we do know. The name indicates that it proved both ''protection'' (i.e. it limited the bus [[address]]es to which the [[user]] could reference), and also ''relocation'' (i.e. the [[address space]] visible to the user was not just main memory, as visible to the CPU, but could be moved elsewhere in main memory).
 It is not known whether the KS11 also allowed use of more than 56KB of main memory, the capacity of an ordinary -11/20, by mapping part of the UNIBUS address space which the -11/20 CPU ''can'' see (i.e. in the 0-56KB range) up to higher addresses, where 'extra' memory is configured. Such a capability would have been trivial to add to something with the KS11's known capabilities, but some one-time users think use of an [[MX11-A Memory Extension Control|MX11]] might have been needed to add extra main memory.