KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
GPU-AV: Find ways to prevent bad commands / pipelines from executing
Open
GPU-AV
- Dominant language
- C++
- Stars
- 1k
- Forks
- 504
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 224
Description
For pipelines, we can try to add a `if (gpu_av_kill_pipeline_execution) { return; }` to every entry point using instrumentation.
For commands, no good answer, it will probably be case by case solutions.
Contributor guide
Research direction
The issue names GPU-AV pipelines, commands, instrumentation, and the gpu_av_kill_pipeline_execution flag, but no files or tests. Start by locating the instrumentation entry points and existing kill-flag handling. Define the expected behavior for pipeline and command execution, then add coverage showing that bad work does not execute.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100