Memory analysis tool for finding nontrivial gather / scatter (g/s) accesses from DynamoRio & NVBit traces. gs_patterns writes the subtraces to binary traces and a spatter yaml formatted file. The source lines of the top aggressors are reported. Use the provided pin clients in the pin_tracing folder or use DynamoRio. Pin tends to be more reliable for larger applications.
For CUDA kernels use the provided nvbit client in the nvbit_tracing folder.
See the README in the respective folders for more detailed information on these tools.
mkdir build
cd build
cmake ..
make
gs_pattern <pin_trace.gz> <binary>
gs_pattern <nvbit_trace.gz> -nv
Trace file should be gzipped (not tar + gz). For Pin or DynamoRio, binary file should be compiled with symbols turned on (-g).
For NVBit tracing the kernel must be compiled with line numbers (--generate-line-info). Please see nvbit_tracing/README.md for detailed information on how to extract traces for CUDA kernels which are compatible with gs_patterns.
g/s accesses are found by looking at repeated instruction addresses (loops) that are memory instructions (scalar and vector). The first pass finds the top g/s's and filters out instructions with trivial access patterns. The second pass focuses on the top g/s accesses and records the normalized address array indices to a binary file and spatter yaml file.
BSD-3 License. See the LICENSE file.
Kevin Sheridan, [email protected] Christopher Scott, [email protected]