| commit | ba8d3d1b4544e14efd216cbcb0ed11e41650a6df | [log] [tgz] |
|---|---|---|
| author | Shac Ron <sron@google.com> | Tue Dec 11 19:34:47 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Dec 13 23:35:11 2018 +0000 |
| tree | 60e1562120da96d27780c63d7468fd21c63f7630 | |
| parent | c3d8c8b9b4664ae62eb54d7ad8120b84f8c70748 [diff] |
[arm64] Replace some inline asm with arm_acle standard extensions. Replaced uses of inline assembly with language extensions where available. The extensions come from the <arm_acle.h>, which is included with gcc and clang, though the gcc version is woefully incomplete. Local arm_acle.h implements missing functionality. __arm_rsr/wsr for reading and writing MSRs. __dmb/dsb/isb for barriers. Some minor optimizations of ISB abundance, as they were previously included by default in ARM64_WRITE_SYSREG(). Conservatively removed some in cases where it seemed like they could be combined. The builtins provide the compiler more information about the operation that's being done, and allow improved optimization, instruction fencing, as well as safety (avoiding common assembler pitfalls such as incomplete side effect flags). Change-Id: I8b776d11095b333f6614d6e9a6c485efd32346e4 Test: Builds with Clang and GCC, manual verification of code gen, qemu boot.
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.