[syscalls] rename mx_handle_wait_*() to mx_object_wait_*()

These act on the object the handle refers to, not the handle itself.

Compatibility wrappers are provided to ensure existing code
continues to compile, link, and run.  Later we will deprecate
the wrappers and eventually remove them.

Change-Id: Icf69e75f7e0c060ba6026343f9d26ff9da4317d9
28 files changed
tree: 185b3abc26f252edf4cb8417216e3db5dccb4318
  1. bootloader/
  2. docs/
  3. infra/
  4. kernel/
  5. prebuilt/
  6. scripts/
  7. system/
  8. third_party/
  9. .clang-format
  10. .dir-locals.el
  11. .gitignore
  12. .travis.yml
  13. AUTHORS
  14. LICENSE
  15. makefile
  16. README.md
README.md

Magenta

Magenta is the core platform that powers the Fuchsia OS. Magenta 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 Magenta Git repository is located at: https://fuchsia.googlesource.com/magenta

A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/magenta

The Magenta 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 10s, not 100s of syscalls.

Magenta syscalls are generally non-blocking. The wait (one, many, set) family of syscalls, ioport reads, and thread sleep being the notable exceptions.

This page is a non-comprehensive index of the magenta documentation.