Can mainline Linux run on Android without vendor hooks

on YouTube ↗15m

" summary

Argues that many Android-only patches are now implemented as vendor hooks (tracepoints added to the GKI) to override kernel behavior because real devices expose scheduler, DVFS and errata problems that upstream kernels don’t yet solve. Lists concrete failures: UI jank, battery and thermal regressions, priority inversion from DVFS and binder locking, EAS packing vs CFS spreading, RT placement and heavy background-task interference. Proposes building user-space QoS libraries and SDKs to reduce hooks, targets incremental fixes aiming for Android 15 timeframes.

AI-written summary · about

" chapters (7)

1. 0:00Introduction and motivation
2. 1:42Vendor hooks and quality issues
3. 3:10Scheduler challenges in Android
4. 8:47Latency and performance inversions
5. 11:15Background tasks and real-time issues
6. 12:18Breaking the deadlock with user space
7. 13:20Q&A and discussion

" related talks

• 08mTechnical debtMatthias Männich · Linux Plumbers Conference 2022
• 09mAndroid Kernel Upstreaming to the Linux KernelJohn Stultz, Greg Kroah-Hartman · Linaro Connect Asia 2013
• 42mAndroid: Protecting the KernelJeffrey Vander Stoep · Linux Security Summit 2016
• 37mRunning Android on the Mainline Graphics StackRobert Foss · foss-north 2018
• 01h 08mAndroid Plateform AnatomyBenjamin Zores · Droidcon Paris 2013
• 41mUnifying Android and Mainline Kernel Graphics StackGustavo Padovan · Embedded Linux Conference + OpenIoT Summit North America 2017
• 33mAndroid Kernel Upstreaming: Overview & StatusJohn Stultz · Android Builders Summit 2013
• 42mAndroid Common Kernel and Out of Mainline Patchset StatusAmit Pundir · Embedded Linux Conference + OpenIoT Summit North America 2018