Linux Device Driver Development Cookbook
上QQ阅读APP看书,第一时间看更新

A Peek Inside the Kernel

Simple operating systems (such as MS-DOS) always execute in a single CPU mode, but Unix-like operating systems use dual modes to effectively implement timesharing and resource allocation and protection. At any time in Linux, the CPU is either operating in a trusted kernel mode (where we can do everything we wish) or in a restricted user mode (where some operations are not allowed). All user processes execute in user mode, whereas the core kernel itself and most device drivers (except ones implemented in user space) run in kernel mode so that they have unrestricted access to the entire processor instruction set and to the full memory and I/O space.

When a user mode process needs to get access to peripherals, it cannot do it by itself, but it has to channel requests through device drivers or other kernel mode code via system calls, which play a major role in controlling process activities and managing data exchange. In this chapter, we will not see system calls yet (they will be introduced in Chapter 3, Working with Char Drivers), but we will start programming into the kernel by directly adding new code into its sources or by using kernel modules, which is another, more versatile, manner to add code to the kernel.

Once we get started writing kernel code, we must not forget that, while in user mode, every resource allocation (the CPU, RAM, and so on) is automatically managed by the kernel (which can properly release them when a process dies), in kernel mode, we are allowed to monopolize the processor until either we voluntarily relinquish the CPU or an interrupt or exception occurs; moreover, every requested resource (as the RAM, for instance) is lost if not properly released. That's why it's really important to correctly manage the CPU usage and to free whatever resource we request!

Now, it's time to do a first jump into the kernel, so in this chapter, we will cover the following recipes:

  • Adding custom code to the sources
  • Using kernel messages
  • Working with kernel modules
  • Using module parameters