commit | e6074f52790f131d37c09a3911ef7659922b0832 | [log] [tgz] |
---|---|---|
author | Nick Maniscalco <maniscalco@google.com> | Wed Sep 19 10:19:31 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Sep 19 18:54:01 2018 +0000 |
tree | 2127b9fb0e08a9ec97f03d535612498991f1b477 | |
parent | e06ddf7f45fee1120a2b051f365efb2d4ed13836 [diff] |
[utest][arm64] Zero out zx_thread_state_vector_regs struct on arm64 On arm64, vector_regs_fill_test_values doesn't set the fpcr and fpsr fields so spin_with_vector_regs ends up loading stack garbage into fpcr and fpsr. It appears the memset was inadvertently placed after the "#if #defined(__x86_64__)". Move memset so that it's called on all platforms. Test: /boot/test/core/threads-test Change-Id: I25a941bf6e849205f574c6f9d75068b2aafcfa3e
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.