kokkos-tools
kokkos-tools copied to clipboard
Kokkos C++ Performance Portability Programming Ecosystem: Profiling and Debugging Tools
https://github.com/kokkos/kokkos-tools/pull/242
I have a kokkos tool that checks the stream and looks to see if a fence call is using the default stream. If I call the Kokkos function below to...
This is good enough for now. As a follow up I want us to consider using an environment variable (and command-line argument) to select the output format instead of the...
The tools currently initialise the event set by using ``` Kokkos::Tools::Experimental::EventSet my_event_set; memset(&my_event_set, 0, sizeof(my_event_set)); // zero any pointers not set here ``` As @dalg24 had pointed out in -...
Currently, a Kokkos Tool relies on an automatic global fencing to ensure that the Tool captures the appropriate state of its recording of state/diagnostic of kernel (e.g., a tool records...
Create Continuous Testing and Integration that ensures any new connector works by itself and can be integrated into the Kokkos Tools
Complementing the example directory, a set of unit tests and a framework for testing needs to be created for all Kokkos Tools libraries. This includes in-house tooling libraries, e.g., kernel-logger,...
# Background There exists three primary Kokkos Tools core vendor Kokkos Tools connectors which provide a hook to vendor tools (NVIDIA's nvtx connector, Intel's vtune connector, and AMD rocm connector)....
Need to put in Appropriate Fence Tool callbacks in NVprof focused connector (soon to be renamed NVTX_Focused_connector from #175). The tool-induced fences should be filtered out (at runtime) when the...
This issue brings forth the need for structured text documentation of Kokkos Tools, and lays out plans to do so.