Book Image

Linux Kernel Programming Part 2 - Char Device Drivers and Kernel Synchronization

By : Kaiwan N. Billimoria
Book Image

Linux Kernel Programming Part 2 - Char Device Drivers and Kernel Synchronization

By: Kaiwan N. Billimoria

Overview of this book

Linux Kernel Programming Part 2 - Char Device Drivers and Kernel Synchronization is an ideal companion guide to the Linux Kernel Programming book. This book provides a comprehensive introduction for those new to Linux device driver development and will have you up and running with writing misc class character device driver code (on the 5.4 LTS Linux kernel) in next to no time. You'll begin by learning how to write a simple and complete misc class character driver before interfacing your driver with user-mode processes via procfs, sysfs, debugfs, netlink sockets, and ioctl. You'll then find out how to work with hardware I/O memory. The book covers working with hardware interrupts in depth and helps you understand interrupt request (IRQ) allocation, threaded IRQ handlers, tasklets, and softirqs. You'll also explore the practical usage of useful kernel mechanisms, setting up delays, timers, kernel threads, and workqueues. Finally, you'll discover how to deal with the complexity of kernel synchronization with locking technologies (mutexes, spinlocks, and atomic/refcount operators), including more advanced topics such as cache effects, a primer on lock-free techniques, deadlock avoidance (with lockdep), and kernel lock debugging techniques. By the end of this Linux kernel book, you'll have learned the fundamentals of writing Linux character device driver code for real-world projects and products.
Table of Contents (11 chapters)
1
Section 1: Character Device Driver Basics
3
User-Kernel Communication Pathways
5
Handling Hardware Interrupts
6
Working with Kernel Timers, Threads, and Workqueues
7
Section 2: Delving Deeper

Summary

Congratulations! This chapter has been long but worthwhile. You will have learned a lot regarding how to work with hardware interrupts. We started by briefly looking at how the OS handles interrupts before learning how you, as a driver author, must work with them. To do so you learned how to, via several methods, allocate IRQ lines (and free them) and implement the hardware interrupt routine. Here, several limitations and caveats, essentially boiling down to the fact that it's an atomic activity, were discussed. The hows and whys of the "threaded interrupt" model were then covered; it's often regarded as the modern recommended way to handle interrupts. After that, we understood and learned how to work with hardirqs/softirqs and top/bottom halves. Finally, we covered, in typical FAQ style, information which taught you about load balancing interrupts, IRQ stacks, and how to employ some useful frameworks and tools that can measure interrupt metrics and latencies...