[Migrated] Document best practices for debugging/profiling.

Issue automatically imported from old repo: https://github.com/EmbarkStudios/rust-gpu/issues/578
Old labels: a: documentation,t: enhancement
Originally creatd by dvc94ch on 2021-04-05T21:18:54Z 👍: 2

These are things that I keep getting hung up on. It is clear how gdb/perf work for example, by using the ptrace/open_perf_event syscalls in the linux kernel. However when it comes to gpu programming there seems to be few tools that aren't vendor specific and it is completely unclear how they work to a non-gpu expert. To open up gpu programming to a larger audience, how to perform debugging/profiling tasks should be documented better.

I presume there is some sort of synchronizing primitive in vulkan that could be used for debugging to step through the code, but how would you sample the gpu stack for example?

Es werden keine Dateien, Tests oder Einstiegspunkte genannt. Beginne damit, herstellerneutrale Workflows für GPU-Debugging und -Profiling zu recherchieren, einschließlich der in diesem Issue aufgeworfenen Fragen zur Vulkan-Synchronisierung und zum GPU-Stack-Sampling. Als erledigt gilt das Hinzufügen von Dokumentation, die praktische Ansätze für das Debugging und Profiling für Nicht-GPU-Experten erklärt.