[roll] Roll fuchsia [sysmem] External sysmem heaps use GetVmoInfo

External sysmem heaps need to stop depending on the koid of sysmem
VMOs to unblock changes to how sysmem arranges its VMOs. In
particular, the parent VMO of a sysmem-provided VMO will no longer
match the koid of the VMO returned by the external heap.

In addition, the heap.fidl protocol doesn't need to be splitting up
AllocateVmo and CreateResource, so now it just has AllocateVmo and
some minor related tweaks. This is more consistent with how allocation
and deletion normally work, and is easier to maintain.

BUG: b/284073556
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/921973
Original-Revision: 40d419c83ea888c67c77c0f7594a00d604fa56e0
GitOrigin-RevId: 47ffeea7efd63c7508c5d08ba2430d537a03efc5
Change-Id: I800a8445e2cf5680bb1bc3cfaa7e3c8ec8be5c0e
1 file changed
tree: 7a50d64205bb94d9e5bd5da9650ba9cb2a01d1db
  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.