[roll] Roll fuchsia [kernel][vm] Populated bytes: Clarify thread safety of ContinuousAttributionTracker

Comment that ContinuousAttributionTracker is not thread safe. Remove
VmCowPages::DebugGetContinuousAttributionTracker because it allows
unsynchronized modification of the count without a thread annotation
warning.

Directly expose a locking DebugGetPopulatedSlotsCount method.

Update the unittests to use the new method.

Original-Bug: 465175014
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1501891
Original-Revision: dedce9c6c0db1d6372ab392f2a6642546ee85965
GitOrigin-RevId: 1d132d4ae0d47b5dde94763fa3669ed1c03c9419
Change-Id: Ib9381573536eba5ef282ab2db659574cabbf8a5c
1 file changed
tree: 120188b5afe3e9a1f3593590bb606a33f7a43f79
  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.