Book Image

Linux Kernel Programming

By : Kaiwan N. Billimoria
Book Image

Linux Kernel Programming

By: Kaiwan N. Billimoria

Overview of this book

Linux Kernel Programming is a comprehensive introduction for those new to Linux kernel and module development. This easy-to-follow guide will have you up and running with writing kernel code in next-to-no time. This book uses the latest 5.4 Long-Term Support (LTS) Linux kernel, which will be maintained from November 2019 through to December 2025. By working with the 5.4 LTS kernel throughout the book, you can be confident that your knowledge will continue to be valid for years to come. You’ll start the journey by learning how to build the kernel from the source. Next, you’ll write your first kernel module using the powerful Loadable Kernel Module (LKM) framework. The following chapters will cover key kernel internals topics including Linux kernel architecture, memory management, and CPU scheduling. During the course of this book, you’ll delve into the fairly complex topic of concurrency within the kernel, understand the issues it can cause, and learn how they can be addressed with various locking technologies (mutexes, spinlocks, atomic, and refcount operators). You’ll also benefit from more advanced material on cache effects, a primer on lock-free techniques within the kernel, deadlock avoidance (with lockdep), and kernel lock debugging techniques. By the end of this kernel book, you’ll have a detailed understanding of the fundamentals of writing Linux kernel module code for real-world projects and products.
Table of Contents (19 chapters)
Section 1: The Basics
Writing Your First Kernel Module - LKMs Part 2
Section 2: Understanding and Working with the Kernel
Kernel Memory Allocation for Module Authors - Part 1
Kernel Memory Allocation for Module Authors - Part 2
Section 3: Delving Deeper
About Packt

Recording a sample session with trace-cmd record

In this section, we record a session with trace-cmd(1); we use a few (of the many possible) option switches to trace-cmd  recordas usual, the man pages on trace-cmd-foo(1) (substitutfoo with check-events, hist, record, report, reset, and so on) are very useful for finding various option switches and usage details. A few of the useful option switches particularly for trace-cmd record are as follows:

  • -o: Specifies the output filename (if not specified, it defaults to trace.dat).
  • -p: The plugin to use, one of function, function_graph, preemptirqsoff, irqsoff, preemptoff, and wakeup; here, in our small demo, we use the function-graph plugin (several other plugins can be configured in the kernel as well).
  • -F: The command (or app) to trace; this is very useful, allowing you to specify exactly which process (or thread) to exclusively trace (otherwise, tracing all threads can result in...