[roll] Roll fuchsia [graphics] parking_lot -> fuchsia-sync

parking_lot has a few disadvantages for Fuchsia:

* adaptive spin w/ thread yields is great for microbenchmarks
  but has poor system-wide interactions with interrupts and
  the scheduler
* the parking lot abstraction doesn't convey priority inheritance
* implicit heap allocations make it unsuitable for use cases
  like instrumentation code

By contrast, fuchsia-sync is built directly on top of our libsync
and Zircon futexes. It tends to perform slightly worse on
microbenchmarks because it lacks an adaptive spin but feedback
from the kernel team is that we should see better whole-system
performance with this implementation. It's also possible that
changing synchronization strategies will surface new test flakes
in code with latent timing bugs.

Original-Bug: b/42169853
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/966895
Original-Revision: 0703ba740206ca88bc694bef5103adb62d5df2a9
GitOrigin-RevId: c3b20a87d03d7aedb14874b801ddbece1c6f5cde
Change-Id: I14fafc74c95b6a287ad3e78263cfee5f19f2fdcc
1 file changed
tree: dc306cacb50a1875909268b1e3a1b2b284ace8c2
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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 via the IRC channel #fuchsia on Freenode.

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.