benchmarks []

====== Differences ====== This shows you the differences between two versions of the page.

--- benchmarks [2013/02/15 14:21]
morr created
+++ benchmarks [2015/03/23 10:38] (current)
powerjg [Compiling Benchmarks]
@@ Line 14: / Line 14: @@
 </code>
-This will create a repository, with sub-repositories, including:
+This will create a repository, with [[http://mercurial.selenic.com/wiki/Subrepository|sub-repositories]], including:
-  * common
+  * common: includes a makefile for compiling CUDA code to run inside gem5-gpu
-  * dcmbmk
+  * dcmbmk: Demystifying GPU Microarchitecture benchmarks
-  * libcuda
+  * libcuda: A version of libcuda that benchmarks are linked with when being compiled to run in gem5-gpu
-  * parboil
+  * parboil: Parboil benchmarks
-  * rodinia
+  * rodinia: Rodinia benchmarks
-  * benchmarks
+  * rodinia-nocopy: Rodinia benchmarks with memcpy api calls elided
-  * unittests
+  * unittests: A set of simple tests for validating gem5-gpu
+==== Compiling Benchmarks ====
+gem5-gpu works with cuda 3.1 and 3.2 (the recommended gcc version is 4.4). Please install this on your system before proceeding further. You will also need to install the CUDA SDK, which includes the cutil library that is linked by many of the benchmarks.
+If you would like to use gem5-gpu ARM32 CPU ISA support, you will also need to obtain a cross-compiler for ARM. We have tested using arm-linux-gnueabihf-*-4.6 and arm-linux-gnueabihf-*-4.8 (gcc, g++, ld, ar), which can be obtained on Debian-based systems using:
+<code>
+[gem5-gpu/benchmarks] apt-get install gcc-4.8-arm-linux-gnueabihf-base cpp-4.8-arm-linux-gnueabihf g++-4.8-arm-linux-gnueabihf binutils-arm-linux-gnueabihf
+</code>
+Ensure that these tools can be found through your PATH variable (e.g. /usr/bin).
+=== Environment Variables ===
+Define the CUDAHOME environment variable and the path to the NVidia CUDA SDK, so that the makefiles know where they can find your installation of CUDA. Make sure that the CUDA executables (nvcc) are in your path. For example:
+<code>
+export CUDAHOME=<path to your cuda install>/cuda
+export PATH=$PATH:<path to your cuda install>/bin/
+export NVIDIA_CUDA_SDK_LOCATION=<path to your sdk installation>/C
+</code>
+=== Compile libcuda ===
+To build libcuda for x86:
+<code>
+[gem5-gpu/benchmarks] cd libcuda
+[gem5-gpu/benchmarks/libcuda] make
+</code>
+To build libcuda for ARM32 (note: Only one ISA can be compiled at a time):
+<code>
+[gem5-gpu/benchmarks] cd libcuda
+[gem5-gpu/benchmarks/libcuda] make ARCH=ARM32
+</code>
+=== Example of Compiling a Benchmark ===
+To build benchmarks for x86 ISA (requires that you have the x86 libcuda built as described above):
+<code>
+[gem5-gpu/benchmarks] cd rodinia/backprop
+[gem5-gpu/benchmarks/rodinia/backprop] make gem5-fusion
+</code>
+To build benchmarks for ARM ISA (requires that you have the ARM libcuda built as described above):
+<code>
+[gem5-gpu/benchmarks] cd rodinia/backprop
+[gem5-gpu/benchmarks/rodinia/backprop] make gem5-fusion ARCH=ARM32
+</code>
+* Note: The "gem5-fusion" nomenclature is legacy and we intend to update it to "gem5-gpu".
+== Example of Running a Benchmark ==
+Once you've [[start|built]] gem5-gpu, you can confirm that your benchmark runs. For example:
+<code>
+build/VI_hammer/gem5.opt ../gem5-gpu/configs/se_fusion.py -c ../benchmarks/rodinia/backprop/gem5_fusion_backprop -o "16"
+</code>

User Tools

Site Tools

Page Tools