Instructions that control interrupts.
Instructions that manage memory mapping and Set the time of day clock.
Instructions that actually access input/output devices by i/o commands or read/write device registers.
Instructions that allow access to memory outside of a users allocated memory area.
Instructions that let you modify system software
Instructions that let you gain priority or privilege not appropriate for your user account.
Kernel ModeIn Kernel mode, the executing code has complete and unrestricted access to the underlying hardware. It can execute any CPU instruction and reference any memory address. Kernel mode is generally reserved for the lowest-level, most trusted functions of the operating system. Crashes in kernel mode are catastrophic; they will halt the entire PC.User ModeIn User mode, the executing code has no ability to directly access hardware or reference memory. Code running in user mode must delegate to system APIs to access hardware or memory. Due to the protection afforded by this sort of isolation, crashes in user mode are always recoverable. Most of the code running on your computer will execute in user mode.
user mode and kernel mode
http://wiki.answers.com/Q/What_are_the_differences_between_minimum_mode_and_maximum_mode maximum mode?
TE10 mode is the dominant mode with a>b, since it has the lowest attenuation of all modes. Either m or n can be zero, but not both.
PIO
no, it wont operatesin kernel mode, it operates on usermode.
Code running in kernel mode has unlimited access to hardware and CPU. Code in user mode can't address memory that kernel mode does not allow it to.
Machine Mode
no commentment
The Executive Services, the Hardware Abstraction Layer (HAL), the microkernal, and kernel mode drivers
User mode and Kernel mode
Kernel ModeIn Kernel mode, the executing code has complete and unrestricted access to the underlying hardware. It can execute any CPU instruction and reference any memory address. Kernel mode is generally reserved for the lowest-level, most trusted functions of the operating system. Crashes in kernel mode are catastrophic; they will halt the entire PC.User ModeIn User mode, the executing code has no ability to directly access hardware or reference memory. Code running in user mode must delegate to system APIs to access hardware or memory. Due to the protection afforded by this sort of isolation, crashes in user mode are always recoverable. Most of the code running on your computer will execute in user mode.
The distinction between kernel mode and user mode provides a rudimentary form of protection in the following manner: Certain instructions could be executed only when the CPU is in kernel mode. Similarly, hardware devices could be accessed only when the program is executing in kernel mode. Control over when interrupts could be enabled or disabled is also possible only when the CPU is in kernel mode. Consequently, the CPU has very limited capability when executing in user mode, thereby enforcing protection of critical resources.
hardware mode
user mode and kernel mode
kernel mode
It usually doesn't. You may think of one of the followings: 1. When processing a higher priority interrupt, more interrupts with lower priority are not allowed. 2. During the context-switch (user-mode<->kernel-mode, entering/exiting interrupt/exception handler), interrupts may be disabled. 3. When in a critical operation (eg. manipulating shared data), interrupts may have to be disabled (for a very short time-interval).