igt-gpu-tools.git - DRM IGT GPU Tools

Age	Commit message (Collapse)	Author
2018-02-23	Iterate over physical engines	Chris Wilson
	We current have a single for_each_engine() iterator which we use to generate both a set of uABI engines and a set of physical engines. Determining what uABI ring-id corresponds to an actual HW engine is tricky, so pull that out to a library function and introduce for_each_physical_engine() for cases where we want to issue requests once on each HW ring (avoiding aliasing issues). v2: Remember can_store_dword for gem_sync v3: Find more open-coded for_each_physical Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
2017-05-18	lib: Refactor testing for ability to use MI_STORE_DATA_IMM	Chris Wilson
	Rather than have the code in multiple locations, put a copy in lib/ Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2017-02-22	igt: Start marking up GEM tests that require an alive GPU to function	Chris Wilson
	Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2017-01-27	igt: Bump ioctl numbers for gem_exec_async and gem_exec_fence	Chris Wilson
	A small amount of drift between proposal and final. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2017-01-02	igt: Mass conversion to to_user_pointer()	Chris Wilson
	Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2016-11-07	igt: Add test case for EXEC_OBJECT_ASYNC	Chris Wilson
	The intention behind EXEC_OBJECT_ASYNC is to instruct the kernel to ignore implicit fences on the object but still maintain them for the GEM API. The user is expected to provide explicit fencing to maintain correct ordering of rendering. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>