[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/execlists: Use list_safe_reset_next() instead of opencoding

2016-12-03 Thread Patchwork
== Series Details == Series: drm/i915/execlists: Use list_safe_reset_next() instead of opencoding URL : https://patchwork.freedesktop.org/series/16316/ State : failure == Summary == Series 16316v1 drm/i915/execlists: Use list_safe_reset_next() instead of opencoding https://patchwork.freedeskt

[Intel-gfx] [PATCH] drm/i915/execlists: Use list_safe_reset_next() instead of opencoding

2016-12-03 Thread Chris Wilson
list.h provides a macro for updating the next element in a safe list-iter, so let's use it so that it is hopefully clearer to the reader about the unusual behaviour, and also easier to grep. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/intel_lrc.c | 2 +- 1 file changed, 1 insertion(+),

Re: [Intel-gfx] [PATCH 2/2] drm/i915: move vma sanity checking into i915_vma_bind

2016-12-03 Thread kbuild test robot
/drm-i915-introduce-GEM_WARN_ON/20161203-231346 base: git://anongit.freedesktop.org/drm-intel for-linux-next config: i386-allmodconfig (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree make ARCH=i386 All

Re: [Intel-gfx] [PATCH 2/2] drm/i915: move vma sanity checking into i915_vma_bind

2016-12-03 Thread kbuild test robot
-Auld/drm-i915-introduce-GEM_WARN_ON/20161203-231346 base: git://anongit.freedesktop.org/drm-intel for-linux-next config: x86_64-randconfig-s3-12040051 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree make

Re: [Intel-gfx] [PATCH] drm/i915: Always load guc by default.

2016-12-03 Thread Chris Wilson
On Fri, Dec 02, 2016 at 06:11:12PM +, Srivatsa, Anusha wrote: > > > >-Original Message- > >From: Chris Wilson [mailto:ch...@chris-wilson.co.uk] > >Sent: Thursday, November 24, 2016 12:41 AM > >To: Tvrtko Ursulin > >Cc: Srivatsa, Anusha ; intel- > >g...@lists.freedesktop.org; Mcgee, J

[Intel-gfx] [PATCH igt] igt: Add gem_exec_capture to exercise capturing user requested buffers on hang

2016-12-03 Thread Chris Wilson
Signed-off-by: Chris Wilson --- tests/Makefile.sources | 1 + tests/gem_exec_capture.c | 169 +++ 2 files changed, 170 insertions(+) create mode 100644 tests/gem_exec_capture.c diff --git a/tests/Makefile.sources b/tests/Makefile.sources index 04d

[Intel-gfx] [PATCH] drm/i915: Copy user requested buffers into the error state

2016-12-03 Thread Chris Wilson
Introduce a new execobject.flag (EXEC_OBJECT_CAPTURE) that userspace may use to indicate that it wants the contents of this buffer preserved in the error state (/sys/class/drm/cardN/error) following a GPU hang involving this batch. Use this at your discretion, the contents of the error state. alth

Re: [Intel-gfx] [PATCH 2/2] drm/i915/audio: extend audio sync rate support for DP MST

2016-12-03 Thread Yang, Libin
>-Original Message- >From: Jani Nikula [mailto:jani.nik...@linux.intel.com] >Sent: Friday, December 2, 2016 10:25 PM >To: Yang, Libin ; intel-gfx@lists.freedesktop.org; >ville.syrj...@linux.intel.com; Vetter, Daniel ; >Pandiyan, Dhinakaran ; ti...@suse.de; >liang.xi...@dell.com >Subject: R

Re: [Intel-gfx] [PATCH] drm/i915: Remove instructions to file a bug report.

2016-12-03 Thread Jani Nikula
On Sat, 03 Dec 2016, Matt Turner wrote: > From these instructions, users assume that /sys/class/drm/card0/error > contains all the information a developer needs to diagnose and fix a GPU > hang. > > In fact it doesn't, and we have no tools for solving them (other than > stabbing in the dark). Most

Re: [Intel-gfx] [RFC 1/3] fs: Introduce drmfs pseudo filesystem interfaces

2016-12-03 Thread Chris Wilson
On Sat, Dec 03, 2016 at 06:23:20AM +0530, sourab gupta wrote: > On Fri, 2016-12-02 at 14:40 -0800, Roper, Matthew D wrote: > > Am I correct in assuming the data made available via drmfs is not > > considered ABI? If we're not going to guarantee a stable ABI and > > backward compatibility forever f

Re: [Intel-gfx] [PATCH] drm/i915: Remove instructions to file a bug report.

2016-12-03 Thread Chris Wilson
On Fri, Dec 02, 2016 at 05:03:05PM -0800, Matt Turner wrote: > From these instructions, users assume that /sys/class/drm/card0/error > contains all the information a developer needs to diagnose and fix a GPU > hang. > > In fact it doesn't, and we have no tools for solving them (other than > stabbi