| commit | 34b5b67a73d1f5a326ba88952595bab9ce90895c | [log] [tgz] |
|---|---|---|
| author | Jiwoong Lee <porce@google.com> | Wed Dec 12 18:03:59 2018 +0000 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Dec 12 18:04:08 2018 +0000 |
| tree | 8bb4c0d67b650afd20514b47087097e1245bbf08 | |
| parent | 491f9697340adc1cbdd341679d343cab78fc4a9c [diff] |
Revert "[bootserver] Show progress even for slow link" This reverts commit d10011b124af056c8a4d29890d63222e2f1694d4. Reason for revert: ZX-3183 Original change's description: > [bootserver] Show progress even for slow link > > The current logic of the progress update is not friendly > to slow or faulty links. > > The bootserver progress will be updated if any of following > conditions is met: > - The first packet is transferred > - One second or more passed since the last update > - 1024 or more packets sent since the last update > - 0.1% or more transfer is done since the last update > - The last packet is transferred since the last update > > Test: Each condition is emulated in a local setup. Confirmed the progress. > Change-Id: I3d65a39cd57e48c7516ae5ddb7d99a605350eb3c TBR=porce@google.com,eyw@google.com Change-Id: I89fb0dcf89c82a05d628a020240f14a8fc8ce909 No-Presubmit: true No-Tree-Checks: true No-Try: true
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.