[kernel][cond] have condition vars match events and let you wake without reschedule

Returns the number of woken threads so you can delay rescheduling for a bit and avoid
the stampede of threads that just hit the mutex.

Not sure cvars in the kernel are really the right solution in the long run,
we may want to place these uses with something more tuned for exactly the situation.

Change-Id: I2279087458adbd8c5fd9ce35adff5412492aff0a
8 files changed
tree: 90a2cd8b2c1fa7b76ab5d4b209d2257ac28f7c97
  1. .clang-format
  2. .dir-locals.el
  3. .gitignore
  4. .travis.yml
  7. README.md
  8. docs/
  9. kernel/
  10. makefile
  11. prebuilt/
  12. scripts/
  13. system/
  14. third_party/


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.