[roll] Roll fuchsia [kernel][vm] Only RangeChangeUpdate new CoW pages

Changes the clone path to only perform the RemoveWrite
RangeChangeUpdate on pages that are becoming CoW in the original
object. For unidirection clones, or clones against hidden parents, the
object being cloned, that might have mappings, is not needing to
perform copy-on-write for these pages. The new object must perform CoW,
but it doesn't exist yet and so has no mappings to invalidate.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1174233
Original-Revision: bd3c81a6a98f2a4a10817bd2e082c87387c6ca7d
GitOrigin-RevId: ac0e3839c757f8e4abc1ee6a2e1d05e324c04f07
Change-Id: I06fdbaebad15df677bbdb9b188181113a5d39bc4
1 file changed
tree: 40a6ee3e06367d3fd8942bead66f1698d4924086
  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.