[roll] Roll fuchsia [starnix] Avoid `MemoryAccessorExt` in `MemoryManager` ...impls of atomic load and store operations. `MemoryManager`'s calls to `MemoryAccessorExt` is replaced with direct VMO-based usercopy methods on `MemoryManager` itself. This prepares us for a later change that drops the `MemoryAccessor` impl from `MemoryManager` so that Starnix is forced to use a `CurrentTask`, `Task`, or some other implementation to perform copies to/from a user's aspace. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/975613 Original-Revision: 16eced4a67c8dd1f54b60c7810f4a2ec0ff55680 GitOrigin-RevId: 1b8ba5a9bc28399c44889bfde43bcfa46005c166 Change-Id: I24085383853e2c4bb05386f62ddc9c83697f843e
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.