[roll] Roll fuchsia [docs] Update FIDL API rubric to recommend VMOs over fuchsia.mem/Buffer The kernel VMO object has undergone a few design iterations about how it tracked its size. It has two conflicting requirements for size: - Track the number of bytes logically contained in the memory - Track the number of bytes in the physical pages allocated for the object In one iteration the object tracked its size up to the next physical page boundary and did not remember the logical size. We introduced the FIDL type fuchsia.mem/Buffer as a VMO + uint64 pair to keep track of logical size. Later, we added kernel size tracking for logical size in the ZX_PROP_VMO_CONTENT_SIZE field. This means that a VMO can now be used directly everywhere that a fuchsia.mem/Buffer used to be required. This updates the rubric to recommend using VMOs directly with a note about the old recommendation. Original-Bug: 85452 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/585121 Original-Revision: c682769db02119ba001a7908d5563398b0c88e69 GitOrigin-RevId: ed71d6ed9abeaa79813e3bc836a5f2bc447e3724 Change-Id: Iaab774c234f9d91651ca1807b41a4ab81e2e7c1d
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.