commit | 993242acb7c406983f6dc49f400ed31b4c4d52d4 | [log] [tgz] |
---|---|---|
author | Travis Geiselbrecht <travisg@google.com> | Mon Jun 18 16:35:19 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jun 19 18:56:22 2018 +0000 |
tree | 0101b02a25d730eaf20ee6beeb8366157cedfbaa | |
parent | 391f7a686d8214d9d83eaacc4de4b2723fe8862b [diff] |
[syscalls][vmo][op_range] add rights checking for different ops Test for the WRITE right for most of the ops, except the simple cache clean ops which cant modify data and thus only need read. This mirrors what arm64 already enforces for user vs supervisor permissions of the different cache ops. All but a pure invalidate is a read operation, permission wise. ZX-967 #done Change-Id: If45f774b5a2de478572e1bacbfc13baf0a4da667
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.