[dawn][vulkan] Removes queue serial assertion.

- The assertion is currently causing flakes after the changes
  in https://dawn-review.googlesource.com/c/dawn/+/242714. The
  change in that CL is necessary to implement spontaneous
  callbacks, but by moving the `CheckPassedSerial` call which is
  the call responsible for actually updating the `mCompletedSerial`
  member in `ExecutionQueue` outside of the scope of the global
  Device lock, the assertion can fail when:

  Thread A:
    - Successfully waited for serial 3 in the critical section of
      `WaitQueueSerials`.
    - Calls `CheckPassedSerial`->`CheckAndUpdateCompletedSerial`
      and gets 3. Note that in the Vulkan implementation of
      `CheckAndUpdateCompletedSerial`, this updates the internal
      fences that are tracked, so all serials < 3 are now no
      longer in `mFencesInFlight`. Begins to try calling
      `UpdateCompletedSerial(3)` but is interrupted by Thread B.
  Thread B:
    - `WaitForQueueSerial` is called for a serial of 2. Since
      the backend implementation, i.e. Vulkan's
      `CheckAndUpdateCompletedSerial` has already been called,
      in `QueueVk::CheckAndUpdateCompletedSerial` we don't
      find a wait fence, so we enter the code block with the
      DAWN_ASSERT. Unfortunately, since Thread A did not
      complete `UpdateCompletedSerial(3)` yet, the actual
      value of `mCompletedSerial == 1`. As a result, the
      assertion fails.
- This temporary change should fix the crashes we are seeing in
  the bugs, but a follow up more extensive change will be done
  to make sure that serials in `ExecutionQueue` are a bit more
  consistent in a multithreaded environment.

Bug: 419598089, 420681969
Change-Id: I8c3002379cec1ce0ab10e314cf3cd9d3a3512314
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/244035
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Auto-Submit: Loko Kung <lokokung@google.com>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
1 file changed
tree: 57070b33ab3b0abcd2c03e90ff5d8105d5b606ae
  1. .github/
  2. .vscode/
  3. build_overrides/
  4. docs/
  5. generator/
  6. include/
  7. infra/
  8. scripts/
  9. src/
  10. test/
  11. third_party/
  12. tools/
  13. webgpu-cts/
  14. .bazelrc
  15. .clang-format
  16. .clang-format-ignore
  17. .clang-tidy
  18. .git-blame-ignore-revs
  19. .gitattributes
  20. .gitignore
  21. .gitmodules
  22. .gn
  23. .style.yapf
  24. .vpython3
  25. AUTHORS
  26. BUILD.bazel
  27. BUILD.gn
  28. CMakeLists.txt
  29. CMakeSettings.json
  30. CODE_OF_CONDUCT.md
  31. codereview.settings
  32. CONTRIBUTING.md
  33. CPPLINT.cfg
  34. DEPS
  35. DIR_METADATA
  36. go.mod
  37. go.sum
  38. go_presubmit_support.py
  39. LICENSE
  40. OWNERS
  41. PRESUBMIT.py
  42. README.chromium
  43. README.md
  44. WATCHLISTS
  45. WORKSPACE.bazel
README.md

Build Status Matrix Space

Dawn, a WebGPU implementation

Dawn is an open-source and cross-platform implementation of the WebGPU standard. More precisely it implements webgpu.h that is a one-to-one mapping with the WebGPU IDL. Dawn is meant to be integrated as part of a larger system and is the underlying implementation of WebGPU in Chromium.

Dawn provides several WebGPU building blocks:

  • WebGPU C/C++ headers that applications and other building blocks use.
    • The webgpu.h version that Dawn implements.
    • A C++ wrapper for the webgpu.h.
  • A “native” implementation of WebGPU using platforms' GPU APIs: D3D12, Metal, Vulkan and OpenGL. See per API support for more details.
  • A client-server implementation of WebGPU for applications that are in a sandbox without access to native drivers
  • Tint is a compiler for the WebGPU Shader Language (WGSL) that can be used in standalone to convert shaders from and to WGSL.

Helpful links:

Documentation table of content

Developer documentation:

User documentation: (TODO, figure out what overlaps with the webgpu.h docs)

License

BSD 3-Clause License, please see LICENSE.

Disclaimer

This is not an officially supported Google product.