commit | 34ec41a6b60abdf42bdd298fdefe15f66dfc2c32 | [log] [tgz] |
---|---|---|
author | Gurchetan Singh <gurchetansingh@chromium.org> | Thu Mar 17 14:55:52 2022 -0700 |
committer | Gurchetan Singh <gurchetansingh@google.com> | Thu Mar 17 17:40:53 2022 -0700 |
tree | 983058a4fc92290722dcc7501a4675b444208133 | |
parent | da84145011df1f2eb3bedee0fb8d52f1a0c13c7c [diff] |
vulkan-cereal: plumb virtgpu ctx_id to process pipe The virtio-gpu context ID is an unique identifier allocated by the guest kernel, via idr_alloc(..). These IDs can be reused, but virtio-gpu gurantees that re-use will only happens after a particular context has been destroyed. Many operations related to resource sharing between guest processes, and between gfxstream and virtgpu are done in reference to this context id. gfxstream has a clear analogue to this already --> m_puid, which is set via connecting to the "pipe:GLProcessPipe" service in the guest. The immediate goal is is make m_puid == ctx_id, so the guest kernel can reference each host render thread via the ctx_id. BUG=202552093 TEST=run Cuttlefish Change-Id: Iadc0c288be6a869261658db87c5c569389f73f5b
Graphics Streaming Kit is a code generator that makes it easier to serialize and forward graphics API calls from one place to another:
Make sure the latest CMake is installed. Make sure the opengl lib is installed. Otherwise, sudo apt-get install libglu1-mesa-dev freeglut3-dev mesa-common-dev Make sure you are using Clang as your CC
and clang++ as yourCXX
. Then
mkdir build cd build cmake . ../ make -j24
Unit tests:
make test
Make sure the latest CMake is installed. Make sure Visual Studio 2019 is installed on your system along with all the Clang C++ toolchain components. Then
mkdir build cd build cmake . ../ -A x64 -T ClangCL
A solution file should be generated. Then open the solution file in Visual studio and build the gfxstream_backend
target.
Be in the Android build system. Then
m libgfxstream_backend
It then ends up in out/host
This also builds for Android on-device.
libgfxstream_backend.(dll|so|dylib)
scripts/generate-vulkan-sources.sh
If you're in an AOSP checkout, this will also modify contents of the guest Vulkan encoder in ../goldfish-opengl
.
First, build build/gfxstream-generic-apigen
. Then run
scripts/generate-apigen-source.sh
There are a bunch of test executables generated. They require libEGL.so
and libGLESv2.so
and libvulkan.so
to be available, possibly from your GPU vendor or ANGLE, in the $LD_LIBRARY_PATH
.
There are a bunch of test executables generated. They require libEGL.dll
and libGLESv2.dll
and vulkan-1.dll
to be available, possibly from your GPU vendor or ANGLE, in the %PATH%
.
These are currently not built due to the dependency on system libEGL/libvulkan to run correctly.
CMakeLists.txt
: specifies all host-side build targets. This includes all backends along with client/server setups that live only on the host. SomeAndroid.bp
: specifies all guest-side build targets for Android:BUILD.gn
: specifies all guest-side build targets for Fuchsiabase/
: common libraries that are built for both the guest and host. Contains utility code related to synchronization, threading, and suballocation.protocols/
: implementations of protocols for various graphics APIs. May contain code generators to make it easy to regen the protocol based on certain things.host-common/
: implementations of host-side support code that makes it easier to run the server in a variety of virtual device environments. Contains concrete implementations of auxiliary virtual devices such as Address Space Device and Goldfish Pipe.stream-servers/
: implementations of various backends for various graphics APIs that consume protocol. gfxstream-virtio-gpu-renderer.cpp
contains a virtio-gpu backend implementation.