Within the Itanium And PA-RISC Architectures > 자유게시판

• 목록
• 답변
• 글쓰기
• 게시판 리스트 옵션
  • 수정
  • 삭제

Memory protection is a approach to control memory access rights on a pc, and is part of most fashionable instruction set architectures and operating systems. The principle goal of memory safety is to stop a process from accessing memory that has not been allotted to it. This prevents a bug or malware inside a process from affecting different processes, or the working system itself. Safety may encompass all accesses to a specified area of memory, write accesses, or attempts to execute the contents of the area. Memory protection for pc safety contains additional techniques reminiscent of tackle house structure randomization and Memory Wave executable-space safety. Segmentation refers to dividing a pc's memory into segments. A reference to a memory location contains a worth that identifies a phase and an offset within that phase. A phase descriptor may restrict access rights, e.g., learn solely, solely from certain rings. The x86 structure has multiple segmentation options, which are useful for using protected memory on this structure.

On the x86 structure, the worldwide Descriptor Table and local Descriptor Tables can be used to reference segments in the computer's memory. Pointers to memory segments on x86 processors can also be saved in the processor's segment registers. Initially x86 processors had 4 segment registers, CS (code section), SS (stack segment), DS (data section) and ES (further phase); later another two phase registers have been added - FS and GS. Utilizing digital memory hardware, every web page can reside in any location at a suitable boundary of the pc's physical memory, or be flagged as being protected. Digital memory makes it potential to have a linear virtual memory tackle house and to use it to access blocks fragmented over bodily memory address space. Most laptop architectures which support paging additionally use pages as the idea for memory protection. A page desk maps digital memory to bodily memory. There could also be a single web page desk, a page table for every process, Memory Wave Workshop a page table for each section, or a hierarchy of web page tables, relying on the structure and the OS.

The page tables are usually invisible to the process. Page tables make it easier to allocate extra memory, as every new page might be allotted from anywhere in bodily memory. On some methods a page table entry can also designate a page as read-only. Some working techniques set up a special address area for every process, which supplies arduous memory protection boundaries. Unallocated pages, and pages allocated to every other software, would not have any addresses from the application standpoint. A web page fault might not essentially point out an error. Page faults are not only used for memory safety. The operating system intercepts the page fault, loads the required memory page, and the applying continues as if no fault had occurred. This scheme, a type of digital memory, allows in-memory knowledge not at present in use to be moved to secondary storage and again in a approach which is clear to purposes, to extend overall Memory Wave Workshop capability.

On some programs, a request for virtual storage could allocate a block of digital addresses for which no page frames have been assigned, and the system will only assign and initialize page frames when web page faults occur. On some programs a guard web page could also be used, either for error detection or to routinely develop information structures. Every course of additionally has a protection key value associated with it. On a memory entry the hardware checks that the current process's protection key matches the worth associated with the memory block being accessed; if not, an exception happens. This mechanism was introduced in the System/360 architecture. It is obtainable on right now's System z mainframes and closely utilized by System z operating programs and their subsystems. The System/360 protection keys described above are associated with physical addresses. That is different from the safety key mechanism utilized by architectures such as the Hewlett-Packard/Intel IA-sixty four and Hewlett-Packard PA-RISC, which are associated with virtual addresses, and Memory Wave which allow multiple keys per course of.