| commit | 60d152d5ee4298583a001127b652cbc2830ab124 | [log] [tgz] |
|---|---|---|
| author | Brian Swetland <swetland@google.com> | Thu Jul 13 11:33:57 2017 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jul 13 21:21:55 2017 +0000 |
| tree | d54b7da407a075680579b3518e0520751363288a | |
| parent | e803fd9b26f13fdabb7fb59d2ecba25359d66008 [diff] |
[syscalls] mx_handle_close(MX_HANDLE_INVALID) now returns MX_OK In the face of MX_POL_BAD_HANDLE, a bad handle error is fatal, but closing the "known never a handle" handle is similar to free(NULL) and is a reasonable strategy for cleanup. It's a different situation than "program double-closed a handle" or "program closed some random not a handle thing". Change-Id: I25410ee3040ec062700a4ca4d363841ca2b623c0
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.