In the Itanium And PA-RISC Architectures
페이지 정보
작성자 JZ 작성일25-08-29 06:50 (수정:25-08-29 06:50)관련링크
본문
Memory protection is a way to control memory entry rights on a computer, and is a part of most trendy instruction set architectures and operating methods. The main function of memory protection is to stop a course of from accessing memory that has not been allotted to it. This prevents a bug or malware within a course of from affecting different processes, or the operating system itself. Protection could encompass all accesses to a specified space of memory, write accesses, or makes an attempt to execute the contents of the realm. Memory Wave focus enhancer safety for computer safety includes extra methods similar to tackle space structure randomization and executable-space safety. Segmentation refers to dividing a pc's memory into segments. A reference to a memory location includes a worth that identifies a segment and an offset within that segment. A segment descriptor could limit access rights, e.g., read solely, only from sure rings. The x86 structure has multiple segmentation features, which are helpful for utilizing protected memory on this architecture.

On the x86 structure, the global Descriptor Table and local Descriptor Tables can be utilized to reference segments in the pc's memory. Pointers to memory segments on x86 processors can also be stored within the processor's section registers. Initially x86 processors had 4 section registers, CS (code phase), SS (stack segment), DS (knowledge segment) and ES (further phase); later one other two segment registers had been added - FS and GS. Utilizing virtual memory hardware, every page can reside in any location at an appropriate boundary of the pc's bodily memory, or be flagged as being protected. Digital memory makes it potential to have a linear virtual memory handle space and to make use of it to entry blocks fragmented over physical memory address space. Most pc architectures which support paging additionally use pages as the basis for memory safety. A page table maps virtual memory to bodily Memory Wave. There may be a single web page table, a web page desk for each process, a web page table for every phase, or a hierarchy of web page tables, depending on the architecture and the OS.
The page tables are often invisible to the process. Web page tables make it simpler to allocate extra memory, Memory Wave focus enhancer as every new web page will be allocated from wherever in bodily memory. On some techniques a page table entry can even designate a page as learn-solely. Some operating methods set up a distinct deal with space for every course of, which supplies hard memory safety boundaries. Unallocated pages, and pages allotted to some other software, shouldn't have any addresses from the appliance perspective. A page fault may not necessarily point out an error. Page faults are usually not only used for memory protection. The working system intercepts the web page fault, loads the required memory page, and the application continues as if no fault had occurred. This scheme, a kind of virtual memory, permits in-memory information not presently in use to be moved to secondary storage and back in a approach which is clear to applications, to extend total memory capability.
On some methods, a request for virtual storage might allocate a block of virtual addresses for which no page frames have been assigned, and the system will solely assign and initialize page frames when page faults occur. On some methods a guard page may be used, either for error detection or to robotically grow knowledge structures. Every course of additionally has a safety key worth related to it. On a memory access the hardware checks that the present course of's safety key matches the value related to the memory block being accessed; if not, an exception occurs. This mechanism was launched within the System/360 architecture. It is offered on in the present day's System z mainframes and heavily used by System z operating techniques and their subsystems. The System/360 protection keys described above are associated with bodily addresses. This is totally different from the safety key mechanism utilized by architectures such as the Hewlett-Packard/Intel IA-sixty four and Hewlett-Packard PA-RISC, that are related to digital addresses, and which allow a number of keys per process.
댓글목록
등록된 댓글이 없습니다.