**This is an old revision of the document!** ----

===== Future gem5-gpu Software Architecture Vision ===== Here is a diagram of the future gem5-gpu software architecture. {{ :future_gem5-gpu_architecture_1_31_2013_-cropped.png?300 |}} * In order to more clearly define and connect GPU hardware with specific gem5-gpu programming constructs, we plan to move much of the functionality currently held in the CudaGPU out to a CudaContext class. This class will aggregate the system state associated with running a GPU kernel and will be used for the following functions: * Managing GPU memory space page table * Interfacing with a copy engine which will copy data into and out of the GPU context’s memory space * Storing and managing PTX code and variables for the context * Managing the process of interfacing with CPU thread context through blocking * Introduction of the CudaContext will require updating the CUDA syscall interface in gem5-gpu (little/no change is expected for libcuda).