[Bug 88439] [BDW Bisected]igt/gem_reloc_vs_gpu/forked-faulting-reloc-thrash-inactive-hang doesn't exit testing
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Jan 15 23:50:57 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=88439
lu hua <huax.lu at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|bisect_pending |
Assignee|intel-gfx-bugs at lists.freede |chris at chris-wilson.co.uk
|sktop.org |
Summary|[BDW |[BDW
|Regression]igt/gem_reloc_vs |Bisected]igt/gem_reloc_vs_g
|_gpu/forked-faulting-reloc- |pu/forked-faulting-reloc-th
|thrash-inactive-hang |rash-inactive-hang doesn't
|doesn't exit testing |exit testing
--- Comment #3 from lu hua <huax.lu at intel.com> ---
c9dc0f35986c0e2fc81e0b71ddc7e3adad733829 is the first bad commit.
commit c9dc0f35986c0e2fc81e0b71ddc7e3adad733829
Author: Chris Wilson <chris at chris-wilson.co.uk>
AuthorDate: Wed Dec 24 08:13:40 2014 -0800
Commit: Daniel Vetter <daniel.vetter at ffwll.ch>
CommitDate: Wed Jan 7 18:19:06 2015 +0100
drm/i915: Add ioctl to set per-context parameters
Sometimes we wish to tweak how an individual context behaves. Since we
always create a context for every filp, this means that individual
processes can fine tune their behaviour even if they do not explicitly
create a context.
The first example parameter here is to enable multi-process GPU testing,
but the interface should be able to cope with passing arbitrarily complex
parameters.
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
Reviewed-by: Mika Kuoppala <mika.kuoppala at intel.com>
Testcase: igt/gem_reset_stats/ban-period-*
Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150116/b66dad9d/attachment.html>
More information about the intel-gfx-bugs
mailing list