| commit | 2bd1616076294e26d594075e29a72dbfeac629cf | [log] [tgz] |
|---|---|---|
| author | Carlos Pizano <cpu@chromium.org> | Thu Apr 27 09:53:08 2017 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed May 03 23:06:01 2017 +0000 |
| tree | 3a54f46112ca512c04a476719c209ee2976fedc9 | |
| parent | 5f385d8ecbed5d0ef50d5b90f8f15f954265c6c8 [diff] |
[kernel][magenta] Implement policy guts .. and wire to one syscall. This CL shows the end-to-end process of computing policy and applying it to a single case: mx_channel_create(). It also changes how policy is declared making it simpler to process: now regardless of the condition, the policy have a single set of constants MX_ACTION_POL_DENY, MX_POL_ACTION_ALLOW and so on. Change-Id: I2b09ce54af3c1ab3332e7b2ab160cd5b768e8dd5
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.