[roll] Roll fuchsia [kernel][vm] Explicitly construct vm_page

Instead of relying on a memset(0) to correctly initialize a vm_page
perform an explicit construction step. This has the side effect of not
requiring the vm_page to be trivially constructible.

Examining the objdump the resulting construction does not invoke
memset, but does perform an optimal loop unrolled zeroing.

NO_IFTTT=vm_page size/layout is not changing

Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1705354
Original-Original-Revision: 4c026b5dbdd7588fe54461c048103d3d952a99ca
GitOrigin-RevId: 263dcae666ada4e6808f2f905490eb5b6490061d
Change-Id: I5ea783a2047ff811dacb1295b901d2114104d384
1 file changed
tree: 30dd7e90cb854bee58de198e84e63fd7e9f77d5f
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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.