Difference between revisions of "Android Kernel Features"

From eLinux.org
Jump to: navigation, search
(Binder: refactor and add link to Kobayashi binder presentation)
(Binder: move binder info to a separate page)
Line 4: Line 4:
=== Binder ===
=== Binder ===
Binder is an Android-specific interprocess communication mechanism, and remote method invocation system
Binder is an Android-specific interprocess communication mechanism, and remote method invocation system
* That is, one Android process can call a routine in another Android process, using binder to indentify the method to invoke and pass the arguments between processes.
See [[Android Binder]]
* note that Android does NOT use SysV IPC for interprocess communication
* A good overview of binder is in the presentation [http://blog.kmckk.com/archives/3676340.html Inter-process method invocation in Android] by Tetsuyuki Kobayashi
==== History ====
* Originally a feature in BeOS, Binder was a central construct for encapsulating software interfaces. One of the architects behind this mechanism was Dianne Hackborn, who is now a key employee at Android/Google. For more history see [http://www.osnews.com/story/13674/Introduction_to_OpenBinder_and_Interview_with_Dianne_Hackborn this interview].
* The Linux version of Binder was originally derived from a project by PalmSource to implement a CORBA-like message-passing or method invocation system.  Documentation on that system is at: http://www.angryredplanet.com/~hackbod/openbinder/docs/html/index.html
==== Notes ====
* implementation is at: <tt>drivers/misc/binder.c</tt>, with include file: <tt>include/linux/binder.h</tt>
=== ashmem ===
=== ashmem ===

Revision as of 10:05, 23 May 2011

List of Kernel features unique to Android

Here is a list of changes/addons that the Android Project made to the linux kernal, these changes are not part of the standard kernel and are only available in the Android kernel branch, some changes was part of the "staging" driver area in the stock kernel but was removed due to lack of support See Greg KH blog post on -staging for 2.6.33, where he announces to remove various Android drivers from -staging.


Binder is an Android-specific interprocess communication mechanism, and remote method invocation system See Android Binder


  • ashmem - Android shared memory
    • implementation is in mm/ashmem.c

According to the Kconfig help "The ashmem subsystem is a new shared memory allocator, similar to POSIX SHM but with different behavior and sporting a simpler file-based API."

Apparently it better-supports low memory devices, because it can discard shared memory units under memory pressure.

To use this, programs open /dev/ashmem, use mmap() on it, and can perform one or more of the following ioctls:


From a thread on android-platform source

You can create a shared memory segment using:

    fd = ashmem_create_region("my_shm_region", size); 
    if(fd < 0) 
        return -1; 
    data = mmap(NULL, size, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); 
    if(data == MAP_FAILED) 
        goto out; 

In the second process, instead of opening the region using the same name, for security reasons the file descriptor is passed to the other process via binder IPC.

The libcutils interface for ashmem consists of the following calls: (found in system/core/include/cutils/ashmem.h)

  • int ashmem_create_region(const char *name, size_t size);
  • int ashmem_set_prot_region(int fd, int prot);
  • int ashmem_pin_region(int fd, size_t offset, size_t len);
  • int ashmem_unpin_region(int fd, size_t offset, size_t len);
  • int ashmem_get_size_region(int fd);


  • PMEM - Process memory allocator
    • implementation at: drivers/misc/pmem.c with include file at: include/linux/android_pmem.h
    • Brian Swetland says:
The pmem driver is used to manage large (1-16+MB) physically contiguous
regions of memory shared between userspace and kernel drivers (dsp, gpu,
etc).  It was written specifically to deal with hardware limitations of
the MSM7201A, but could be used for other chipsets as well.  For now,
you're safe to turn it off on x86.

David Sparks wrote the following: source

2. ashmem and pmem are very similar. Both are used for sharing memory 
between processes. ashmem uses virtual memory, whereas pmem uses 
physically contiguous memory. One big difference is that with ashmem, 
you have a ref-counted object that can be shared equally between 
processes. For example, if two processes are sharing an ashmem memory 
buffer, the buffer reference goes away when both process have removed 
all their references by closing all their file descriptors. pmem 
doesn't work that way because it needs to maintain a physical to 
virtual mapping. This requires the process that allocates a pmem heap 
to hold the file descriptor until all the other references are closed. 

3. You have the right idea for using shared memory. The choice between 
ashmem and pmem depends on whether you need physically contiguous 
buffers. In the case of the G1, we use the hardware 2D engine to do 
scaling, rotation, and color conversion, so we use pmem heaps. The 
emulator doesn't have a pmem driver and doesn't really need one, so we 
use ashmem in the emulator. If you use ashmem on the G1, you lose the 
hardware 2D engine capability, so SurfaceFlinger falls back to its 
software renderer which does not do color conversion, which is why you 
see the monochrome image. 


  • logger - system logging facility
    • This is the kernel support for the 'logcat' command
    • The kernel driver for the serial devices for logging are in the source code drivers/misc/logger.c
    • See Android logger for more information about the kernel code
    • See Android Logging System for an overview of the system it supports


  • wakelock - used for power management files kernel/power/wakelock.c
    • Holds machine awake on a per-event basis until wakelock is released
    • See Android Power Management for detailed information

oom handling

  • oom handling modifications
    • lowmem notifications
    • implementation at: drivers/misc/lowmemorykiller.c
    • also at: security/lowmem.c

Informally known as the Viking Killer, the OOM handler simply kills processes as available memory becomes low. The kernel module follows rules for this that are supplied from user space in two ways:

1. init writes information about memory levels and associated classes:

  • The write value must be consistent with the above properties.
  • Note that the driver only supports 6 slots, so we have combined some of the classes into the same memory level; the associated processes of higher classes will still be killed first.
    • From /init.rc:
   write /sys/module/lowmemorykiller/parameters/adj 0,1,2,4,7,15
   write /sys/module/lowmemorykiller/parameters/minfree 2048,3072,4096,6144,7168,8192

2. User space sets the oom_adj of processes to put them in the correct class for their current operation. This redefines the meaning of oom_adj from that used by the standard OOM killer to something that is more aggressive and controlled.

These oom_adj levels end up being based on the process lifecycle defined here: http://developer.android.com/guide/topics/fundamentals.html#proclife


This is the kernel implementation to support Android's AlarmManager. It lets user space tell the kernel when it would like to wake up, allowing the kernel to schedule that appropriately and come back (holding a wake lock) when the time has expired regardless of the sleep state of the CPU.

paranoid network security

timed output / timed gpio

Generic gpio is a mechanism to allow programs to access and manipulate gpio registers from user space.

Timed output/gpio is a system to allow chaning a gpio pin and restore it automatically after a specified timeout. See drives/misc/timed_output.c and drives/misc/timed_gpio.c This expose a user space interface used by the vibrator code.

On ADP1, there is a driver at:

# cd /sys/bus/platform/drivers/timed-gpio
# ls -l
--w-------    1 0        0            4096 Nov 13 02:11 bind
lrwxrwxrwx    1 0        0               0 Nov 13 02:11 timed-gpio -> ../../../../devices/platform/timed-gpio
--w-------    1 0        0            4096 Nov 13 02:11 uevent
--w-------    1 0        0            4096 Nov 13 02:11 unbind

Also, there is a device at:

# cd /sys/devices/platform/timed-gpio
# ls -lR
lrwxrwxrwx    1 0        0               0 Nov 13 01:34 driver -> ../../../bus/platform/drivers/timed-gpio
-r--r--r--    1 0        0            4096 Nov 13 01:34 modalias
drwxr-xr-x    2 0        0               0 Nov 13 01:34 power
lrwxrwxrwx    1 0        0               0 Nov 13 01:34 subsystem -> ../../../bus/platform
-rw-r--r--    1 0        0            4096 Nov 13 01:34 uevent

-rw-r--r--    1 0        0            4096 Nov 13 01:34 wakeup


This allows saving the kernel printk messages to a buffer in RAM, so that after a kernel panic they can be viewed in the next kernel invocation, by accessing /proc/last_kmsg.

[Would be good to get more details on how to set this up and use it here!] [I guess this is something like pramfs?]

other kernel changes

Here is a miscellaneous list of other kernel changes in the mistral Android kernel:

  • switch events - drivers/switch/* userspace support for monitoring GPIO via sysfs/uevent used by vold to detect USB
  • USB gadget driver for ADB - drivers/usb/gadget/android.c
  • yaffs2 flash filesystem
  • support in FAT filesystem for FVAT_IOCTL_GET_VOLUME_ID
  • RAM console
  • and more...

Kernel configuration options

The file Documentation/android.txt has a list of required configuration options for a kernel to support an Android system.