[roll] Roll fuchsia [memory] Share attribution of Reference VMOs

VMOs created by reference have no page attributed to them by Zircon
APIs. We still want to register that these VMOs give access to their
parent and its memory in memory reports.

While we wait for a better way to detect reference VMOs, this change
fixes memory reports by also claiming parent VMOS of VMOs with no
contents.

BUG=393402141

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1254864
Original-Revision: 775c01bd5a699c5af6237ff3e811c87b455fab5c
GitOrigin-RevId: 430e3b14c28d158c3de9fc0fd75f58d69e4504bc
Change-Id: I2c3548debe94dbfa02dbd863277782200d9881c3
1 file changed
tree: d9e673c59eb7cee40ec3a0068a3737581877df37
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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 in one of the communication channels documented at get involved.

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.