Speaker
Todd Kjos
(Google)
Description
Android’s Generic Kernel Image (GKI) enforces a single binary kernel, restricting Android ecosystem partners from modifying core kernel code. To allow partner-specific optimizations, Google introduced "vendor hooks", based on Linux tracepoints, to act as in-kernel callback registration points. Partners use loadable kernel modules to register handlers for these hooks to implement partner-specific features.
But what are they actually used for?
In this session we'll discuss the motivation behind providing vendor hooks and some of the common optimization patterns implemented by partners across various kernel subsystems including scheduler and mm. The discussion will be based on the actual usage of these hooks across major Android partners.
Author
Todd Kjos
(Google)