Google Git
Sign in
fuchsia / fuchsia / 910c42476df82c3677bebaaff64b4c52d76651f4
commit910c42476df82c3677bebaaff64b4c52d76651f4[log] [tgz]
authorNick Kralevich <nnk@google.com>Tue Feb 13 14:09:15 2018 -0800
committerNick Kralevich <nnk@google.com>Thu Feb 15 08:10:19 2018 -0800
tree5c181f32353a56d00778345e51b716ee84462193
parente9483f9997cc5e5d32c3c44177f1dbc02a50494a [diff]
[libc] undef _POSIX_THREAD_PRIORITY_SCHEDULING

Posix allows for an implement to choose not to support thread scheduling
by ensuring that _POSIX_THREAD_PRIORITY_SCHEDULING is either not
defined, or defined to be -1.

 * http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/unistd.h.html
 * https://linux.die.net/man/7/posixoptions

Undefine _POSIX_THREAD_PRIORITY_SCHEDULING and remove function
prototypes associated with those functions. These functions are not used
by any fuchsia based caller.

Change-Id: I865743b37f69d2ef5e76e041e9ef41b662286930
10 files changed
tree: 5c181f32353a56d00778345e51b716ee84462193
  1. bootloader/
  2. docs/
  3. kernel/
  4. make/
  5. manifest/
  6. prebuilt/
  7. public/
  8. scripts/
  9. system/
  10. third_party/
  11. .clang-format
  12. .dir-locals.el
  13. .gitignore
  14. .travis.yml
  15. AUTHORS
  16. LICENSE
  17. makefile
  18. navbar.md
  19. PATENTS
  20. README.md
README.md

Zircon

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.