Description
Android continues to find interesting new applications and problems to solve, both within and outside the mobile arena. Mainlining continues to be an area of focus, as do a number of areas of core Android functionality, including the kernel. Other areas where there is ongoing work include the low memory killer, dynamically-allocated Binder devices, kernel namespaces, EAS, userdata FS checkpointing and DT.
The working planning document is here:
https://docs.google.com/spreadsheets/d/1ymzOB4wapccX6t1b11T2-m9ny8buN7EuUqhCxrsmKe4
-
Martijn Coenen (Google)14/11/2018, 14:00
As of Linux 4.18, there are more than 30000 exported symbols in the kernel that can be used by loadable kernel modules. These exported symbols are all part of a global namespace, and there seems to be consensus among kernel devs that the export surface is too large, and hard to reason about. This talk describes a series of patches that introduce symbol namespaces, in order to more clearly...
Go to contribution page -
Suren Baghdasaryan (Google)14/11/2018, 14:15
Android's transition from in-kernel lowmemorykiller to userspace LMKD introduced a number of challenges including low-latency memory pressure detection and signaling, improving kill decision mechanisms and improving SIGKILL delivery latency. This talk will focus on the memory pressure detection mechanism based on PSI (Pressure Stall Information) recently developed by Johannes Weiner. It will...
Go to contribution page -
Christian Brauner14/11/2018, 14:30
The Binder driver currently does allow for the allocation of multiple binder devices through a kconfig option. However, this means how many binder devices the kernel will allocate is hard-coded and cannot be changed at runtime. This is inconvenient for scenarios where processes wish to allocate binder devices on the fly and the number of needed devices is not know in advance. For example, we...
Go to contribution page -
Patrick Bellasi (ARM)14/11/2018, 14:45
Despite the continuous and encouraging improvements, AOSP stable kernels have still a certain delta with respect to mainline. Some features are still unique to AOSP (e.g. WALT or SchedTune), others are back-port from mainline (e.g. idle loop optimization). Whenever an existing feature is modified, or a new/backported feature is proposed for an AOSP stable kernel, apart from a great code review...
Go to contribution page -
Daniel Rosenberg (Google), Paul Lawrence14/11/2018, 15:00
Android A/B updates allows roll back of updates that fail to boot, rolling back system, vendor partitions. BUT if update modifies the userdata partition before failing, cannot roll back modifications, and Android does not support updated userdata with old system/vendor partitions. If the file system supports snapshots, use them! We are adding snapshot support to F2FS. If no filesystem support,...
Go to contribution page -
David Anderson14/11/2018, 15:15
The Android OS is stored on signed, read-only partitions. Sizing these partitions is difficult. After a few years, a major OS pdate may no longer fit in a device's existing partitions. To use space more intelligently, we are introducing a userspace partitioning system based on dm-linear, similar to LVM.
Go to contribution page -
Sandeep Patil (Google)14/11/2018, 16:00
Android Oreo introduced some device tree bindings that MUST be specified for Android to be able to mount core partitions early (before SELinux enforcement) in the boot sequence for Project Treble. This talk is about the plans to get rid of that kernel / device tree dependency.. Instead, have a single global fstab for all and how the device tree fstab is to be deprecated.
Go to contribution page -
Joel Fernandes (Google)14/11/2018, 16:15
Android uses ashmem for sharing memory regions. We are trying to migrate all usecases of ashmem to memfd so that we can possibly remove the ashmem driver in the future from staging while also benefiting from using memfd for shared memory in Android, and contributing to improving memfd upstream. Note staging drivers are also not ABI and generally can be removed at anytime. This talk is about...
Go to contribution page -
Sandeep Patil (Google)14/11/2018, 16:30
Android kernels is a cocktail of upstream, android common kernels and big amounts of out-of-tree vendor code to support the SoCs and board peripherals. Android Pie now requires the board peripherals to be described using a device tree overlay. It is recommended that the drivers for those peripherals be loaded at boot time as a kernel module.
This discussion is intended to evaluate, seek...
Go to contribution page -
Alistair Strachan (Google)14/11/2018, 16:45
A short update on what Google is doing to help move partners away from proprietary interfaces for their display drivers and towards DRM/KMS and upstreaming.
Go to contribution page -
Laura Abbott14/11/2018, 17:00
Follow-up discussion to previous years about remaining work to be done to get ION driver merged upstream.
Go to contribution page -
Alistair Strachan14/11/2018, 17:15
Introduction to Cuttlefish VM
Go to contribution page -
Sandeep Patil (Google)14/11/2018, 17:30
Refereed track talk
Go to contribution page -
Karim Yaghmour (Opersys inc.)14/11/2018, 17:35
Collective progress report from Android MC 2018
Go to contribution page
