Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Project Treble
September 28, 2017
Iliyan Malchev
What and Why
1
What is the
problem? Why do
we care to solve
it?
Userspace
2
What is the
solution?
What is the
timeframe?
K...
What's the Problem?
https://developer.android.com/about/dashboards/index.html
I Userspace
I Kernel
3.4
3.1
3.10
3.18
Why Care?
Faster Device Launches on Latest Google SoC OEM users
Easier Device Upgrades Google
Better Quality Google SoC OEM users
BE...
The Life of an Android Device Launch
I Start with AOSP
...
I Add Functionality/Customizations
...
I Adapt to SoC and Device
"HALs"
"Ext"AOSP
I Reality
● Short product cycles
● No Single Android OS to update
○ Large AOSP Delta
○ SoC Support not universal
● Certification: Ca...
How to Fix it?
Architectural changes
Android Platform
Operational changes
Partner outreach
Compatibility changes
Partner outreach
Upstrea...
ExtAOSP
"HALs"
ExtAOSP
I Solve SoC Support
kernel driverdriverdriver driverdriver
libc
other libraries
activity
Media
Server
System
Server
Camera
Server
Audio
Server...
kernel driverdriverdriver driverdriver
libc
other libraries
activity
Media
Server
System
Server
Camera
Server
Audio
Server...
I The Vendor Test Suite
CTS
VTS
Android
Framework
VINTF
Implementation
General
System
Image
VINTF
Implementation
CTS on AO...
"HALs"
ExtAOSP
I Tackle the AOSP Delta
Q3 ACP ALL HANDS
Multiple implementations of same functionality
Drive convergence between AOSP and Framework Variants
Foru...
"HALs"
ExtAOSP
ExtAOSP
Must pass Vendor Test Suite (VTS; tests for HALs) for approval
All OEM devices launched with O must implement Treble HALs
...
How Fast to Fix it?
● Release uptake is 6 months to a year
○ Mostly just flagships
● Solving the problem forwards
● Customer pull is strong
● ...
The Kernel
Existing LTS is not Enough
Device Kernel
Stable Long Term Support
Android Common
SoC Kernel
Device
Release
Device
Update
C...
Announcing 6-year LTS
Device Kernel
Stable Long Term Support
Android Common
SoC Kernel
Device
Release
Device
Update
Clone ...
Stats
health/1.0
thermal/1.0
oemlock/1.0
gnss/1.0
automotive/vehicle/2.0
automotive/vehicle/2.1
automotive/evs/1.0
audio/2.0
aud...
Authors
Files
300
3000
Commits
20k
LOC
~1M
I Code Stats
Qualcomm, Mediatek,
Samsung/LSI,
Huawei/HiSilicon, Motorola,
Sony, LG
Partners
San Diego
Taipei
Seoul
Onsite Teams
7
3 Dir...
Next Steps
Clone Merge Cherry-Pick
Linux 4.9.y
Android Common 4.9
msm-4.9
(Common SoC
Kernel)
MSMXXXX based
device 1
MSMXXXX based
de...
I There's More To Do
● Continued work with SoC Vendors
● Continued work on Kernel Unification
● Expanding test coverage
● ...
END
Upcoming SlideShare
Loading in …5
×

Keynote: Iliyan Malchev (Google) – SFO17-400K1

4,583 views

Published on

Session ID: SFO17-400K1
Session Name: Keynote: Iliyan Malchev (Google) – SFO17-400K1
Speaker: Iliyan Malchev
Track: Keynote

★ Session Summary ★
Keynote: Iliyan Malchev (Google)
—————————————————
★ Resources ★
Event Page: http://connect.linaro.org/resource/sfo17/sfo17-400k1/
Presentation:
Video: https://www.youtube.com/watch?v=_BLHJBkSsfI
—————————————————

★ Event Details ★
Linaro Connect San Francisco 2017 (SFO17)
25-29 September 2017
Hyatt Regency San Francisco Airport

—————————————————
Keyword:
‘http://www.linaro.org’
‘http://connect.linaro.org’
—————————————————
Follow us on Social Media
https://www.facebook.com/LinaroOrg

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Keynote: Iliyan Malchev (Google) – SFO17-400K1

  1. 1. Project Treble September 28, 2017 Iliyan Malchev
  2. 2. What and Why 1 What is the problem? Why do we care to solve it? Userspace 2 What is the solution? What is the timeframe? Kernel 3 Tackling kernel fragmentation Results 4 Some stats and early results I Agenda
  3. 3. What's the Problem?
  4. 4. https://developer.android.com/about/dashboards/index.html I Userspace
  5. 5. I Kernel 3.4 3.1 3.10 3.18
  6. 6. Why Care?
  7. 7. Faster Device Launches on Latest Google SoC OEM users Easier Device Upgrades Google Better Quality Google SoC OEM users BEtter Security (esp. Kernel) Google SoC OEM users I Who Wants What
  8. 8. The Life of an Android Device Launch
  9. 9. I Start with AOSP
  10. 10. ... I Add Functionality/Customizations
  11. 11. ... I Adapt to SoC and Device
  12. 12. "HALs" "Ext"AOSP I Reality
  13. 13. ● Short product cycles ● No Single Android OS to update ○ Large AOSP Delta ○ SoC Support not universal ● Certification: Carrier, Regulatory, CTS ● QA ● Support (Call Center), OTA Infrastructure, etc... "HALs" ExtAOSP I Difficult means Expensive
  14. 14. How to Fix it?
  15. 15. Architectural changes Android Platform Operational changes Partner outreach Compatibility changes Partner outreach Upstreaming Android Platform I Project Treble
  16. 16. ExtAOSP "HALs" ExtAOSP I Solve SoC Support
  17. 17. kernel driverdriverdriver driverdriver libc other libraries activity Media Server System Server Camera Server Audio Server Surface Flinger OMX ... ... camera HAL audio HAL gralloc hwc sensor HAL etc ART API java.* android.* GL HAL Binder I Android Architecture Pre-O
  18. 18. kernel driverdriverdriver driverdriver libc other libraries activity Media Server System Server Camera Server Audio Server Surface Flinger OMX ... ...camera HAL audio HAL gralloc hwc sensor HAL etc ART API java.* android.* GL HAL Binder Binder I Android Architecture Post-O
  19. 19. I The Vendor Test Suite CTS VTS Android Framework VINTF Implementation General System Image VINTF Implementation CTS on AOSP <Before Oreo> <Android Oreo> HAL Kernel Library
  20. 20. "HALs" ExtAOSP I Tackle the AOSP Delta
  21. 21. Q3 ACP ALL HANDS Multiple implementations of same functionality Drive convergence between AOSP and Framework Variants Forum involving major contributors to AOSP Feature review, approval, (re)engineering Non-US regulatory requirements Extensions to Bluetooth, Telephony, Dialer, SysUI, Home Screen I Upstreaming
  22. 22. "HALs" ExtAOSP ExtAOSP
  23. 23. Must pass Vendor Test Suite (VTS; tests for HALs) for approval All OEM devices launched with O must implement Treble HALs Must pass CTS on AOSP Q3 ACP ALL HANDS This includes older SoCs that will be used by OEMs to launch O-based devices I Compatibility Requirements
  24. 24. How Fast to Fix it?
  25. 25. ● Release uptake is 6 months to a year ○ Mostly just flagships ● Solving the problem forwards ● Customer pull is strong ● Attention Span outside and within ● Addressing fragmentation is a MUST I The One-Release Fix
  26. 26. The Kernel
  27. 27. Existing LTS is not Enough Device Kernel Stable Long Term Support Android Common SoC Kernel Device Release Device Update Clone Merge Cherry-Pick Device Update Device Update Device Update
  28. 28. Announcing 6-year LTS Device Kernel Stable Long Term Support Android Common SoC Kernel Device Release Device Update Clone Merge Cherry-Pick Device Update Device Update Device Update
  29. 29. Stats
  30. 30. health/1.0 thermal/1.0 oemlock/1.0 gnss/1.0 automotive/vehicle/2.0 automotive/vehicle/2.1 automotive/evs/1.0 audio/2.0 audio/effect/2.0 audio/common/2.0 vibrator/1.1 vibrator/1.0 tv/cec/1.0 tv/input/1.0 bluetooth/1.0 usb/1.1 usb/1.0 gatekeeper/1.0 wifi/offload/1.0 wifi/supplicant/1.0 wifi/1.0 radio/1.1 radio/1.0 radio/deprecated/1.0 renderscript/1.0 weaver/1.0 light/2.0 keymaster/3.0 soundtrigger/2.0 ir/1.0 boot/1.0 graphics/allocator/2.0 graphics/bufferqueue/1.0 graphics/mapper/2.0 graphics/common/1.0 graphics/composer/2.1 drm/1.0 nfc/1.0 biometrics/fingerprint/2.1 contexthub/1.0 broadcastradio/1.1 broadcastradio/1.0 power/1.1 power/1.0 vr/1.0 sensors/1.0 configstore/1.1 configstore/1.0 media/omx/1.0 media/1.0 memtrack/1.0 dumpstate/1.0 camera/metadata/3.2 camera/provider/2.4 camera/device/3.2 camera/device/1.0 camera/common/1.0 tetheroffload/control/1.0 tetheroffload/config/1.0 I 60 Subsystem Conversions
  31. 31. Authors Files 300 3000 Commits 20k LOC ~1M I Code Stats
  32. 32. Qualcomm, Mediatek, Samsung/LSI, Huawei/HiSilicon, Motorola, Sony, LG Partners San Diego Taipei Seoul Onsite Teams 7 3 Direct on-site visits Partner Summits Android Bootcamp Executive Sync-ups Forums + 3 Qualcomm SoCs 1 Mediatek SoC 1 HiSilicon SoC 1 Exynos SoC SONY Huawei Samsung Oreo Launches / Upgrades 3/1 I Partner Outreach
  33. 33. Next Steps
  34. 34. Clone Merge Cherry-Pick Linux 4.9.y Android Common 4.9 msm-4.9 (Common SoC Kernel) MSMXXXX based device 1 MSMXXXX based device 2 MSMXXXX based device 3 Linux 4.9.y xLTS backports exynos-4.9 (Common SoC Kernel) mediatek-4.9 (Common SoC Kernel) I Kernel Unification
  35. 35. I There's More To Do ● Continued work with SoC Vendors ● Continued work on Kernel Unification ● Expanding test coverage ● Bringing the ecosystem together with Linaro
  36. 36. END

×