gem5 - gem5

Age	Commit message (Collapse)	Author
2017-07-12	gpu-compute: Refactor some Event subclasses to lambdas	Sean Wilson
	Change-Id: Ic1332b8e8ba0afacbe591c80f4d06afbf5f04bd9 Signed-off-by: Sean Wilson <spwilson2@wisc.edu> Reviewed-on: https://gem5-review.googlesource.com/3922 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Reviewed-by: Anthony Gutierrez <anthony.gutierrez@amd.com> Maintainer: Anthony Gutierrez <anthony.gutierrez@amd.com>
2016-09-16	gpu-compute: fix typo in GPUDispatcher	Tony Gutierrez

2016-09-16	gpu-compute: Adding ioctl for HW context size	Alexandru Dutu
	Adding runtime support for determining the memory required by a SIMD engine when executing a particular wavefront.
2016-09-16	gpu-compute: Wavefront refactoring	Alexandru Dutu
	Renaming members of the Wavefront class in accordance with the style guide.
2016-06-09	gpu-compute: parametrize Wavefront size	jkalamat
	Eliminate the VSZ constant that defined the Wavefront size (in numbers of work items); replaced it with a parameter in the GPU.py configuration script. Changed all data structures dependent on the Wavefront size to be dynamically sized. Legal values of Wavefront size are 16, 32, 64 for now and checked at initialization time.
2016-04-07	mem: Remove threadId from memory request class	Mitch Hayenga
	In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit.
2016-01-19	gpu-compute: AMD's baseline GPU model	Tony Gutierrez