[roll] Roll fuchsia [kernel][vm] Dedicated VmObject hierarchy lock

Uses a global lock for all manipulations of parent/child relationships
in a VmObject.

Usage of this lock happens on VmObject creation/deletion in situations
where we are also either manipulating the heap and/or the AllVmosList
lock. As such this lock does not end up receiving any contention, due
to both being an infrequent operation and already effectively
serialized by the aforementioned other global locks.

Using a global hierarchy lock will simplify the fine locking
implementation.

Original-Bug: 338300943
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1200844
Original-Revision: 183d114a1754b353f3860c54b13ea204be38588d
GitOrigin-RevId: 5658241d427d1cdb176fbbd0bde2e5f6f1576043
Change-Id: Ic2d5ed6cd663bde22636a70e9500acf31820761a
1 file changed
tree: 4b57923d8d7159f6fb044da0a0a80c4c9753512c
  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.