Protected mode - Knowledge

1843: 380: 1851: 766: 4158: 4148: 4138: 4128: 4118: 807:. The next bit (bit 2) specifies whether the operation is used with the GDT or the LDT. The lowest two bits (bit 1 and bit 0) of the selector are combined to define the privilege of the request, where the values of 0 and 3 represent the highest and the lowest privilege, respectively. This means that the byte offset of descriptors in the descriptor table is the same as the 16-bit selector, provided the lower three bits are zeroed. 351:, equivalent to 256 KB, could be accessed at a time. Because changing a segment register in protected mode caused a 6-byte segment descriptor to be loaded into the CPU from memory, the segment register load instruction took many tens of processor cycles, making it much slower than on the 8086; therefore, the strategy of computing segment addresses on-the-fly in order to access data structures larger than 128 611: 398:. The segment sizes were also increased to 32 bits, meaning that the full address space of 4 gigabytes could be accessed without the need to switch between multiple segments. In addition to the increased size of the address bus and segment registers, many other new features were added with the intention of increasing operational security and stability. Protected mode is now used in virtually all modern 259:(386) in 1985. Due to the enhancements added by protected mode, it has become widely adopted and has become the foundation for all subsequent enhancements to the x86 (IA-32) architecture, although many of those enhancements, such as added instructions and new registers, also brought benefits to the real mode. 1963:

series. If a Windows 1.x or 2.x program is written properly and avoids segment arithmetic, it will run the same way in both real and protected modes. Windows programs generally avoid segment arithmetic because Windows implements a software virtual memory scheme, moving program code and data in memory

3124:

The reason why software task switching is so popular is that it can be faster than hardware task switching. Intel never actually developed the hardware task switching, they implemented it, saw that it worked, and just left it there. Advances in multitasking using software have made this form of task

366:

to run unmodified on the newer 286. Real mode also served as a more basic mode in which protected mode could be set up, solving a sort of chicken-and-egg problem. To access the extended functionality of the 286, the operating system would set up some tables in memory that controlled memory access in

1968:

to memory blocks when not running. Starting an old program while Windows 3.0 is running in protected mode triggers a warning dialog, suggesting to either run Windows in real mode or to obtain an updated version of the application. Updating well-behaved programs using the MARK utility with the

778:

In real mode each logical address points directly into a physical memory location, every logical address consists of two 16-bit parts: The segment part of the logical address contains the base address of a segment with a granularity of 16 bytes, i.e. a segment may start at physical address 0, 16,

1958:

was able to run real mode programs in 16-bit protected mode; when switching to protected mode, it decided to preserve the single privilege level model that was used in real mode, which is why Windows applications and DLLs can hook interrupts and do direct hardware access. That lasted through the

1858:

In addition to adding virtual 8086 mode, the 386 also added paging to protected mode. Through paging, system software can restrict and control a task's access to pages, which are sections of memory. In many operating systems, paging is used to create an independent virtual address space for each

1886:

to a page table. A page table was also originally four kilobytes in size and contained 1,024 page table entries (PTE). Each PTE contained a pointer to the actual page's physical address and are only used when the four-kilobyte pages are used. At any given time, only one page directory may be in

822:

The segment address inside the descriptor table entry has a length of 24 bits so every byte of the physical memory can be defined as bound of the segment. The limit value inside the descriptor table entry has a length of 16 bits so segment length can be between 1 byte and 2 byte. The calculated

595:

Protected mode has a number of features designed to enhance an operating system's control over application software, in order to increase security and system stability. These additions allow the operating system to function in a way that would be significantly more difficult or even impossible

847:

For maintaining compatibility with 286 protected mode a new default flag (D-bit, for short) was added. If the D-bit of a code segment is off (0) all commands inside this segment will be interpreted as 16-bit commands by default; if it is on (1), they will be interpreted as 32-bit commands.

1913:

was made possible on the x86 architecture. The TSS allows general-purpose registers, segment selector fields, and stacks to all be modified without affecting those of another task. The TSS also allows a task's privilege level, and I/O port permissions to be independent of another task's.

1917:

In many operating systems, the full features of the TSS are not used. This is commonly due to portability concerns or due to the performance issues created with hardware task switches. As a result, many operating systems use both hardware and software to create a multitasking system.

831:

The segment address inside the descriptor table entry is expanded to 32 bits so every byte of the physical memory can be defined as bound of the segment. The limit value inside the descriptor table entry is expanded to 20 bits and completed with a granularity flag (G-bit, for short):

343:. Several shortcomings such as the inability to make BIOS and DOS calls due to inability to switch back to real mode without resetting the processor prevented widespread usage. Acceptance was additionally hampered by the fact that the 286 only allowed memory access in 64 504:(21st address line) also must be enabled to allow the use of all the address lines so that the CPU can access beyond 1 megabyte of memory (Only the first 20 are allowed to be used after power-up, to guarantee compatibility with older software written for the Intel 8088-based 839:

If G-bit is one limit has a granularity of 2 bytes, i.e. segment size may be 1 × 2, 2 × 2, ..., 2 × 2 bytes. If paging is off, the calculated linear address equals the physical memory address. If paging is on, the calculated linear address is used as input of

367:

protected mode, set the addresses of those tables into some special registers of the processor, and then set the processor into protected mode. This enabled 24-bit addressing, which allowed the processor to access 2 bytes of memory, equivalent to 16

586:

With the release of the 386, protected mode could be exited by loading the segment registers with real mode values, disabling the A20 line and clearing the PE bit in the CR0 register, without the need to perform the initial setup steps required with the 286.

393:

With the release of the 386 in 1985, many of the issues preventing widespread adoption of the previous protected mode were addressed. The 386 was released with an address bus size of 32 bits, which allows for 2 bytes of memory accessing, equivalent to 4

1882:. Originally, a page directory was the size of one page, four kilobytes, and contained 1,024 page directory entries (PDE), although subsequent enhancements to the x86 architecture have added the ability to use larger page sizes. Each PDE contained a 742:

Due to these limitations, some programs originally designed to run on the 8086 cannot be run in virtual 8086 mode. As a result, system software is forced to either compromise system security or backward compatibility when dealing with

779:

32, ..., 2 − 16. The offset part of the logical address contains an offset inside the segment, i.e. the physical address can be calculated as physical_address = segment_part × 16 + offset, if the address

3052:

The paging process allows the operating system to overcome the real physical memory limits. However, it also has a direct impact on performance because of the time necessary to write or retrieve data from

493:

was used to reset the 286 CPU, which was a lot faster and cleaner than the keyboard controller method (and does not depend on IBM AT-compatible hardware, but will work on any 80286 CPU in any system).

646:

the 80286 remains upwardly compatible with most 8086 and 80186 application programs. Most 8086 application programs can be re-compiled or re-assembled and executed on the 80286 in Protected Mode.

3033: 654:, were the most apparent changes to application programmers. This was not without its limitations. If an application utilized or relied on any of the techniques below, it would not run: 723:

Virtual 8086 mode, however, is not completely backward compatible with all programs. Programs that require segment manipulation, privileged instructions, direct hardware access, or use

720:. Virtual 8086 mode is designed to allow code previously written for the 8086 to run unmodified and concurrently with other tasks, without compromising security or system stability. 489:

and often the interrupt mask in the real-time clock chip's RAM. This allowed the BIOS to restore the CPU to a similar state and begin executing code before the reset. Later, a

2083:

The memory access control system according to claim 4, wherein said first address mode is a real address mode, and said second address mode is a protected virtual address mode.

2911: 2891: 2682: 2664: 2646: 2628: 500:(GDT) must first be created with a minimum of three entries: a null descriptor, a code segment descriptor and data segment descriptor. In an IBM-compatible machine, the 2951:

A downside to using V86 mode is speed: every IOPL-sensitive instruction will cause the CPU to trap to kernel mode, as will I/O to ports which are masked out in the TSS.

622:, numbered from 0 to 3, with ring 0 being the most privileged and 3 being the least. The use of rings allows for system software to restrict tasks from accessing data, 2722: 2508: 2261: 2207: 2155: 2098: 1969:

MEMORY parameter avoids this dialog. It is not possible to have some GUI programs running in 16-bit protected mode and other GUI programs running in real mode. In

232:

with earlier x86 processors. Protected mode may only be entered after the system software sets up one descriptor table and enables the Protection Enable (PE)

2176: 2140:

The purpose of protected mode is not to protect your program. The purpose is to protect everyone else (including the operating system) from your program.

3125:

switching faster (some say up to 3 times faster) than the hardware method. Another reason is that the Intel way of switching tasks isn't portable at all

2818:

This has been impossible to-date and has forced BIOS development teams to add support into the BIOS for 32 bit function calls from 32 bit applications.

2398: 3285: 2230: 3037: 2780: 2761: 2742: 168: 4182: 4098: 477:

Until the release of the 386, protected mode did not offer a direct method to switch back into real mode once protected mode was entered.

3759: 3232: 3180: 2356: 2576: 1930:

1.x try to switch the processor between protected and real modes. This is both slow and unsafe, because a real mode program can easily

355:(the combined size of the two data segments) became impractical, even for those few programmers who had mastered it on the 8086/8088. 2700: 2489: 2060: 650:

For the most part, the binary compatibility with real-mode code, the ability to access up to 16 MB of physical memory, and 1 GB of

3807: 2183: 512:

models). After performing those two steps, the PE bit must be set in the CR0 register and a far jump must be made to clear the

3138: 3101: 2286: 4151: 3955: 3779: 3561: 3532: 2683:"Intel 64 and IA-32 Architectures Software Developer's Manual Combined Volumes 3A, 3B, 3C, and 3D: System Programming Guide" 2665:"Intel 64 and IA-32 Architectures Software Developer's Manual Combined Volumes 3A, 3B, 3C, and 3D: System Programming Guide" 2647:"Intel 64 and IA-32 Architectures Software Developer's Manual Combined Volumes 3A, 3B, 3C, and 3D: System Programming Guide" 2629:"Intel 64 and IA-32 Architectures Software Developer's Manual Combined Volumes 3A, 3B, 3C, and 3D: System Programming Guide" 4141: 2913:

Intel 64 and IA-32 Architectures Software Developer's Manual Combined Volumes 3A, 3B, 3C, and 3D: System Programming Guide

2893:

Intel 64 and IA-32 Architectures Software Developer's Manual Combined Volumes 3A, 3B, 3C, and 3D: System Programming Guide

2616:

80386SX — low cost version of the 80386. This processor had 16 bit external data bus and 24-bit external address bus.

4161: 2315: 2972: 2541: 2464: 161: 3066: 3336: 3280: 2334:

What is interesting is that the designers of the time never suspected anyone would ever need more than 1 MB of RAM.

1859:

task, preventing one task from manipulating the memory of another. Paging also allows for pages to be moved out of

2850:... secondly, protected mode was also incompatible with the vast amount of real-mode code around at the time. 3978: 3752: 3255: 3225: 362:

on power up. Real mode functioned virtually identically to the 8086, allowing the vast majority of existing 8086

1842: 4103: 3448: 3346: 2429: 1883: 731:

that must be served by the operating system. In addition, applications running in virtual 8086 mode generate a

2932: 2863: 2831: 3726: 3275: 3260: 1682:

bit, and determines which privilege levels can far-jump to this segment (without changing privilege level):

783:

is enabled, or (segment_part × 16 + offset) mod 2, if A20 is off. Every segment has a size of 2 bytes.

313:

As the cost of memory decreased and memory use increased, the 1 MB limitation became a significant problem.

4187: 3963: 3801: 3321: 3306: 3265: 2405: 1981: 154: 3190: 1964:

when programs are not running, so manipulating absolute addresses is dangerous; programs should only keep

694:

and its successors can take advantage of the binary compatibility with real mode to run many Windows 2.x (

3940: 3487: 3434: 332: 20: 4121: 4008: 3998: 3988: 3841: 3745: 3502: 3341: 3218: 2448: 3161:... both rely on the Intel processors ability to switch tasks, they rely on it in different ways. 2234: 290:. At the time, 1 megabyte was considered a relatively large amount of memory, so the designers of the 4067: 3537: 3356: 3316: 3311: 3270: 224:

When a processor that supports x86 protected mode is powered on, it begins executing instructions in

132: 331:

The initial protected mode, released with the 286, was not widely used; for example, it was used by

3927: 3580: 3467: 3331: 2529: 2453: 2036: 619: 605: 509: 482: 4131: 3993: 3968: 3874: 3326: 1910: 760: 497: 194: 836:

If G-bit is zero limit has a granularity of 1 byte, i.e. segment size may be 1, 2, ..., 2 bytes.

485:) which involved resetting the CPU via the keyboard controller and saving the system registers, 425:

required for virtualizing the protected mode itself, however, had to wait for another 20 years.

3945: 3897: 3795: 3714: 3653: 3542: 3522: 3471: 3429: 229: 98: 3175: 2360: 358:

The 286 maintained backward compatibility with its precursor (the 8086) by initially entering

3973: 3497: 3463: 3365: 3301: 2041: 1896: 814:

address of the segment, a limit value for the segment size, and some attribute bits (flags).

505: 433:

With the release of the 386, the following additional features were added to protected mode:

291: 214: 2122: 3694: 3668: 2993: 1875: 513: 413:

Furthermore, learning from the failures of the 286 protected mode to satisfy the needs for

218: 2788:. Santa Clara, California: Intel. 1987. Appendix C 8086/8088 Compatibility Considerations. 626:

or executing privileged instructions. In most environments, the operating system and some

8: 3851: 3663: 3615: 3492: 2724: