You're reading from Mastering Embedded Linux Programming - Third Edition

Product type Book

Published in May 2021

Publisher Packt

ISBN-13 9781789530384

Pages 758 pages

Edition 3rd Edition

Languages

Concepts

Embedded Systems

Authors (2):

Frank Vasquez

Chris Simmonds

View More author details

Table of Contents (27) Chapters

Preface

1. Section 1: Elements of Embedded Linux

2. Chapter 1: Starting Out

3. Chapter 2: Learning about Toolchains

4. Chapter 3: All about Bootloaders

5. Chapter 4: Configuring and Building the Kernel

6. Chapter 5: Building a Root Filesystem

7. Chapter 6: Selecting a Build System

8. Chapter 7: Developing with Yocto

9. Chapter 8: Yocto Under the Hood

10. Section 2: System Architecture and Design Decisions

11. Chapter 9: Creating a Storage Strategy

12. Chapter 10: Updating Software in the Field

13. Chapter 11: Interfacing with Device Drivers

14. Chapter 12: Prototyping with Breakout Boards

15. Chapter 13: Starting Up – The init Program

16. Chapter 14: Starting with BusyBox runit

17. Chapter 15: Managing Power

18. Section 3: Writing Embedded Applications

19. Chapter 16: Packaging Python

20. Chapter 17: Learning about Processes and Threads

21. Chapter 18: Managing Memory

22. Section 4: Debugging and Optimizing Performance

23. Chapter 19: Debugging with GDB

24. Chapter 20: Profiling and Tracing

25. Chapter 21: Real-Time Programming

26. Other Books You May Enjoy

Summary

Nobody can complain that Linux lacks options for profiling and tracing. This chapter has given you an overview of some of the most common ones.

When faced with a system that is not performing as well as you would like, start with top and try to identify the problem. If it proves to be a single application, then you can use perf record/report to profile it, bearing in mind that you will have to configure the kernel to enable perf and you will need debug symbols for the binaries and kernel. If the problem is not so well localized, use perf or BCC tools to get a system-wide view.

Ftrace comes into its own when you have specific questions about the behavior of the kernel. The function and function_graph tracers provide a detailed view of the relationship and sequence of function calls. The event tracers allow you to extract more information about functions, including the parameters and return values. LTTng performs a similar role, making use of the event trace mechanism,...