[roll] Roll fuchsia [starnix] Always perform VMO-backed I/O w/ `Task`

Only `CurrentTask`'s address space may be mapped while in Normal mode
(if unified aspace is enabled). A `Task` may represent a task different
from the `CurrentTask` so we can't leverage unified aspaces when
performing memory I/O with a memory address belonging to a `Task`.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/972854
Original-Revision: f91be1987f0e0201e6e4a447c0abd81b6e92a031
GitOrigin-RevId: 12be1d3a87964bab8e768ac89c3c145e3e904c09
Change-Id: I91d3187646a58fffe6ad333c037a9ceada537113
1 file changed
tree: 98f6eabacbf1ee7f13d50cd2e0c9a93b2a3d1eae
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.