{"id":53000,"date":"2019-11-21T00:00:00","date_gmt":"2019-11-20T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/google-rabotaet-nad-ispolzovaniem-obychnogo-yadra-linux-v-android"},"modified":"2020-02-18T14:00:50","modified_gmt":"2020-02-18T11:00:50","slug":"google-rabotaet-nad-ispolzovaniem-obychnogo-yadra-linux-v-android","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/google-rabotaet-nad-ispolzovaniem-obychnogo-yadra-linux-v-android","title":{"rendered":"Google is working on using a regular Linux kernel in Android","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

At the recent Linux Plumbers Conference 2019, Google told<\/a><\/noindex> discussed the development of the<\/a><\/noindex> of integrating changes developed in the kernel variant<\/a><\/noindex> for the Android platform. The ultimate goal is to provide a common kernel for Android usage, instead of preparing separate builds for each device based on an Android-specific branch. Android Common Kernel<\/a><\/noindex>. This goal has already been partially achieved, and the conference showcased an Android smartphone, the Xiaomi Poco F1, with firmware based on a standard unmodified Linux kernel.<\/p>\n

Once the project is ready, suppliers will be encouraged to provide a base kernel based on the main Linux kernel. Components for hardware support will be supplied by vendors only as additional kernel modules, without applying patches to the kernel. The modules must ensure compatibility with the main kernel regarding kernel symbol namespaces. All changes affecting the main kernel will be promoted upstream. To maintain compatibility with proprietary modules in LTS branches, it is proposed to stabilize the kernel's API and ABI, which will allow module compatibility with updates for each common kernel branch.<\/p>\n

\"Google<\/center><\/p>\n

In a year, features such as the PSI (Pressure Stall Information) subsystem for analyzing wait times for various resources (CPU, memory, I\/O), the BinderFS pseudo-filesystem for the Binder inter-process communication mechanism, and the Energy Aware Scheduling (EAS) task scheduler have been integrated from the Android kernel edition into the main Linux kernel. In the future, Android is planned to transition from the specific SchedTune scheduler to a new subsystem developed by ARM called UtilClamp, based on cgroups2 and the kernel's native mechanisms.<\/p>\n

\"Google<\/center><\/p>\n

Let\u2019s remember that until now, the kernel for the Android platform went through several preparation stages:<\/p>\n