[roll] Roll fuchsia [starnix] Avoid exclusive lock in user vmar check

Check if mappings in user vmar ranges are lazy under a shared
read lock before acquiring the exclusive write lock. Since pages
are typically already resident, this eliminates lock contention in
the common path during futex operations.

Original-Original-Bug: 313523356
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1640934
Original-Original-Revision: 87884986e189d1fef4bd5d9072f784e6f981ab22
GitOrigin-RevId: fd0a9c6045819d7d4ef9d09c0aff09007061929e
Change-Id: Iff44847bdd107a174645431275519defcaf405ad
1 file changed
tree: 109d66af7e85381e72c03932c4dd91e780e3c0bb
  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.