[roll] Roll fuchsia [kernel][vm] Plumb write flag on the VMO pin path

Pass down the IOMMU write permission to the VMO pinning code so that it
can distinguish between pinning for a read and a write. This is
essential to dirty track pages in the case of a pinned write. Once the
pages have been pinned and mapped in the IOMMU, the VM system will no
longer be able to trap the writes in order to mark pages dirty.

This commit just plumbs through the write flag but does not actually use
it yet. That will follow in a future CL. There is no change in behavior
with this commit.

Original-Bug: 63989
Run-All-Tests: true
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/693382
Original-Revision: ffe1835bdd076eb43b56d48e4032a429c1ba4780
GitOrigin-RevId: 1ab2a20bf5e1f6f92701897cd7f0a7b3feec30bd
Change-Id: I722161fb8b4549a78c356dfe83da8ca737cdd589
1 file changed
tree: a18d0cf6f5bba8b31c33e4f0fa9d9908666af2b5
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.