| commit | 066a6e641a6e112e71a391ad485c63cf4e95df09 | [log] [tgz] |
|---|---|---|
| author | Dustin Green <dustingreen@fuchsia.infra.roller.google.com> | Thu Oct 05 06:15:09 2023 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 04 23:17:24 2023 -0700 |
| tree | ca1eaaf770712dadc03ece943c489e71a21aed84 | |
| parent | 07eadb78339d35891c094f322e1330f82a1a8bba [diff] |
[roll] Roll fuchsia [sysmem] sysmem2 support for logically weak VMOs This allows for scenarios where the only owner(s) of a buffer can/will only convey the buffer as a VMO handle, not by using a BufferCollection or BufferCollectionToken. For these scenarios, we can instead correlate a VMO back to a previously established BufferCollection. This is somewhat less direct than conveying a BufferCollectionToken, but adds client scenario flexibility. A participant can be involved in allocation, keeping only a weak BufferCollection channel and weak sysmem VMOs, cleaning up asap if strong VMOs all close (per buffer_index). If the participant sees a VMO show up via other protocol(s), the participant can correlate the VMO back to the weak BufferCollection via GetVmoInfo(). BUG: b/284073556 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/918633 Original-Revision: 764e7591b6c18f4265ea185c7cebbecaa7a35913 GitOrigin-RevId: 608264b2c0997501360675eb2c4d18aae77adbf6 Change-Id: Ib4096323a4c5dcba21ecd320a9c1904a731a4fd9
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.