[sysmem] sysmem-connector zircon service

Make fuchsia_sysmem_Allocator2 a zircon service.  The service finds a
sysmem device instance and forwards the service request to the driver
to be served directly from there.

This way a non-driver client of sysmem doesn't need to hassle with
finding the sysmem device instance etc.

A similar garnet service will be added which shares the sysmem-connector
code, so to anticipate that, sysmem-connector is a ulib.

Tested: /system/test/sys/sysmem-test
Change-Id: Ie2773eb919b67a5bc53bd0a4e8b50921e33127fc
10 files changed
tree: 8096276e94b7effc6425134f5968d7cecac3c7ef
  1. bootloader/
  2. docs/
  3. kernel/
  4. make/
  5. prebuilt/
  6. public/
  7. scripts/
  8. system/
  9. third_party/
  10. .clang-format
  11. .clang-tidy
  12. .dir-locals.el
  13. .gitignore
  14. AUTHORS
  15. LICENSE
  16. MAINTAINERS
  17. makefile
  18. navbar.md
  19. PATENTS
  20. README.md
README.md

Zircon

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.