Conveners
Android MC
- There are no conveners in this block
Android MC: Android reprise
- Karim Yaghmour (Opersys inc.)
Description
The Android microconference focuses on cooperation between the Android and Linux communities.
-
22/09/2021, 07:00
-
Todd Kjos (Google)22/09/2021, 07:05
Shortly after last year's Plumbers Conference the initial version of Generic Kernel Images (GKI) shipped in products based on the 5.4 kernel and Android 11. Devices that shipped with a 5.4 kernel are compatible with GKI. Kernel developers can replace the system image with the publicly available GSI image and replace the boot image with GKI and the device will boot and run Android 11.
In...
Go to contribution page -
Wei Wang (Google LLC), Quentin Perret (Google)22/09/2021, 07:20
Android has been benefiting from extensive use of the cgroup V1 interface to boost important tasks (the top-app and foreground groups) and limit unimportant ones (background). Our recent investigations have shown that combining CPU shares in addition to the newly introduced util-clamp feature can improve user-visible jank specifically in cases where background load is high. Unfortunately,...
Go to contribution page -
Alessio Balsini (Google), Paul Lawrence (Google)22/09/2021, 07:40
Stacking file systems based on FUSE are intended to go through complicated code paths implemented by the FUSE service, to enforce special access policies or manipulate data at runtime, based on what is the request received by the FUSE file system and the data in the lower file system.
Go to contribution page
Android relies on FUSE to enforce fine-grained access policies depending on file contents and requesting... -
Kailash Akilesh (Google), David Anderson (Google)22/09/2021, 08:00
dm-snapshot was a huge step forward for Android updates, but it can have greatly outsized disk space requirements for relatively small binary patches. Since dm-snapshot is closely tuned to the underlying exception store, it is not easily amenable to custom storage formats.
We have addressed this by implementing dm-snapshot in userspace via a new "dm-user" device-mapper module (like FUSE,...
Go to contribution page -
Wei Wang (Google LLC)22/09/2021, 08:35
The Android community has been using thermal core infrastructure for both Tj and Tskin solutions for years, and many thermal DVFS features from various Vendors/OEMs are built upon this, which usually require changes in the thermal governor and framework. However, with GKI introduced, it is now forbidden for OEM to put a custom thermal governor as a module which limits the solution and...
Go to contribution page -
Hridya Valsaraju22/09/2021, 08:55
A discussion on how we can find a cost-effective solution to attribute shared buffers to their allocating processes. Other than being useful for memory accounting/debugging, this could also lead the way to a solution to set limits on how much memory a process can allocate.
Go to contribution page -
Saravana Kannan22/09/2021, 09:15
fw_devlink has been enabled as "on" by default since version 5.13 and ensures a device's probe() is never called before its supplier devices have successfully bound to a driver.
This talk will be focusing on any remaining issues and future improvements. Some of the topics that'll be discussed include:
- Are there any unresolved issues on specific hardware due to fw_devlink=on?
- Are...
-
Wedson Almeida Filho, Miguel Ojeda22/09/2021, 09:35
The Rust for Linux project is adding support for the Rust language to the Linux kernel. We have a partial implementation of the Android Binder driver, as well as PL061 GPIO and NVMe drivers in Rust. Our goal is to make Rust available to kernel developers so that drivers can be written more expeditiously, with most potential memory bugs caught at compile-time, while at the same time preserving...
Go to contribution page -
Michel Lespinasse (Facebook), Mr Laurent Dufour22/09/2021, 10:10
Most Android vendors currently ship kernels that include Laurent Dufour's speculative page fault patchset from about 2.5 years ago. The patch set was rejected upstream at that time, due to code complexity, but provides a significant benefit to application startup times. I have been working on a new spin on the same basic idea, and came up with a patchset version which is (IMO) simpler and more...
Go to contribution page -
John Stultz (Linaro)22/09/2021, 10:30
While there are only a small number of devboards in AOSP, a number of vendors and community members have created external projects to enable their devices against AOSP.
Some examples:
- The GloDroid project: https://github.com/glodroid/glodroid_manifest
- android-rpi: https://github.com/android-rpi
- PocoF1 AOSP:...
-
John Stultz (Linaro), Karim Yaghmour (Opersys inc.)24/09/2021, 07:00
Come join and further discuss what was talked about at the earlier Android Microconference session. This provides space to allow folks who couldn't attend due to conflicts as well as for longer discussions that wouldn't fit into the earlier microconference session. We'll have a few topics scheduled, but also leave open some space for folks to propose their own items.
Go to contribution page -
24/09/2021, 07:05
Continued discussion from the Android Microconference.
Go to contribution page -
24/09/2021, 07:25
Continued discussion from the Android Microconference.
Go to contribution page -
24/09/2021, 08:00
-
24/09/2021, 08:20
-
24/09/2021, 08:40
Continued discussion from the microconf
- Continue default async boot -- what to do about mmc or others like it?
- How do we deal with the missing driver case?
- What do we do about parents depending on child devices.
- Any caveats/concerns with doing topological probing?
-
24/09/2021, 09:40
-
24/09/2021, 10:00
Continued discussion from microconference session
Go to contribution page -
24/09/2021, 10:20
Continued discussion from the Android Microconference.
Go to contribution page -
24/09/2021, 10:40
-
Over the past few years, the Android kernel team has increasingly worked closely with the rest of kernel community. It remains that many of the past Android microconferences were centred around the idea that it was primarily a sync point that enabled the Android kernel team to come and share what they had been doing in the past year.
Last year, GKI was the highlight of Android MC 2020....
Go to contribution page -
Over the past few years, the Android kernel team has increasingly worked closely with the rest of kernel community. It remains that many of the past Android microconferences were centred around the idea that it was primarily a sync point that enabled the Android kernel team to come and share what they had been doing in the past year.
Last year, GKI was the highlight of Android MC 2020....
Go to contribution page
