Android-x86
Fork


最近のコミット RSS

Rev. 日時 作者 メッセージ
d2616f9 2018-05-25 18:16:34 Chih-Wei Huang oreo-x86 Android 8.1.0 Release 29 (OPM4.171019.016.C1) -----BEGI...
e285944 2018-05-15 11:19:25 Chih-Wei Huang nougat-x86 We require text relocations Don't show annoying warnings.
3c75c11 2018-03-22 06:23:19 android-build-team Robot Snap for 4657601 from 3a927fc8396898cbc5ce6e9286e5b205e5e...
9a381df 2018-03-08 13:30:36 Chih-Wei Huang We require text relocations Don't show annoying warnings.
b7245a1 2018-03-07 17:41:26 Chih-Wei Huang Android 8.1.0 Release 18 (OPM5.171019.017) -----BEGIN P...
7947353 2018-02-12 17:51:26 Chih-Wei Huang cm-14.1-x86 Merge remote-tracking branch 'x86/nougat-x86' into cm-14....
01e64af 2018-01-04 17:12:07 Chih-Wei Huang android-x86-7.1-r1 android-x86-7.1-r2 Android 7.1.2 Release 36 (N2G48H) -----BEGIN PGP SIGNAT...
8d077c5 2017-12-08 16:38:43 Chih-Wei Huang Add syscalls ioperm and iopl
ebd024d 2017-12-08 16:38:43 Christopher R. Palmer linker: Allow text-relocs for x86 (only) This effectivel...
52213f1 2017-11-29 08:33:01 android-build-team Robot Snap for 4448085 from fcabaf45b7a17a2b67b3a7cc019da4b3969...

最近変更されたタグ

名前 Rev. 日時 作者
android-x86-7.1-r1 01e64af 2018-01-04 17:12:07 Chih-Wei Huang
android-x86-7.1-r2 01e64af 2018-01-04 17:12:07 Chih-Wei Huang
android-x86-6.0-r3 744d624 2017-03-23 23:58:48 Chih-Wei Huang
android-x86-6.0-r1 e025056 2016-05-05 18:32:25 Elliott Hughes
android-x86-6.0-r2 e025056 2016-05-05 18:32:25 Elliott Hughes
android-x86-4.4-r3 9df637a 2015-07-15 20:24:20 Chih-Wei Huang
android-x86-4.4-r2 78b58d8 2014-08-27 19:36:15 Chih-Wei Huang
android-x86-4.4-r1 d4213b8 2014-02-14 04:34:52 Pavel Chupin
android-x86-2.2-r2 217e95b 2011-06-10 00:18:09 Chih-Wei Huang
android-x86-2.2 d66c838 2010-12-16 20:39:00 Chih-Wei Huang
android-x86-1.6 a56cd49 2009-10-08 12:35:43 Chih-Wei Huang

ブランチ

名前 Rev. 日時 作者 メッセージ
oreo-x86 d2616f9 2018-05-25 18:16:34 Chih-Wei Huang Android 8.1.0 Release 29 (...
nougat-x86 e285944 2018-05-15 11:19:25 Chih-Wei Huang We require text relocations...
cm-14.1-x86 7947353 2018-02-12 17:51:26 Chih-Wei Huang Merge remote-tracking branc...
marshmallow-x86 744d624 2017-03-23 23:58:48 Chih-Wei Huang Android 6.0.1 release 79 ...
lollipop-x86 f7946c0 2017-02-17 10:30:14 Elliott Hughes Don't receive structs conta...
cm-14.0-x86 dc4f8f5 2016-10-06 06:52:04 Jaap Jan Meijer Merge remote-tracking branc...
cm-13.0-x86 232c5f0 2016-08-08 19:40:41 Jaap Jan Meijer Merge remote-tracking branc...
kitkat-x86 9df637a 2015-07-15 20:24:20 Chih-Wei Huang Add ppoll This is partial ...
jb-x86 4bfc661 2014-01-08 20:33:34 Chih-Wei Huang Add mmap64() The patch add...
ics-x86 23db25f 2012-07-13 15:30:27 David 'Digit' Turner linker: reduce size by near...
honeycomb-x86 48b6d2e 2011-12-30 14:41:04 Chih-Wei Huang input.h: update to EV_VERSI...
gingerbread-x86 e094c34 2011-11-13 17:56:21 William Esser fix PPTP VPN failures Chan...
froyo-x86 217e95b 2011-06-10 00:18:09 Chih-Wei Huang input.h: update to EV_VERSI...
eclair-x86 f423b5a 2010-04-15 18:46:10 Chih-Wei Huang Additions necessary for bus...
donut-x86 1cbd57c 2010-03-15 12:02:49 Dylan Simon Additions necessary for bus...

README.md

Working on bionic

What are the big pieces of bionic?

libc/ --- libc.so, libc.a

The C library. Stuff like fopen(3) and kill(2).

libm/ --- libm.so, libm.a

The math library. Traditionally Unix systems kept stuff like sin(3) and cos(3) in a separate library to save space in the days before shared libraries.

libdl/ --- libdl.so

The dynamic linker interface library. This is actually just a bunch of stubs that the dynamic linker replaces with pointers to its own implementation at runtime. This is where stuff like dlopen(3) lives.

libstdc++/ --- libstdc++.so

The C++ ABI support functions. The C++ compiler doesn't know how to implement thread-safe static initialization and the like, so it just calls functions that are supplied by the system. Stuff like __cxa_guard_acquire and __cxa_pure_virtual live here.

linker/ --- /system/bin/linker and /system/bin/linker64

The dynamic linker. When you run a dynamically-linked executable, its ELF file has a DT_INTERP entry that says "use the following program to start me". On Android, that's either linker or linker64 (depending on whether it's a 32-bit or 64-bit executable). It's responsible for loading the ELF executable into memory and resolving references to symbols (so that when your code tries to jump to fopen(3), say, it lands in the right place).

tests/ --- unit tests

The tests/ directory contains unit tests. Roughly arranged as one file per publicly-exported header file.

benchmarks/ --- benchmarks

The benchmarks/ directory contains benchmarks.

What's in libc/?

libc/
  arch-arm/
  arch-arm64/
  arch-common/
  arch-mips/
  arch-mips64/
  arch-x86/
  arch-x86_64/
    # Each architecture has its own subdirectory for stuff that isn't shared
    # because it's architecture-specific. There will be a .mk file in here that
    # drags in all the architecture-specific files.
    bionic/
      # Every architecture needs a handful of machine-specific assembler files.
      # They live here.
    include/
      machine/
        # The majority of header files are actually in libc/include/, but many
        # of them pull in a  for things like limits,
        # endianness, and how floating point numbers are represented. Those
        # headers live here.
    string/
      # Most architectures have a handful of optional assembler files
      # implementing optimized versions of various routines. The 
      # functions are particular favorites.
    syscalls/
      # The syscalls directories contain script-generated assembler files.
      # See 'Adding system calls' later.

  include/
    # The public header files on everyone's include path. These are a mixture of
    # files written by us and files taken from BSD.

  kernel/
    # The kernel uapi header files. These are scrubbed copies of the originals
    # in external/kernel-headers/. These files must not be edited directly. The
    # generate_uapi_headers.sh script should be used to go from a kernel tree to
    # external/kernel-headers/ --- this takes care of the architecture-specific
    # details. The update_all.py script should be used to regenerate bionic's
    # scrubbed headers from external/kernel-headers/.

  private/
    # These are private header files meant for use within bionic itself.

  dns/
    # Contains the DNS resolver (originates from NetBSD code).

  upstream-freebsd/
  upstream-netbsd/
  upstream-openbsd/
    # These directories contain unmolested upstream source. Any time we can
    # just use a BSD implementation of something unmodified, we should.
    # The structure under these directories mimics the upstream tree,
    # but there's also...
    android/
      include/
        # This is where we keep the hacks necessary to build BSD source
        # in our world. The *-compat.h files are automatically included
        # using -include, but we also provide equivalents for missing
        # header/source files needed by the BSD implementation.

  bionic/
    # This is the biggest mess. The C++ files are files we own, typically
    # because the Linux kernel interface is sufficiently different that we
    # can't use any of the BSD implementations. The C files are usually
    # legacy mess that needs to be sorted out, either by replacing it with
    # current upstream source in one of the upstream directories or by
    # switching the file to C++ and cleaning it up.

  malloc_debug/
    # The code that implements the functionality to enable debugging of
    # native allocation problems.

  stdio/
    # These are legacy files of dubious provenance. We're working to clean
    # this mess up, and this directory should disappear.

  tools/
    # Various tools used to maintain bionic.

  tzcode/
    # A modified superset of the IANA tzcode. Most of the modifications relate
    # to Android's use of a single file (with corresponding index) to contain
    # time zone data.
  zoneinfo/
    # Android-format time zone data.
    # See 'Updating tzdata' later.

Adding system calls

Adding a system call usually involves:

  1. Add entries to SYSCALLS.TXT. See SYSCALLS.TXT itself for documentation on the format.
  2. Run the gensyscalls.py script.
  3. Add constants (and perhaps types) to the appropriate header file. Note that you should check to see whether the constants are already in kernel uapi header files, in which case you just need to make sure that the appropriate POSIX header file in libc/include/ includes the relevant file or files.
  4. Add function declarations to the appropriate header file.
  5. Add the function name to the correct section in libc/libc.map.txt and run ./libc/tools/genversion-scripts.py.
  6. Add at least basic tests. Even a test that deliberately supplies an invalid argument helps check that we're generating the right symbol and have the right declaration in the header file, and that you correctly updated the maps in step 5. (You can use strace(1) to confirm that the correct system call is being made.)

Updating kernel header files

As mentioned above, this is currently a two-step process:

  1. Use generateuapiheaders.sh to go from a Linux source tree to appropriate contents for external/kernel-headers/.
  2. Run update_all.py to scrub those headers and import them into bionic.

Updating tzdata

This is fully automated (and these days handled by the libcore team, because they own icu, and that needs to be updated in sync with bionic):

  1. Run update-tzdata.py in external/icu/tools/.

Verifying changes

If you make a change that is likely to have a wide effect on the tree (such as a libc header change), you should run make checkbuild. A regular make will not build the entire tree; just the minimum number of projects that are required for the device. Tests, additional developer tools, and various other modules will not be built. Note that make checkbuild will not be complete either, as make tests covers a few additional modules, but generally speaking make checkbuild is enough.

Running the tests

The tests are all built from the tests/ directory.

Device tests

$ mma # In $ANDROID_ROOT/bionic.
$ adb root && adb remount && adb sync
$ adb shell /data/nativetest/bionic-unit-tests/bionic-unit-tests32
$ adb shell \
    /data/nativetest/bionic-unit-tests-static/bionic-unit-tests-static32
# Only for 64-bit targets
$ adb shell /data/nativetest64/bionic-unit-tests/bionic-unit-tests64
$ adb shell \
    /data/nativetest64/bionic-unit-tests-static/bionic-unit-tests-static64

Note that we use our own custom gtest runner that offers a superset of the options documented at https://github.com/google/googletest/blob/master/googletest/docs/AdvancedGuide.md#running-test-programs-advanced-options, in particular for test isolation and parallelism (both on by default).

Device tests via CTS

Most of the unit tests are executed by CTS. By default, CTS runs as a non-root user, so the unit tests must also pass when not run as root. Some tests cannot do any useful work unless run as root. In this case, the test should check getuid() == 0 and do nothing otherwise (typically we log in this case to prevent accidents!). Obviously, if the test can be rewritten to not require root, that's an even better solution.

Currently, the list of bionic CTS tests is generated at build time by running a host version of the test executable and dumping the list of all tests. In order for this to continue to work, all architectures must have the same number of tests, and the host version of the executable must also have the same number of tests.

Running the gtests directly is orders of magnitude faster than using CTS, but in cases where you really have to run CTS:

$ make cts # In $ANDROID_ROOT.
$ adb unroot # Because real CTS doesn't run as root.
# This will sync any *test* changes, but not *code* changes:
$ cts-tradefed \
    run singleCommand cts --skip-preconditions -m CtsBionicTestCases

Host tests

The host tests require that you have lunched either an x86 or x8664 target. Note that due to ABI limitations (specifically, the size of pthreadmutext), 32-bit bionic requires PIDs less than 65536. To enforce this, set /proc/sys/kernel/pidmax to 65536.

$ ./tests/run-on-host.sh 32
$ ./tests/run-on-host.sh 64   # For x86_64-bit *targets* only.

You can supply gtest flags as extra arguments to this script.

Against glibc

As a way to check that our tests do in fact test the correct behavior (and not just the behavior we think is correct), it is possible to run the tests against the host's glibc.

$ ./tests/run-on-host.sh glibc

Gathering test coverage

For either host or target coverage, you must first:

  • $ export NATIVE_COVERAGE=true
    • Note that the build system is ignorant to this flag being toggled, i.e. if you change this flag, you will have to manually rebuild bionic.
  • Set bionic_coverage=true in libc/Android.mk and libm/Android.mk.

Coverage from device tests

$ mma
$ adb sync
$ adb shell \
    GCOV_PREFIX=/data/local/tmp/gcov \
    GCOV_PREFIX_STRIP=`echo $ANDROID_BUILD_TOP | grep -o / | wc -l` \
    /data/nativetest/bionic-unit-tests/bionic-unit-tests32
$ acov

acov will pull all coverage information from the device, push it to the right directories, run lcov, and open the coverage report in your browser.

Coverage from host tests

First, build and run the host tests as usual (see above).

$ croot
$ lcov -c -d $ANDROID_PRODUCT_OUT -o coverage.info
$ genhtml -o covreport coverage.info # or lcov --list coverage.info

The coverage report is now available at covreport/index.html.

Running the benchmarks

Device benchmarks

$ mma
$ adb remount
$ adb sync
$ adb shell /data/nativetest/bionic-benchmarks/bionic-benchmarks
$ adb shell /data/nativetest64/bionic-benchmarks/bionic-benchmarks

You can use --benchmark_filter=getpid to just run benchmarks with "getpid" in their name.

Host benchmarks

See the "Host tests" section of "Running the tests" above.

Attaching GDB to the tests

Bionic's test runner will run each test in its own process by default to prevent tests failures from impacting other tests. This also has the added benefit of running them in parallel, so they are much faster.

However, this also makes it difficult to run the tests under GDB. To prevent each test from being forked, run the tests with the flag --no-isolate.

32-bit ABI bugs

off_t is 32-bit.

On 32-bit Android, off_t is a signed 32-bit integer. This limits functions that use off_t to working on files no larger than 2GiB.

Android does not require the _LARGEFILE_SOURCE macro to be used to make fseeko and ftello available. Instead they're always available from API level 24 where they were introduced, and never available before then.

Android also does not require the _LARGEFILE64_SOURCE macro to be used to make off64_t and corresponding functions such as ftruncate64 available. Instead, whatever subset of those functions was available at your target API level will be visible.

There are a couple of exceptions to note. Firstly, off64_t and the single function lseek64 were available right from the beginning in API 3. Secondly, Android has always silently inserted O_LARGEFILE into any open call, so if all you need are functions like read that don't take/return off_t, large files have always worked.

Android support for _FILE_OFFSET_BITS=64 (which turns off_t into off64_t and replaces each off_t function with its off64_t counterpart, such as lseek in the source becoming lseek64 at runtime) was added late. Even when it became available for the platform, it wasn't available from the NDK until r15. Before NDK r15, _FILE_OFFSET_BITS=64 silently did nothing: all code compiled with that was actually using a 32-bit off_t. With a new enough NDK, the situation becomes complicated. If you're targeting an API before 21, almost all functions that take an off_t become unavailable. You've asked for their 64-bit equivalents, and none of them (except lseek/lseek64) exist. As you increase your target API level, you'll have more and more of the functions available. API 12 adds some of the <unistd.h> functions, API 21 adds mmap, and by API 24 you have everything including <stdio.h>. See the linker map for full details.

In the 64-bit ABI, off_t is always 64-bit.

sigset_t is too small for real-time signals.

On 32-bit Android, sigset_t is too small for ARM and x86 (but correct for MIPS). This means that there is no support for real-time signals in 32-bit code.

In the 64-bit ABI, sigset_t is the correct size for every architecture.

time_t is 32-bit.

On 32-bit Android, time_t is 32-bit. The header <time64.h> and type time64_t exist as a workaround, but the kernel interfaces exposed on 32-bit Android all use the 32-bit time_t.

In the 64-bit ABI, time_t is 64-bit.

旧リポジトリブラウザで表示