GKI Experience
summary
Qualcomm moves from GKI 1.0 test-only to shipping full GKI kernels, adopting a mixed build workflow that keeps a GKI boot image while building vendor modules from the MSM tree. Results: about 125 contributions backported to upstream, more frequent LTS merges, and fewer divergent commits on 5.15. Practical problems: 90MB overhead on some 1GB targets when switching from arm32 to arm64 GKI, Kconfig and device tree handling for out-of-tree leaf drivers, and a need for cleaner output control for module builds.
AI-written summary · about
chapters (11)
- 0:00Introduction to GKI
- 1:04GKI 2.0 adoption and mixed builds
- 2:28Security patches and LTS merges
- 4:11Upstream contributions and divergence
- 4:53Future of GKI at Qualcomm
- 6:20Out-of-tree module challenges
- 7:05Q&A: Low memory devices
- 9:12Q&A: Memory overhead details
- 10:17Q&A: Out-of-tree drivers concerns
- 11:41Q&A: ARM64 vs GKI memory impact
- 12:15Q&A: Upstream participation
related talks
15mSimplified Android Kernel Driver Development with DDK v2
15mDriver Development Kit DDK and Vendor Workflow
37mA Developer's Diary: The Trials and Triumphs of Maintaining Devboards in AOSP
26mBootloops & Coffee: The Daily Grind of an AOSP Developer
22mAOSP Toolchains: Where we are with building kernels, bootloaders and AOSP with Clang
16mPixel 6 support on androidmainline
38mHow to Enable Android (AOSP) on Your Developer Board
13mAndroid Kernel testing with platform integration