GB2127994A - Memory management unit for digital computer - Google Patents

Memory management unit for digital computer Download PDF

Info

Publication number
GB2127994A
GB2127994A GB08316129A GB8316129A GB2127994A GB 2127994 A GB2127994 A GB 2127994A GB 08316129 A GB08316129 A GB 08316129A GB 8316129 A GB8316129 A GB 8316129A GB 2127994 A GB2127994 A GB 2127994A
Authority
GB
United Kingdom
Prior art keywords
mmu
memory
main memory
addresses
stored
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
GB08316129A
Other versions
GB8316129D0 (en
GB2127994B (en
Inventor
Paul A Baker
Gary L Marten
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Computer Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Computer Inc filed Critical Apple Computer Inc
Publication of GB8316129D0 publication Critical patent/GB8316129D0/en
Publication of GB2127994A publication Critical patent/GB2127994A/en
Application granted granted Critical
Publication of GB2127994B publication Critical patent/GB2127994B/en
Expired legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02Addressing or allocation; Relocation
    • G06F12/0223User address space allocation, e.g. contiguous or non contiguous base addressing
    • G06F12/0292User address space allocation, e.g. contiguous or non contiguous base addressing using tables or multilevel address translation means
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/14Protection against unauthorised use of memory or access to memory
    • G06F12/1416Protection against unauthorised use of memory or access to memory by checking the object accessibility, e.g. type of access defined by the memory independently of subject rights
    • G06F12/145Protection against unauthorised use of memory or access to memory by checking the object accessibility, e.g. type of access defined by the memory independently of subject rights the protection being virtual, e.g. for virtual blocks or segments before a translation mechanism

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Storage Device Security (AREA)
  • Techniques For Improving Reliability Of Storages (AREA)
  • Memory System (AREA)
  • Memory System Of A Hierarchy Structure (AREA)

Abstract

An improved memory management unit (MMU) for interfacing between a CPU and a main computer memory to convert logical addresses to physical addresses. The MMU's memory 20 provides sufficient capacity to permit relocation data and limit data to be stored for a plurality of processes, and thus, allows several programs to be run without reprogramming the MMU. Special "access" bits are also stored in the MMU's memory which, by way of example, prevent the writing into program, accessing of unselected processes or user access to certain memory locations to prevent, for instance, the copying of an operating system. <IMAGE>

Description

SPECIFICATION Memory management unit for digital computer The invention relates to the field of computer memories and units for managing the contents of such memories.
In most computers, a central processing unit (CPU) communicates directly with both an address bus and a data bus. These buses are coupled to a main memory (or main memory systems) in addition to numerous other items such as input/output ports, specialized processors, DMA units, etc. The main computer memory is often the most expensive component of the computer, particularly when compared to the price of currently available microcomputer CPUs such as the 8080, 8086, 6800 and 68000. Thus, it is important to efficiently utilize the computer's main memory.
Memory management units (MMUs) are used in the prior art to provide efficient utilization of the computer's main memory. These units perform housekeeping functions such as remapping, etc. Often, an MMU includes a memory which stores a data relocation base. The higher order bits of the logical address from by the CPU are used to address the MMU's memory. These bits from the CPU's standpoint, for instance, select a segment of the main memory. The selected CPU segment number is replaced by a new number from the MMU's memory and effectively, a relocation occurs between the logical address from the CPU and the physical address used to access the main memory.
Another function performed by prior art MMUs is to check addresses from the CPU to verify that they fall within certain ranges. A limit number stored in the MMU's memory is compared with lower order bits of the logical address (for example, the page offset) to ensure that the page offset falls within a predetermined address range of the selected segment number. This prevents, by way of example, the accidental reading of "data" from memory locations where date has not been placed.
The present invention builds upon those prior art MMUs which provide a relocation base and address range verification. As will be seen, the MMU's memory is expanded in one direction to store signals representing the nature of information stored in the main memory. This is used to control access to the main memory and, by way of illustration, prevents accidental writing into programs and user access to operating systems. The MMU's memory is expanded in another direction so that overlapping memory management is provided. This allows several different processes (program and data) to be run by the computer without reprogramming the MMU memory.
An improved memory management unit (MMU) is described for use with a computer which includes a central processing unit (CPU) and a main memory. The MMU includes a relocation base and when receiving first address signals from the CPU, provides second address signals for accessing the memory. The MMU also includes storage means for receiving and storing signals respresentative of the types of information stored in locations in the main memory. Accessing means are provided for accessing these stored signals when the corresponding locations are accessed in the main memory. The stored signals from the storage means are coupled to the main memory to, for example, limit access of certain types of data in the memory such as operating systems. The signals may be also used to permit reading-only of programs, and reading and writing of data.
In the presently preferred embodiment, the storage means is an integral part of the MMU's memory. The MMU's memory has four times the capacity than is needed to provide relocation base numbers and limit numbers for the entire main memory. As will be described, this additional capacity permits a form of "bank switching" and allows different processes to be run on the computer without reprogramming of the MMU memory.
The present invention will be further illustrated, by way of example, with reference to the accompanying drawings, in which: Figure 1 is a general block diagram illustrating a central processing unit, memory management unit (MMU) and main memory and their interconnections in a computer; Figure2 is a diagram illustrating the organization of data stored in the memory of the invented MMU; Figure 3 is a block diagram of the invented MMU; and Figure 4 is a diagram used to described the different contexts used in the operation of the MMU and the resultant organization of information stored in the computer's main memory.
A memory management unit (MMU) is described for use in a digital computer which includes a central processing unit (CPU) and a main memory. In the following description, numerous specific details are set forth such as specific memory sizes, part numbers, etc., in order to provide a thorough understanding of the present invention.. However, it will be obvious to one skilled in the art that these specific details are not required to practice the present invention. In other instances, well-known structures and circuits are not described in details in order to obscure the present invention in unnecessary detail.
Referring first to Figure 1, the coupling between an MMU, CPU and main memory is illustrated. This coupling is somewhat the same for the present invention as it is for the prior art. The computer of Figure 1 includes a bidirectional data bus 16 which communicates with the CPU 10, main memory 14 and the MMU 12. The address bus 18 receives address signals from the CPU 10 and communicates part of these addresses to the MMU 12 and part to the main memory 14. Other control signals are coupled between the CPU 10 and MMU as illustrated by lines 35 and 37 and between the MMU 12 and the main memory 14 as shown by line 57.
The MMU 12 is programmed from the CPU 10 through the data bus 16. Addresses are communicated over the bus 18 to the MMU from the CPU 10 to allow the loading ofthe MMU 12.
In the presently preferred embodiment, the CPU 10 comprises a 68000 processor. For this processor, the CPU 10 provides 24 bit addresses. (Actually, the lowest order bit is not physically present as such but encoded into other signals, however, for purposes of discussion, it will be assumed to be an ordinary address bit). Also, for purposes of discussion, it will be assumed that the 7 highest order bits of each logical address from the CPU selects a segment in memory, the next 8 lesser significant bits comprise a page offset, and the least significant 9 bits, an offset.
In the presently preferred embodiment, the segment and page offset of each address are coupled to the MMU 12. The MMU provides a relocation base by exchanging the segment number from the CPU 10 with a segment number stored in the MMU 12. Specifically, the segment number from the CPU 10 addresses a memory within the MMU 12 and this memory provides a segment base used to address the main memory 14. The page offset portion of the address from the CPU 10 is checked to determine if the page offset falls within a predetermined range of the segment. This, for instance, would prevent the reading and interpreting as data, all zeros from an unused space in main memory. The segment base from the MMU along with the page offset are added and then coupled to the main memory 14 on the bus 18a and 18b of Figure 1.The 9 least significant bits are passed directly from the CPU to the main memory via bus 18c.
Referring now to Figure 3, the presently preferred embodiment of the MMU includes an MMU memory 20.
This memory is a ramdom-access memory fabricated from commercially available MOS static RAMs. As currently implemented, three Part No. 2148 RAMs are used for memory 20, thus providing a total capacity of 12k bits. The organization of the MMU memory is discussed in greater detail, particularly in conjunction with Figure 2.
The address from the CPU is shown as the 24 bit address (logical address) in the uppermost part of Figure 3. The 7 most significant bits of this address are coupled to the MMU's memory via bus 18a and are used to address the MMU's memory. The next most significant bits (bus 18b) are coupled to an adder 27, and the least significant 9 bits (offset) are coupled via bus 18coo register 18. The output of the MMU's memory 20 consists of two 12-bit words (buses 22 and 23). These words are coupled through the multiplexer 25 to the 12-bit bus 30. One of the 12 bit words from the memory 20 provides the segment base from the stored relocation base. The second 12 bits consist of 8 bits for limit checking of the page offset and 4 additional bits which perform functions which are part of the present invention.
(In the presently preferred embodiment, multiplexer 25 does not physically exist, rather the output of memory 20 is time division multiplexed. However, for purposes of explanation it is easier to include the multiplexer 25).
The multiplexer 25 is also used to load information from the bus 16 into the memory 20. The signal on line 47 from the access check logic 40 provides access to the memory 20 as do the signals on line 35. The signal on line 37 controls the multiplexing of data between either the bus 22 or the bus 23.
The 12 bit bus 30 from the multiplexer 25 is coupled to the adder 27. This adder also receives the 8 bits on bus 18b. As will be described, the adder 27 is used to determine if the page offset falls within a predetermined range of the selected segment. The adder 27 also combines the relocation (segment base) from the MMU's memory with the page offset to provide the 12 most significant bits of the physical address.
These 12 bits along with the 9 bits from bus 1 8c are coupled to the register 28 to provide a 21 bit address which is communicated to the main memory 14. (The register 28 does not exist in the presently preferred embodiment, it is shown for purposes of explanation).
The 4 access check bits are coupled from the multiplexer 25 via line 45 to the access logic 40. Here the signals are decoded to provide main memory control and other control as follows: One bit controls the type of main memory access (1 = read only, = read/write). The second bit controls I/o access (1 = I/o,0 = no I/o access). The third bit controls main memory access (1 = memory acces, 0 = no main memory access). The fourth bit controls stacking (1 = stacking segment - check for no overflow, 0 = normal segment - check for overflow). The access check logic 40 is shown in Figure 3 coupled to the main memory control via line 57 to control memory access and the type of accesses permitted (i.e., read or read/write). Logic 40 is coupled to adder 27 via the overflow/carry in lines and to memory 20 via line 47 to enable memory 20 access.
The specific access control bit pattern used in the presently preferred embodiment is shown below.
Access Control Bits MEM/ 10/ RO/ STKI BITS ADDRESS SPACE AND ACCESS 0 1 0 0 Main Memory - Read Only Stack 0 1 0 1 Main Memory- Read Only 0 1 1 0 Main Memory - Read/Write Stack 0 1 1 1 Main Memory-Read/Write 1 1 0 0 1 I/O Space 1 1 0 0 Page Invalid (Segment not present) 1 1 1 1 Space Any Other Not allowed (unpredictable result) Assume first that the memory 20 has bee programmed from the CPU. For purposes of a first level explanation of the MMU's operation, the function of the 2 bits on lines 35 shall be ignored. When the CPU addresses the main memory, the most significant 7 bits address the MMU's memory 20.The 12 bits from the relocation data segment are coupled via bus 22 and bus 30 to the adder 27. There they are combined with the page offset (bus 18b) and the resultant address is combined with the 9 bits of the offset in the register 28 to provide the final physical address. This portion of the MMU operates in a manner quite similar to prior art MMUs. Thus, the relocation segment base data can be programmed into the memory (ignoring line 35) in a manner well-known in the prior art.
The 12 bits forming the limit and access data are coupled via bus 23 through the multiplexer 25. The 8 bits of the limit data are coupled to the adder 27. The 4 bits of the access data are coupled to logic 40 via line 45 as discussed. The limit data in the presently preferred embodiment is stored in ones complement form in the memory 20 for a non-stacked segment. For stacked segments the limit stored is "length minus one" (e.g. a two page segment would be stored as 0000 0001 in memory 20.) When this limit data is added to the page offset in adder 27, the result of this addition determines whether or not the page offset falls within the predetermined range of the segment. This is an improvement over prior art limit checking where additional logic steps are required.
Non-stack example Referring briefly to Figure 4, a representation of the computer's main memory 14 is illustrated. Assume that data is stored at locations 50. Further assume that the highest page offset (11111111) for data 50 extends to location 52, and that within this segment data extends to a page offset of 1110 0000 (line 51). For this page offset, the ones complement of 1110 0000 (0001 1111) is stored in the memory 20 of Figure 3. If this segment is addressed, and assuming the page offset address is 11111111 (that is, into the free space of the memory), adder 27 adds 11111111 to the stored number 0001 1111.An An overflow occurs from the adder 27 and this overflow condition is sensed by the logic 57 of Figure 3.For this example, an overflow indicates that the page offset is not within range and a signal is provided on line 57 to show that the addres is in error.
Logic 40 via line 57 prevents access to main memory and/or an error signal is generated.
Again referring to Figure 4, assume that a program is stored at locations 53 and that the highest page offset (11111111) for program 53 extends to location 50 which is outside of the actual program which ends at location 54. If the page offset for location 54 is 0011 0000 then 1100 1111 is stored within the memory 20 of Figure 3 for the segment which begins at location 55. If this segment is addressed and the page offset is 0000 0001, (addressing the program) the adder 27 adds 1100 1111 and 00000001. This time no overflow occurs and no signal is communicated to the logic 40, that is, access is permitted. Note that if the page offset is 0100 0000 (not within range) when this number is added to the stored number of 1100 1111 an overflow occurs.
This overflow indicates to the logic 40 that the page offset is not in range and memory access is disabled.
Stack example For some programming languages (e.g. Pascal) stacks (in memory) are very desirable. Stacks can be formed by moving data up in memory, albeit time consuming. Stacks with the presently described system are permitted to grow down in memory with a different limit checking procedure.
Assume a one page stack segment. The limit number stored in memory 20 as the one's compliment of the page offset (1111 1111 00000000) which is the same as the size minus one (0000 0001 00000000). The access check bits causes the logic 40 to provide a carry-in of one. If the page offset is 11111111, an overflow occurs. This overflow is sensed by logic 40, and interpreted as a valid (within range) condition. If the page offset were 1 1 1 1 1 1 10 (stack grown too much), no overflow occurs and this is interpreted as an out of range address.
Similarly, if the stack is a two page segment, 00000001 is stored in memory 20. Again the carry in is set to a one. A page offset of 11111110 would result in an overflow indicating an in range address, whereas with a page offset of 11111100 no overflow would occur, indicating an out of range address.
Figure 4 example Referring again to Figure 4, assume that a process (program and data) is stored in the main memory 14 between the locations 0 and 500 KB. The 3 remaining access bits in the memory 20 corresponding to the segment addresses for locations 0-500 KB are used to provide special control, as mentioned. For instance, for those segments containing only program, only reading of the memory is allowed. This, of course, prevents the inadvertent writing into program. Both reading and writing into the segments which contain data may be permitted. This is indicated to the right of program 59 and data 60 in Figure 4.
The memory 20 is programmed (i.e., access check bits) to prevent reading of some segments of the main memory except in certain modes (e.g., supervisory mode). This is done, for instance, to prevent a user from reading and then copying an operating system. Referring briefly to Figure 4, when the program 59 is being run, no access to memory 20 is permitted since such access could cause the relocation base, limit data or access data to be inadvertently altered. Thus, the four access bits provide protection for the program stored within the main memory and also limit access to certain information stored in the memory. In a typical application, an operating system is loaded from a disk into the main memory. Once in the main memory, the CPU can access the operating system in supervisory modes, however, the user is prevented from accessing and hence copying the operating system.
With the present invention, the memory 20 has four times the capacity than is actually needed to provide a relocation base, and limit and access data for the main memory. The signals from the CPU on lines 35 allow the selection of each quadrant of the memory 20. Each of these quadrants are referred to as a context (context 0-3) in the following description.
Referring to Figure 2, the organization of the MMU memory 20 is illustrated as four separate quadrants: 20a (context 0), 20b (context 1), 20c (context 2) and 20d (context 3). Context 1,2 and 3 are each organized in a 256x 12 bit arrangement (128x 12 bits for the relocation base and 128x 12 bits for the limit and access data).
Context 0 is selected by the CPU during the supervisory mode and this context stores management data relating to the operating system. It should be noted that each context is capable of storing information covering the entire main memory, thus there are three overlapping MMU memories for user processes.
The value of having these overlapping memories is best illustrated in Figure 4. The main memory 14 is shown programmed with three processes, PI, P2 and P3. Process 1 is stored between 0 and 500 KB, process 2 between 600 KB and 1 mB and process 3 between 1.2 mB and 1.5 m B. Data relating to the operating system is stored between 1.8 mB and 2 m B. Assume first that the operating system is loaded into memory and is stored between 1.8 mB and 2 m B. An appropriate relocation base is stored within the memory 20 such that during supervisory modes, the addresses 0-200 KB automatically select 1.8 mB through 2mB in the main memory. Also, the appropriate limits are loaded to assure that during the supervisory mode, the free space in the memory is not accessed.During the supervisory mode (context 0) as indicated in Figure 4 under the heading context 0, complete access to the MMU memory and main memory is possible (except for access bits which prevent the writing into the operating system stored in main memory thereby protecting the program from damage due to a program error). Since the MMU memory is accessible at this time, it can be programmed through the bus 16 as indicated in Figure 3, and as previously discussed.
Assume that context 1 is to be used for program 50 and data 60, one quadrant of the MMU's memory 20 corresponding to context 1 is programmed to indicate the location of program 59 and data 60. The limit and access bits are set as indicated under context 1. Thus, when context 1 is selected, program 59 can be read (only) and, reading and writing of the data 60 is permitted. No other access to other memory locations is possible nor can the MMU memory be written into.
A second process can be stored in memory. The operating system knows the location of the first process and can program another quadrant of memory 20 for process 2. The relocation base is programmed such that when the CPU addresses locations corresponding to 0-400 KB, locations 600 KB to 1 mB, are provided to the main memory. As indicated under the heading context 2 in Figure 4, the access bits are programmed to allow reading and writing into the data 50 and reading-only of the program 53. Also, no access (for writing) to the MMU memory is permitted, nor is access permitted to other locations in the main memory. Similarly, a third process can be stored in the main memory for context 4 as indicated in Figure 4.
The advantage to the arrangement of Figure 4 is that three separate processes are stored within the main memory and that each process may be easily selected through the MMU's memory, that is, by selecting context 1,2 or 3. A separate context (context 0) is reserved as a starting point for the operating system, in the presently preferred embodiment, as discussed. This allows running of three separate programs without any reprogramming of the MMU's memory. This versatility is achieved because of the overlapping memory management capacity of the MMU's memory.
Thus, an improved memory management unit has been described which allows a plurality of programs to be run without reprogramming of the computer's MMU memory. The improved unit also limits access to certain types of data and prevents inadvertent writing into programs.

Claims (21)

1. An improved memory management unit (MMU) in a computer which includes a central processing unit (CPU), and a computer main memory, said memory arrangement unit receiving first addresses from said CPU and providing second addresses for accessing said main memory, said MMU comprising: storage means for receiving and storing signals representative of the types of information stored in locations of said main memory, said storage means coupled to said CPU for receiving at least a portion of said first address; accessing means for accessing said stored signals in said storage means when corresponding locations in said main memory are accessed by said second addresses; coupling means for coupling said signals representative of said types of information stored in said main memory to said main memory to limit accessing of certain of said types of information, whereby user access to certain types of information in said main memory such as operating systems is limited.
2. An improved MMU defined by Claim 1 wherein said storage means and accessing means comprise a random-access memory (MMU memory) which also stores the relocation base of said MMU.
3. An improved MMU defined by Claim 2 wherein said coupling means also permits reading-only of other of said types of information.
4. An improved MMU defined by Claim 3wherein said coupling means also permits reading and writing of still other of said types of information.
5. An improved MMU defined by Claim 2 wherein said MMU memory also stores limit numbers.
6. An improved MMU defined by Claim 5 wherein said MMU memory includes a plurality of memory sections (contexts) each for receiving said first addresses and for providing different second addresses depending upon the ones of said contexts which is selected, such that said contexts provide overlapping memory management.
7. In a computer which includes a central processing unit (CPU), a computer main memory management unit (MMU) for receiving first addresses from said CPU and for providing second addresses for accessing said main memory, an improvement in said MMU comprising: storage means for receiving and storing signals representative of the types of information stored in locations of said main memory, said storage means coupled to said CPU for receiving at least a portion of said first addresses; accessing means for accessing said stored signals in said storage means when corresponding locations in said main memory are accessed by said second addresses; coupling means for coupling said signals representative of said types of information stored in said main memory to said main memory to limit user access to processes stored in said memory, whereby user access to certain types of information in said memory such as programs is limited.
8. The improved MMU defined by Claim 7 wherein said storage means and accessing means comprise a random-access memory (MMU memory) which also stores the relocation base of said MMU.
9. The improved MMU defined by Claim 8 wherein said coupling means also permits reading-only of programs stored in said main memory.
10. The improved MMU defined by Claim 9 wherein said coupling means permits reading and writing of data stored in said main memory.
11. The improved MMU defined by Claim 10 wherein said coupling means prohibits user access to operating system stored in said memory.
12. The improved MMU defined by Claim 8 wherein said MMU memory stores limit numbers.
13. The improved MMU defined by Claim 8 wherein said MMU memory includes a plurality of sections (contexts) each for receiving said first addresses and for providing different second addresses depending upon the ones of said contexts which is selected, such that said contexts provide overlapping memory arrangement.
14. In a computer system which includes a central processing unit (CPU) and a computer main memory, an improved memory management unit (MMU) comprising: an MMU memory comprising a plurality of sections (contexts); control means for selecting said MMU memory sections, said control means coupled to said CPU; each of said MMU memory sections for receiving first addresses from said CPU and for providing different second addresses for accessing said main memory such that said MMU memory sections provide overlapping memory management; whereby said MMU provides a relocation base for a plurality of process stored in said main memory without reprogramming of said MMU.
15. The MMU defined by Claim 14 wherein one of said MMU memory sections is selected when said CPU is in a supervisory mode.
16. The MMU defined by Claim 14 wherein said MMU memory sections store limit numbers to permit a determination as to whether or not certain main memory addresses fall within a predetermined range.
17. The MMU defined by Claim 16 including an adder coupled to receive said limit numbers from said MMU memory sections, and wherein said limit numbers are stored in a complementary binary form in said MMU memory sections for non-stacked segments such that when combined in said adder the overflow or underflow from said adder provides said determination as to whether or not said addresses falls within said predetermined range.
18. The MMU defined by Claim 17 wherein said limit numbers are stored for stacked segments in the form of the size of the segment minus one.
19. The MMU defined by Claim 14 wherein said MMU memory includes storage means for storing signals representative of the types of information stored in said main memory.
20. The MMU defined by Claim 19 wherein said stored signals are used to control access to said main memory.
21. An improved memory management unit in a computer substantially as herein described with reference to and as illustrated in the accompanying drawings.
GB08316129A 1982-09-29 1983-06-14 Memory management unit for digital computer Expired GB2127994B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US42686982A 1982-09-29 1982-09-29

Publications (3)

Publication Number Publication Date
GB8316129D0 GB8316129D0 (en) 1983-07-20
GB2127994A true GB2127994A (en) 1984-04-18
GB2127994B GB2127994B (en) 1987-01-21

Family

ID=23692542

Family Applications (1)

Application Number Title Priority Date Filing Date
GB08316129A Expired GB2127994B (en) 1982-09-29 1983-06-14 Memory management unit for digital computer

Country Status (12)

Country Link
JP (1) JPS5979367A (en)
AU (1) AU559067B2 (en)
CA (1) CA1197020A (en)
DE (1) DE3333894A1 (en)
FR (1) FR2533736A1 (en)
GB (1) GB2127994B (en)
IL (1) IL69784A (en)
IN (1) IN161125B (en)
IT (1) IT1221741B (en)
NZ (1) NZ205486A (en)
SE (1) SE464052B (en)
ZA (1) ZA836384B (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2176918A (en) * 1985-06-13 1987-01-07 Intel Corp Memory management for microprocessor system
GB2191317A (en) * 1986-05-24 1987-12-09 Hitachi Ltd Accessing memory
GB2228350A (en) * 1989-01-19 1990-08-22 Strahlen Umweltforsch Gmbh Memory protection against unauthorised access
US5321836A (en) * 1985-06-13 1994-06-14 Intel Corporation Virtual memory management method and apparatus utilizing separate and independent segmentation and paging mechanism
US5617554A (en) * 1992-02-10 1997-04-01 Intel Corporation Physical address size selection and page size selection in an address translator
US5752275A (en) * 1995-03-31 1998-05-12 Intel Corporation Translation look-aside buffer including a single page size translation unit
EP1519274A2 (en) * 2003-09-26 2005-03-30 Seiko Epson Corporation Apparatus, program, and method for memory management

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1988001411A1 (en) * 1986-08-22 1988-02-25 Commonwealth Scientific And Industrial Research Or A content-addressable memory system
ATE97535T1 (en) * 1986-09-25 1993-12-15 Siemens Ag ADDRESS MANAGEMENT UNIT OF A MULTIPROCESSOR CENTRAL CONTROL UNIT OF A MESSAGE SWITCHING SYSTEM.
FR2618578A1 (en) * 1987-07-21 1989-01-27 Digilog On-board modular computer system with integrated virtual memory

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB1477977A (en) * 1974-06-07 1977-06-29 Control Data Corp Apparatus for forming an absolute address for accessing a memory of a computer
GB1498116A (en) * 1974-04-18 1978-01-18 Honeywell Inf Systems Data processing systems
GB1557121A (en) * 1976-04-30 1979-12-05 Ibm Data processing apparatus
GB1577592A (en) * 1976-12-27 1980-10-29 Ibm Data processing apparatus
GB1585960A (en) * 1976-07-30 1981-03-11 Plessey Co Ltd Information flow security mechanisms for data processing systems
EP0040702A2 (en) * 1980-05-23 1981-12-02 International Business Machines Corporation Authorization mechanism for transfer of program control or data between different address spaces having different storage protect keys

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS5315779B2 (en) * 1973-08-16 1978-05-27
US3999052A (en) * 1975-06-18 1976-12-21 International Business Machines Corporation Upper bounds address checking system for providing storage protection for a digital data processor
JPS5436144A (en) * 1977-08-26 1979-03-16 Toshiba Corp Address conversion unit
DE2837241C2 (en) * 1978-08-25 1982-05-06 Siemens AG, 1000 Berlin und 8000 München Device for securing data against unauthorized access

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB1498116A (en) * 1974-04-18 1978-01-18 Honeywell Inf Systems Data processing systems
GB1477977A (en) * 1974-06-07 1977-06-29 Control Data Corp Apparatus for forming an absolute address for accessing a memory of a computer
GB1557121A (en) * 1976-04-30 1979-12-05 Ibm Data processing apparatus
GB1585960A (en) * 1976-07-30 1981-03-11 Plessey Co Ltd Information flow security mechanisms for data processing systems
GB1577592A (en) * 1976-12-27 1980-10-29 Ibm Data processing apparatus
EP0040702A2 (en) * 1980-05-23 1981-12-02 International Business Machines Corporation Authorization mechanism for transfer of program control or data between different address spaces having different storage protect keys

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2176918A (en) * 1985-06-13 1987-01-07 Intel Corp Memory management for microprocessor system
US5321836A (en) * 1985-06-13 1994-06-14 Intel Corporation Virtual memory management method and apparatus utilizing separate and independent segmentation and paging mechanism
GB2176918B (en) * 1985-06-13 1989-11-01 Intel Corp Memory management for microprocessor system
GB2191317B (en) * 1986-05-24 1990-05-16 Hitachi Ltd A register access mechanism for a data processing system
GB2191317A (en) * 1986-05-24 1987-12-09 Hitachi Ltd Accessing memory
GB2228350A (en) * 1989-01-19 1990-08-22 Strahlen Umweltforsch Gmbh Memory protection against unauthorised access
GB2228350B (en) * 1989-01-19 1993-04-28 Strahlen Umweltforsch Gmbh Method of real-time monitoring the address regions in data processing devices
US5396609A (en) * 1989-01-19 1995-03-07 Gesellschaft Fur Strahlen- Und Umweltforschung Mbh (Gsf) Method of protecting programs and data in a computer against unauthorized access and modification by monitoring address regions
US5617554A (en) * 1992-02-10 1997-04-01 Intel Corporation Physical address size selection and page size selection in an address translator
US5802605A (en) * 1992-02-10 1998-09-01 Intel Corporation Physical address size selection and page size selection in an address translator
US5752275A (en) * 1995-03-31 1998-05-12 Intel Corporation Translation look-aside buffer including a single page size translation unit
EP1519274A2 (en) * 2003-09-26 2005-03-30 Seiko Epson Corporation Apparatus, program, and method for memory management
EP1519274A3 (en) * 2003-09-26 2006-11-02 Seiko Epson Corporation Apparatus, program, and method for memory management
US7404060B2 (en) 2003-09-26 2008-07-22 Seiko Epson Corporation Apparatus, program, and method for managing usage of memory

Also Published As

Publication number Publication date
IN161125B (en) 1987-10-10
JPS5979367A (en) 1984-05-08
IL69784A (en) 1986-12-31
CA1197020A (en) 1985-11-19
DE3333894C2 (en) 1993-04-01
SE464052B (en) 1991-02-25
FR2533736A1 (en) 1984-03-30
IL69784A0 (en) 1983-12-30
IT8322960A0 (en) 1983-09-22
AU1894083A (en) 1984-04-05
GB8316129D0 (en) 1983-07-20
AU559067B2 (en) 1987-02-19
SE8305290D0 (en) 1983-09-29
DE3333894A1 (en) 1984-03-29
GB2127994B (en) 1987-01-21
NZ205486A (en) 1987-02-20
ZA836384B (en) 1984-05-30
IT1221741B (en) 1990-07-12
SE8305290L (en) 1984-03-30

Similar Documents

Publication Publication Date Title
US4926316A (en) Memory management unit with overlapping control for accessing main memory of a digital computer
US4037215A (en) Key controlled address relocation translation system
US4037214A (en) Key register controlled accessing system
EP0979456B1 (en) Memory access protection
US6256715B1 (en) System and method of performing gateway access
CA1313424C (en) Nonhierarchical program authorization mechanism
US4408274A (en) Memory protection system using capability registers
US5991858A (en) Multi-user data processing system with storage protection
EP1035475B1 (en) Simple high-performance memory management unit
JPH04213131A (en) System and method for performing shadowing and remapping for reserved memory of microcomputer
JPS6248258B2 (en)
US4050094A (en) Translator lookahead controls
US7260690B2 (en) Microprocessor circuit for data carriers and method for organizing access to data stored in a memory
US4943914A (en) Storage control system in which real address portion of TLB is on same chip as BAA
GB2127994A (en) Memory management unit for digital computer
US5317706A (en) Memory expansion method and apparatus in a virtual memory system
US5802598A (en) Data memory access control and method using fixed size memory sections that are sub-divided into a fixed number of variable size sub-sections
KR860002759A (en) Access Verifier for Digital Data Processing Systems with Demand-Page Memory
CA1075823A (en) Supervisor address key control system
US6754794B2 (en) Chip card with integrated circuit
AU592349B2 (en) Call instruction for ring crossing architecture
US4318175A (en) Addressing means for random access memory system
CA1078068A (en) Address key register load/store instruction system
US4050060A (en) Equate operand address space control system
US5802397A (en) System for storage protection from unintended I/O access using I/O protection key by providing no control by I/O key entries over access by CP entity

Legal Events

Date Code Title Description
PCNP Patent ceased through non-payment of renewal fee

Effective date: 19940614