Description
The Android Micro Conference brings the upstream community and Android systems developers together to discuss issues and changes to the Android platform and their dependencies and interactions with the Linux kernel, allowing for collaboration on solutions for upstream.
Some highlights of progress made since last year’s MC:
-
For fw_devlink, got post-init-providers accepted into DT schema, as proposed and discussed at LPC. Additionally, as proposed at LPC, fw_devlink=rpm was made the default, so fw_devlink now enforces runtime PM ordering too.
-
After discussions last year on board-id property being used to pick a DTB by the bootloader, patches for a shared solution were submitted upstream.
- Initial Pixel6 support has landed upstream, such that it can boot to console with 6.9-rc kernels.
- Having the chance to connect with the right glibc people facilitating a consensus between the bionic folks and the clang driver/lld ELF owners on an approach to mitigate the VMA (Virtual Memory Area) slab memory increase caused by the dynamic linker in devices supporting larger than 4KB page sizes.
- Discussion with the BPF ring buffer maintainer led to the event driven memory notifications from the kernel for low memory killer daemon (lmkd).
Also, listening to feedback from last year, we are planning to have slightly longer slots, so talks are not so rushed, but that also means we will have to be even more selective with topics.
Potential discussion topics for this year include:
- Device Longevity
- Power usage modeling and simulations
- Unified bootloader efforts
- The Power of Perfetto
- Using & tuning with the (soon to be) upstream Dynamic Energy Model
- Android Storage features: ublk, ureadhead, FUSE-BPF
- AVF updates&plans / pVM firmware
- More discussion on 16k pages
- RISCV updates
-
Todd Kjos (Google)20/09/2024, 10:00
In pursuit of a stronger defense against kernel security issues, the Android ecosystem has been evolving since 2017 to more aggressively follow the upstream stable kernels. To support this evolution, the Android Common Kernel has been transformed from a reference kernel used primarily to cherry-pick features and security bug fixes into a binary release of a kernel that is kept up-to-date with...
Go to contribution page -
Serban Constantinescu (source.dev), Luca Weiss (Fairphone), Karim Yaghmour (Opersys inc.)20/09/2024, 10:20
The Android Open Source Project (AOSP) is an extremely attractive Linux-based stack for HMIs and all manner of richly-connected devices. Its ever expanding and industry-leading handset-grade feature-set, universally-known user experience and mostly permissive licensing make it a great fit for a large number of products. Despite all its benefits, however, keeping an AOSP-enabled device...
Go to contribution page -
Mr Chris Simmonds20/09/2024, 10:40
AOSP is used in many different types of device, not just smart phones and tablets, but also digital advertising, white boards, building entry systems, and more. Consequently, there are a large number of AOSP developers, but where are they? It's like
Go to contribution page
the Fermi Paradox, but for software engineers. Contrast this with the community around, for example, the Yocto Project, which is active and... -
Mr Dmitrii Merkurev (Google), Mr Ram Muthiah (Google)20/09/2024, 11:00
Context I'm going to provide:
- Android bootflow (current situation, problems, focus on bootloaders fragmentation which leads to upstream features adoption delays)
- Overview of the boot standards (UEFI, Coreboot, etc)
- GBL proposal (revealing early specs, focus on OEM requirements/customizations)
- How to try GBL with Cuttlefish
Potential discussion points:
1....
Go to contribution page -
Prakash Gupta (Qualcomm)20/09/2024, 11:20
Kernel supports default cma and system dmabuf heaps. In order to support protected usecase, additional heap types needs to be supported.
There are quite a few downstream dmabuf heaps maintained by vendors to support protected usecase. There is need to provide generic framework, which will reduce fragmentation of such dmabuf heap types.
The proposed restricted dmabuf heaps will support...
Go to contribution page -
T.J. Mercier (Google - Android Kernel Team)20/09/2024, 12:00
This talk will cover the status of recent changes in Android and upstream related to memory control groups, planned work, and outstanding issues.
Here are some details:
Updates:
- memcg v2 can now be used in A15 with
PRODUCT_MEMCG_V2_FORCE_ENABLEDor vendor overrides of cgroups.json - Control of memcg activation depth is queued for A16 (Reduction in kernel...
- memcg v2 can now be used in A15 with
-
Juan Yescas, Mr Kalesh Singh20/09/2024, 12:20
Android's transition to 16kb page sizes necessitates a comprehensive overhaul of device components to ensure seamless compatibility and optimal performance. This presentation will delve into the critical modifications required across the entire software stack:
- Bootloader: We'll explore the necessary adjustments to the bootloader to accommodate the 16kb page size, ensuring a smooth...
-
Akilesh Kailash20/09/2024, 12:40
This presentation delves into the ongoing upstream work: ublk zero copy based io_uring effort:
https://lore.kernel.org/io-uring/06c5f635-b065-4ff1-9733-face599ddfe3@gmail.com/T/#m6c99306b44992ee8fc12ad4e9d7a28cd59e081bb
The talk will focus on:
1: Why ublk zero copy is required in Android and how it will be used. Will explore the use cases that necessitate the implementation of ublk...
Go to contribution page -
Barry Song, Mr Chuanhua Han, Mr Hailong Liu, Kalesh Singh (Google), Yu Zhao (Google)20/09/2024, 13:00
OPPO has deployed ARM64 CONT-PTE-based large folios (mTHP) on millions of real phones and is committed to contributing the code to Linus' tree, GKI, and the open-source community.
This topic will primarily discuss the opportunities and challenges encountered by OPPO in memory allocation, memory reclamation, LRU, and mTHP compression/decompression in zsmalloc/zRAM during the deployment of...
Go to contribution page -
-
