[vfs] Plumb a hash table around to track koids of tokens

This is a reland of 0f31d965b40a34d3da7447c6494fe4b641793dd1, now that
https://fuchsia-review.googlesource.com/c/garnet/+/248677 has landed
and all clients of libfs have correct header dependencies.

Original change's description:
> [vfs] Plumb a hash table around to track koids of tokens
> Rather than rely on set/get_cookie
> Test: fs unit tests
> Change-Id: I03d6b5de4eae90e8bbcef09958fb983b84e86e64

Test: fs unit tests
Change-Id: If1632111373282bd82be113e5760c255fc3ef0f0
11 files changed
tree: bf8193716b87163efba3ffdedcac2db85f9ba97c
  1. .clang-format
  2. .clang-tidy
  3. .dir-locals.el
  4. .gitignore
  9. README.md
  10. bootloader/
  11. docs/
  12. kernel/
  13. make/
  14. makefile
  15. navbar.md
  16. prebuilt/
  17. public/
  18. scripts/
  19. system/
  20. third_party/


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

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.