[roll] Roll fuchsia [kernel][vm] ReclaimPage locking refactor

Changes ReclaimPage to not acquire the lock before calling the specific
reclamation method, requiring them to acquire the lock internally
themselves. This causes the specific methods to have to duplicate some
checks, although they were already largely duplicated for ASSERTs
anyway, but will simplify locking and deferred updates in future
changes.

Original-Bug: 338300943
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1230604
Original-Revision: 985c2bcb5d6839c92691b70f474ef7e61084b3b6
GitOrigin-RevId: 2517b0b15908d49f206dcd1e09e323c57d6c7e4f
Change-Id: Ia96e1d9c5ecd5f04422a48f9dcd7d9ba8de1d2fe
1 file changed
tree: 1344447b6264a0d6e809e66ee383fde29ac4d07f
  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.