[roll] Roll fuchsia [kernel][vm] Use CriticalMutex for VMO and related locks.

Mitigate the impact of preemption while holding widely shared VM locks,
including VMO, all VMOs list, and discardable VMOs list locks using the
time bounded preemption disabled CriticalMutex. Preemption while holding
any of these locks can cause cascading delays throughout the system.

In particular, this CL mitigates:
- Preemption while holding the VMO lock in memory_monitor and audio_core
  pin-executable-memory causing delays in handling page faults.
- Preemption in any process while holding the AllVmosLock while creating
  a VMO.
- Preemption in any process while holding the DiscardableVmosLock.

Original-Bug: b/234776870
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/709282
Original-Revision: eb08814767aa073f41aee037941bebaae26c3b06
GitOrigin-RevId: 82f9ffee9c72f9b0977b553a703e217e3de03fe6
Change-Id: Ia78369ca0cf86f27ab73b59f4bdfc726bf277e9e
1 file changed
tree: 3ee816af54cf8ff12ae4ed14369f343190713665
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.