756a9d7e49
This CL is part of a chain of CLs that imports dma-bufs as VkImages to support WebGPU on Chrome OS. There are currently two steps for importing external memory into Vulkan: 1. DeviceVk::ImportExternalImage: calls into MemoryServiceOpaqueFD::ImportMemory which in turn calls into vkAllocateMemory and outputs a VkDeviceMemory handle to the imported memory. 2. TextureVk::CreateFromExternal: creates the actual TextureVk object, creates the VkImage, and binds the VkDeviceMemory from ImportExternalImage to the VkImage. For dma-buf support, however, we need to re-order these two steps because importing dma-buf memory requires a handle to the VkImage that will alias it [1]. This CL splits these two steps into three steps to ensure we create the VkImage first so we can use it in vkAllocateMemory: 1. TextureVk::CreateFromExternal: creates the TextureVk and VkImage (no longer concerns itself with vkBindImageMemory). 2. DeviceVk::ImportExternalImage: now takes the VkImage as input but is otherwise unchanged. 3. TextureVk::BindExternalMemory: calls vkBindImageMemory with handles to VkDeviceMemory and VkImage. [1] https://www.khronos.org/registry/vulkan/specs/1.1-extensions/man/html/VkMemoryDedicatedAllocateInfo.html BUG=chromium:996470 Change-Id: Id2d5951e9b573af79c44ce8c63be5210a279f946 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13780 Commit-Queue: Brian Ho <hob@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> |
||
---|---|---|
build_overrides | ||
docs | ||
examples | ||
generator | ||
infra/config | ||
scripts | ||
src | ||
third_party | ||
.clang-format | ||
.gitattributes | ||
.gitignore | ||
.gn | ||
AUTHORS | ||
BUILD.gn | ||
CONTRIBUTING.md | ||
DEPS | ||
LICENSE | ||
OWNERS | ||
PRESUBMIT.py | ||
README.chromium | ||
README.md | ||
codereview.settings | ||
dawn.json | ||
dawn_wire.json |
README.md
Dawn, a WebGPU implementation
Dawn (formerly NXT) is an open-source and cross-platform implementation of the work-in-progress WebGPU standard. It exposes a C/C++ API that maps almost one-to-one to the WebGPU IDL and can be managed as part of a larger system such as a Web browser.
Dawn provides several WebGPU building blocks:
- WebGPU C/C++ headers that applications and other building blocks use.
- The main C header for the WebGPU API.
- Definition of a structure of all function pointers for this specific Dawn version (called "proctable").
- A C++ wrapper for the C header.
- A "native" implementation of WebGPU using platforms' GPU APIs:
- D3D12 on Windows 10
- Metal on OSX (and eventually iOS)
- Vulkan on Windows, Linux (eventually ChromeOS, Android and Fuchsia too)
- OpenGL as best effort where available
- A client-server implementation of WebGPU for applications that are in a sandbox without access to native drivers
- A Dawn proc-table backend implementation of WebGPU for applications what want to be able to switch at runtime between native or client-server mode.
Directory structure
dawn.json
: description of the API used to drive code generators.examples
: examples showing how Dawn is used.generator
: code generator for files produces fromdawn.json
templates
: Jinja2 templates for the generator
scripts
: scripts to support things like continuous testing, build files, etc.src
:common
: helper code shared between core Dawn libraries and tests/samplesdawn_native
: native implementation of WebGPU, one subfolder per backenddawn_wire
: client-server implementation of WebGPUinclude
: public headers for Dawntests
: internal Dawn testsend2end
: WebGPU tests performing GPU operationsunittests
: unittests and by extension tests not using the GPUvalidation
: WebGPU validation tests not using the GPU (frontend tests)
utils
: helper code to use Dawn used by tests and samples
third_party
: directory where dependencies live as well as their buildfiles.
Building Dawn
Dawn uses the Chromium build system and dependency management so you need to install depot_tools and add it to the PATH.
On Linux you need to have the pkg-config
command:
# Install pkg-config on Ubuntu
sudo apt-get install pkg-config
Then get the source as follows:
# Clone the repo as "dawn"
git clone https://dawn.googlesource.com/dawn dawn && cd dawn
# Bootstrap the gclient configuration
cp scripts/standalone.gclient .gclient
# Fetch external dependencies and toolchains with gclient
gclient sync
Then generate build files using gn args out/Debug
or gn args out/Release
.
A text editor will appear asking build options, the most common option is is_debug=true/false
; otherwise gn args out/Release --list
shows all the possible options.
Then use ninja -C out/Release
to build dawn and for example ./out/Release/dawn_end2end_tests
to run the tests.
Contributing
Please read and follow CONTRIBUTING.md. Dawn doesn't have a formal coding style yet, except what's defined by our clang format style. Overall try to use the same style and convention as code around your change.
If you find issues with Dawn, please feel free to report them on the bug tracker. For other discussions, please post to Dawn's mailing list.
License
Please see LICENSE.
Disclaimer
This is not an officially supported Google product.