[roll] Roll fuchsia Reland "[diagnostics] Add new VMO size header field to C++ impl"

This is a reland of commit 7fbc17485ebda9e94154c058f593633c50756bba

Set the initial value of the VMO size field to VMO max size instead of
min size. Since the rust implementation already uses the size field
it needs to be set to the maximum value as long as it's not properly
updated (which will happen in the following change).

Original change's description:
> [diagnostics] Add new VMO size header field to C++ impl
>
> To be able to track the size of the VMO we decided to add a new size
> which allows us to coarsely track the size of the inspect VMO.
>
> This change increases the order of the header to 1 and thus the size to
> 32 byte from previously 16 byte and adds the new field to the VMO header.
>
> Original-Bug: 41448
> Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/689525

Original-Bug: 41448
Run-All-Tests: true
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/714942
Original-Revision: 2bc5ef2d55b000148ed7601fe6ac731eaeea2d30
GitOrigin-RevId: cb935eecc9996c639ca50947429189544466ce24
Change-Id: Ib301ed928310f4e385f089aa0a5f649f431e0993
1 file changed
tree: f7c1ffb60060f42bfdc3af88bb9676d4b89372e8
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.