Re: [Intel-gfx] Can recent i915 support more than 8192x8192 screen?

2018-07-21 Thread Marcin Owsiany
pt., 20 lip 2018, 23:35 użytkownik Rodrigo Vivi 
napisał:

> On Fri, Jul 20, 2018 at 11:01:38PM +0200, Marcin Owsiany wrote:
> >2018-07-20 22:22 GMT+02:00 Rodrigo Vivi <[1]rodrigo.v...@intel.com>:
> >
> >On Thu, Jul 19, 2018 at 11:31:19PM +0200, Marcin Owsiany wrote:
>
> >PS: Sorry for the initial double-post, I thought my first email was
> >blackholed
>
> np... I approved it as soon as I saw it there.
> list is open, but I have to filter the non-subscribed emails because of
> so many spams...
>

I see, perhaps it might make sense to mention that the list is moderated to
https://01.org/community/participation-guidelines#list

Currently the policy makes it sound like messages from non-subscribers are
doomed for good.

Marcin
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] Can recent i915 support more than 8192x8192 screen?

2018-07-21 Thread Chris Wilson
Quoting Rodrigo Vivi (2018-07-20 21:22:25)
> On Thu, Jul 19, 2018 at 11:31:19PM +0200, Marcin Owsiany wrote:
> >Hello,
> >TL;DR: how can I set a 8960x2880 screen (not display) size on a T580? A
> >patch for i915 that I found on the internets does not seem to work.
> >Full story:
> >I'm a rather happy user of ThinkPad T580 which comes with a
> >high-density 3840x2160 LCD, and the following graphics hardware.
> >00:02.0 VGA compatible controller: Intel Corporation Device 5917 (rev
> >07) (prog-if 00 [VGA controller])
> >Subsystem: Lenovo Device 225a
> >Flags: bus master, fast devsel, latency 0, IRQ 142
> >Memory at e700 (64-bit, non-prefetchable) [size=16M]
> >Memory at c000 (64-bit, prefetchable) [size=256M]
> >I/O ports at e000 [size=64]
> >[virtual] Expansion ROM at 000c [disabled] [size=128K]
> >Capabilities: [40] Vendor Specific Information: Len=0c 
> >Capabilities: [70] Express Root Complex Integrated Endpoint,
> >MSI 00
> >Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
> >Capabilities: [d0] Power Management version 2
> >Capabilities: [100] Process Address Space ID (PASID)
> >Capabilities: [200] Address Translation Service (ATS)
> >Capabilities: [300] Page Request Interface (PRI)
> >Kernel driver in use: i915
> >Kernel modules: i915
> >Unfortunately attaching it to an external normal-density 2560x1440
> >display means I need to apply scaling. Combined with the side-by-side
> >arrangement of monitors, this means I'd need to set screen size
> >to 8960x2880. However this does not work:
> > $ xrandr --fb 8960x2880
> > xrandr: screen cannot be larger than 8192x8192 (desired size
> >8960x2880)
> >I found this [1]thread on reddit about the same problem, where a user
> >posted a simple patch claimed to be supplied by someone on #intel-gfx.
> >Unfortunately it does not work (or at least is not sufficient) - after
> >applying it xrandr does claim that 16384x16384 is possible, but
> >actually trying to use more than 8192x8192 fails with an error
> >(unfortunately I lost the exact message).
> 
> I'm afraid that it is a hardware limitation that you won't be able to
> workaround. But a log would be interesting anyway... (both dmesg and 
> xorg.0.log)

It is only a hardware limitation for a single pipe. We have supported
32kx32k screens for over 6 years in SNA.
-Chris
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [RESEND] drm/i915: Interactive RPS mode

2018-07-21 Thread Chris Wilson
Quoting Ville Syrjälä (2018-07-20 15:19:20)
> On Fri, Jul 20, 2018 at 03:03:09PM +0100, Chris Wilson wrote:
> > Quoting Ville Syrjälä (2018-07-20 14:50:25)
> > > On Fri, Jul 20, 2018 at 02:38:32PM +0100, Chris Wilson wrote:
> > > > Quoting Ville Syrjälä (2018-07-20 14:32:40)
> > > > > Another question is what happens where there are parallel flips
> > > > > happening? One could undo the boost from the other AFAICS. But maybe
> > > > > we don't care enough to protect against that?
> > > > 
> > > > It's a counter, so the "interactive" mode remains high until all
> > > > concurrent flips are completed.
> > > 
> > > Ah. I guess the bool in the atomic state threw me off. I suppose that
> > > one is just an optimization to avoid calling the function more than
> > > once?
> > 
> > Yes, it's that I caught the RPS counter going negative. We have more
> > cleanup_plane than we prepared I believe that's from
> > find_initial_plane.
> 
> Hmm. I don't quite see how that could happen. I believe
> prepare_fb/cleanup_fb should be fully paired up within a single commit.

The way I read intel_find_initial_plane_obj() is that it writes the
current configuration into the current intel_crtc->base.primary->state.
I think that is where the initial mismatch comes from. Also we seem to
be quite adapt at not holding rps_interactive high after modeset
completion, which suggests to me that something sneaky is happening with
the plane_state duplication.
-Chris
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] [PATCH] drm/i915: Fix gen-2 check for 128B tiling

2018-07-21 Thread Dhinakaran Pandiyan
intel_tile_width_bytes() returns 128B for gen-2 y-tiled buffers while at
the same time HAS_128_BYTE_Y_TILING() returns false for gen-2. I am
assuming intel_tile_width_bytes() does the right thing.

Cc: Chris Wilson 
Cc: Ville Syrjälä 
Signed-off-by: Dhinakaran Pandiyan 
---
 drivers/gpu/drm/i915/i915_drv.h | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 0f49f9988dfa..9b8a4f57a28c 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -2556,9 +2556,8 @@ intel_info(const struct drm_i915_private *dev_priv)
 /* With the 945 and later, Y tiling got adjusted so that it was 32 128-byte
  * rows, which changed the alignment requirements and fence programming.
  */
-#define HAS_128_BYTE_Y_TILING(dev_priv) (!IS_GEN2(dev_priv) && \
-!(IS_I915G(dev_priv) || \
-IS_I915GM(dev_priv)))
+#define HAS_128_BYTE_Y_TILING(dev_priv) (!(IS_I915G(dev_priv) || \
+  IS_I915GM(dev_priv)))
 #define SUPPORTS_TV(dev_priv)  ((dev_priv)->info.supports_tv)
 #define I915_HAS_HOTPLUG(dev_priv) ((dev_priv)->info.has_hotplug)
 
-- 
2.17.1

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [PATCH] drm/i915: Fix gen-2 check for 128B tiling

2018-07-21 Thread Chris Wilson
Quoting Dhinakaran Pandiyan (2018-07-21 10:06:07)
> intel_tile_width_bytes() returns 128B for gen-2 y-tiled buffers while at
> the same time HAS_128_BYTE_Y_TILING() returns false for gen-2. I am
> assuming intel_tile_width_bytes() does the right thing.
> 
> Cc: Chris Wilson 
> Cc: Ville Syrjälä 
> Signed-off-by: Dhinakaran Pandiyan 

It's rather that gen2 only has 128B tiling. Note that it only makes any
difference for intel_tile_width_bytes()..
-Chris
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] Can recent i915 support more than 8192x8192 screen?

2018-07-21 Thread Marcin Owsiany
sob., 21 lip 2018, 10:20 użytkownik Chris Wilson 
napisał:

> Quoting Rodrigo Vivi (2018-07-20 21:22:25)
> > On Thu, Jul 19, 2018 at 11:31:19PM +0200, Marcin Owsiany wrote:
> > >Hello,
> > >TL;DR: how can I set a 8960x2880 screen (not display) size on a
> T580? A
> > >patch for i915 that I found on the internets does not seem to work.
> > >Full story:
> > >I'm a rather happy user of ThinkPad T580 which comes with a
> > >high-density 3840x2160 LCD, and the following graphics hardware.
> > >00:02.0 VGA compatible controller: Intel Corporation Device 5917
> (rev
> > >07) (prog-if 00 [VGA controller])
> > >Subsystem: Lenovo Device 225a
> > >Flags: bus master, fast devsel, latency 0, IRQ 142
> > >Memory at e700 (64-bit, non-prefetchable) [size=16M]
> > >Memory at c000 (64-bit, prefetchable) [size=256M]
> > >I/O ports at e000 [size=64]
> > >[virtual] Expansion ROM at 000c [disabled] [size=128K]
> > >Capabilities: [40] Vendor Specific Information: Len=0c 
> > >Capabilities: [70] Express Root Complex Integrated Endpoint,
> > >MSI 00
> > >Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
> > >Capabilities: [d0] Power Management version 2
> > >Capabilities: [100] Process Address Space ID (PASID)
> > >Capabilities: [200] Address Translation Service (ATS)
> > >Capabilities: [300] Page Request Interface (PRI)
> > >Kernel driver in use: i915
> > >Kernel modules: i915
> > >Unfortunately attaching it to an external normal-density 2560x1440
> > >display means I need to apply scaling. Combined with the
> side-by-side
> > >arrangement of monitors, this means I'd need to set screen size
> > >to 8960x2880. However this does not work:
> > > $ xrandr --fb 8960x2880
> > > xrandr: screen cannot be larger than 8192x8192 (desired size
> > >8960x2880)
> > >I found this [1]thread on reddit about the same problem, where a
> user
> > >posted a simple patch claimed to be supplied by someone on
> #intel-gfx.
> > >Unfortunately it does not work (or at least is not sufficient) -
> after
> > >applying it xrandr does claim that 16384x16384 is possible, but
> > >actually trying to use more than 8192x8192 fails with an error
> > >(unfortunately I lost the exact message).
> >
> > I'm afraid that it is a hardware limitation that you won't be able to
> > workaround. But a log would be interesting anyway... (both dmesg and
> xorg.0.log)
>
> It is only a hardware limitation for a single pipe. We have supported
> 32kx32k screens for over 6 years in SNA.
>

Do you mean hardware, out Linux X? Does it mean it should be working
already on Linux 4.9.x (x~80)? Or does it depend on Ville's patch set?

Marcin
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] Can recent i915 support more than 8192x8192 screen?

2018-07-21 Thread Marcin Owsiany
sob., 21 lip 2018, 11:20 użytkownik Marcin Owsiany 
napisał:

>
> Do you mean hardware, out Linux X?
>

Do you mean hardware, *or Linux/X*?

Marcin

>
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fix gen-2 check for 128B tiling

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Fix gen-2 check for 128B tiling
URL   : https://patchwork.freedesktop.org/series/47003/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
4b57e640b38e drm/i915: Fix gen-2 check for 128B tiling
-:28: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'dev_priv' - possible 
side-effects?
#28: FILE: drivers/gpu/drm/i915/i915_drv.h:2559:
+#define HAS_128_BYTE_Y_TILING(dev_priv) (!(IS_I915G(dev_priv) || \
+  IS_I915GM(dev_priv)))

total: 0 errors, 0 warnings, 1 checks, 11 lines checked

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Fix gen-2 check for 128B tiling

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Fix gen-2 check for 128B tiling
URL   : https://patchwork.freedesktop.org/series/47003/
State : warning

== Summary ==

$ dim sparse origin/drm-tip
Commit: drm/i915: Fix gen-2 check for 128B tiling
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3645:16: warning: expression 
using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3644:16: warning: expression 
using sizeof(void)

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix gen-2 check for 128B tiling

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Fix gen-2 check for 128B tiling
URL   : https://patchwork.freedesktop.org/series/47003/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4522 -> Patchwork_9742 =

== Summary - SUCCESS ==

  No regressions found.

  External URL: 
https://patchwork.freedesktop.org/api/1.0/series/47003/revisions/1/mbox/

== Known issues ==

  Here are the changes found in Patchwork_9742 that come from known issues:

  === IGT changes ===

 Issues hit 

igt@drv_module_reload@basic-reload:
  fi-glk-j4005:   PASS -> DMESG-WARN (fdo#106725, fdo#106248)

igt@drv_selftest@live_workarounds:
  {fi-cfl-8109u}: PASS -> DMESG-FAIL (fdo#107292)


 Possible fixes 

igt@drv_selftest@live_hangcheck:
  fi-kbl-7560u:   DMESG-FAIL (fdo#106560, fdo#106947) -> PASS
  fi-skl-guc: DMESG-FAIL (fdo#107174) -> PASS

igt@drv_selftest@live_workarounds:
  fi-skl-6700k2:  DMESG-FAIL (fdo#107292) -> PASS

igt@kms_flip@basic-flip-vs-dpms:
  fi-kbl-r:   DMESG-WARN (fdo#105602) -> PASS

igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
  fi-skl-guc: FAIL (fdo#103191) -> PASS


  {name}: This element is suppressed. This means it is ignored when computing
  the status of the difference (SUCCESS, WARNING, or FAILURE).

  fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
  fdo#105602 https://bugs.freedesktop.org/show_bug.cgi?id=105602
  fdo#106248 https://bugs.freedesktop.org/show_bug.cgi?id=106248
  fdo#106560 https://bugs.freedesktop.org/show_bug.cgi?id=106560
  fdo#106725 https://bugs.freedesktop.org/show_bug.cgi?id=106725
  fdo#106947 https://bugs.freedesktop.org/show_bug.cgi?id=106947
  fdo#107174 https://bugs.freedesktop.org/show_bug.cgi?id=107174
  fdo#107292 https://bugs.freedesktop.org/show_bug.cgi?id=107292


== Participating hosts (47 -> 41) ==

  Missing(6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan 
fi-ctg-p8600 fi-kbl-8809g 


== Build changes ==

* Linux: CI_DRM_4522 -> Patchwork_9742

  CI_DRM_4522: 20532651221ed29af16e2db0a7ec8b9bd482c994 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4571: 65fccc149b85968cdce4737266b056059c1510f3 @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9742: 4b57e640b38ee3918057e37686cb6b94bd96c2d5 @ 
git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

4b57e640b38e drm/i915: Fix gen-2 check for 128B tiling

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9742/issues.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] [PATCH] drm/i915: Pull unpin map into vma release

2018-07-21 Thread Chris Wilson
A reasonably common operation is to pin the map of the vma alongside the
vma itself for the lifetime of the vma, and so release both pin at the
same time as destroying the vma. It is common enough to pull into the
release function, making that central function more attractive to a
couple of other callsites.

The continual ulterior motive is to sweep over errors on module load
aborting...

Testcase: igt/drv_module_reload/basic-reload-inject
Signed-off-by: Chris Wilson 
Cc: Michał Winiarski 
Cc: Michal Wajdeczko 
---
 drivers/gpu/drm/i915/i915_perf.c| 10 --
 drivers/gpu/drm/i915/i915_vma.c |  5 -
 drivers/gpu/drm/i915/i915_vma.h |  3 ++-
 drivers/gpu/drm/i915/intel_engine_cs.c  | 18 +++---
 drivers/gpu/drm/i915/intel_guc.c|  5 ++---
 drivers/gpu/drm/i915/intel_guc_ads.c|  2 +-
 drivers/gpu/drm/i915/intel_guc_ct.c |  7 ++-
 drivers/gpu/drm/i915/intel_guc_log.c|  2 +-
 drivers/gpu/drm/i915/intel_guc_submission.c | 10 --
 drivers/gpu/drm/i915/intel_lrc.c|  2 +-
 10 files changed, 24 insertions(+), 40 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
index 6bf10952c724..0376338d1f8d 100644
--- a/drivers/gpu/drm/i915/i915_perf.c
+++ b/drivers/gpu/drm/i915/i915_perf.c
@@ -1338,14 +1338,12 @@ free_oa_buffer(struct drm_i915_private *i915)
 {
mutex_lock(&i915->drm.struct_mutex);
 
-   i915_gem_object_unpin_map(i915->perf.oa.oa_buffer.vma->obj);
-   i915_vma_unpin(i915->perf.oa.oa_buffer.vma);
-   i915_gem_object_put(i915->perf.oa.oa_buffer.vma->obj);
-
-   i915->perf.oa.oa_buffer.vma = NULL;
-   i915->perf.oa.oa_buffer.vaddr = NULL;
+   i915_vma_unpin_and_release(&i915->perf.oa.oa_buffer.vma,
+  I915_VMA_RELEASE_MAP);
 
mutex_unlock(&i915->drm.struct_mutex);
+
+   i915->perf.oa.oa_buffer.vaddr = NULL;
 }
 
 static void i915_oa_stream_destroy(struct i915_perf_stream *stream)
diff --git a/drivers/gpu/drm/i915/i915_vma.c b/drivers/gpu/drm/i915/i915_vma.c
index 11d834f94220..274fd2a7bcb6 100644
--- a/drivers/gpu/drm/i915/i915_vma.c
+++ b/drivers/gpu/drm/i915/i915_vma.c
@@ -406,7 +406,7 @@ void i915_vma_unpin_iomap(struct i915_vma *vma)
i915_vma_unpin(vma);
 }
 
-void i915_vma_unpin_and_release(struct i915_vma **p_vma)
+void i915_vma_unpin_and_release(struct i915_vma **p_vma, unsigned int flags)
 {
struct i915_vma *vma;
struct drm_i915_gem_object *obj;
@@ -421,6 +421,9 @@ void i915_vma_unpin_and_release(struct i915_vma **p_vma)
i915_vma_unpin(vma);
i915_vma_close(vma);
 
+   if (flags & I915_VMA_RELEASE_MAP)
+   i915_gem_object_unpin_map(obj);
+
__i915_gem_object_release_unless_active(obj);
 }
 
diff --git a/drivers/gpu/drm/i915/i915_vma.h b/drivers/gpu/drm/i915/i915_vma.h
index f06d66377107..af5296b015f5 100644
--- a/drivers/gpu/drm/i915/i915_vma.h
+++ b/drivers/gpu/drm/i915/i915_vma.h
@@ -138,7 +138,8 @@ i915_vma_instance(struct drm_i915_gem_object *obj,
  struct i915_address_space *vm,
  const struct i915_ggtt_view *view);
 
-void i915_vma_unpin_and_release(struct i915_vma **p_vma);
+void i915_vma_unpin_and_release(struct i915_vma **p_vma, unsigned int flags);
+#define I915_VMA_RELEASE_MAP BIT(0)
 
 static inline bool i915_vma_is_active(struct i915_vma *vma)
 {
diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c 
b/drivers/gpu/drm/i915/intel_engine_cs.c
index 2d1952849d69..734a789688da 100644
--- a/drivers/gpu/drm/i915/intel_engine_cs.c
+++ b/drivers/gpu/drm/i915/intel_engine_cs.c
@@ -527,7 +527,7 @@ int intel_engine_create_scratch(struct intel_engine_cs 
*engine,
 
 void intel_engine_cleanup_scratch(struct intel_engine_cs *engine)
 {
-   i915_vma_unpin_and_release(&engine->scratch);
+   i915_vma_unpin_and_release(&engine->scratch, 0);
 }
 
 static void cleanup_phys_status_page(struct intel_engine_cs *engine)
@@ -543,20 +543,8 @@ static void cleanup_phys_status_page(struct 
intel_engine_cs *engine)
 
 static void cleanup_status_page(struct intel_engine_cs *engine)
 {
-   struct i915_vma *vma;
-   struct drm_i915_gem_object *obj;
-
-   vma = fetch_and_zero(&engine->status_page.vma);
-   if (!vma)
-   return;
-
-   obj = vma->obj;
-
-   i915_vma_unpin(vma);
-   i915_vma_close(vma);
-
-   i915_gem_object_unpin_map(obj);
-   __i915_gem_object_release_unless_active(obj);
+   i915_vma_unpin_and_release(&engine->status_page.vma,
+  I915_VMA_RELEASE_MAP);
 }
 
 static int init_status_page(struct intel_engine_cs *engine)
diff --git a/drivers/gpu/drm/i915/intel_guc.c b/drivers/gpu/drm/i915/intel_guc.c
index 560c7406ae40..846d693ecb53 100644
--- a/drivers/gpu/drm/i915/intel_guc.c
+++ b/drivers/gpu/drm/i915/intel_guc.c
@@ -170,7 +170,7 @@ static int guc_shared_data_create(struct intel_guc *guc)
 
v

[Intel-gfx] [PATCH i-g-t] igt/gem_exec_schedule: Trim deep runtime

2018-07-21 Thread Chris Wilson
Time the runtime for emitting deep dependency tree, while keeping it
full of umpteen thousand requests.

Signed-off-by: Chris Wilson 
---
 tests/gem_exec_schedule.c | 83 +--
 1 file changed, 70 insertions(+), 13 deletions(-)

diff --git a/tests/gem_exec_schedule.c b/tests/gem_exec_schedule.c
index 43ea97e61..0462ce84f 100644
--- a/tests/gem_exec_schedule.c
+++ b/tests/gem_exec_schedule.c
@@ -748,21 +748,29 @@ static void preemptive_hang(int fd, unsigned ring)
 static void deep(int fd, unsigned ring)
 {
 #define XS 8
-   const unsigned int nreq = MAX_PRIO - MIN_PRIO;
-   const unsigned size = ALIGN(4*nreq, 4096);
+   const unsigned int max_req = MAX_PRIO - MIN_PRIO;
+   const unsigned size = ALIGN(4*max_req, 4096);
struct timespec tv = {};
IGT_CORK_HANDLE(cork);
+   unsigned int nreq;
uint32_t plug;
uint32_t result, dep[XS];
uint32_t expected = 0;
uint32_t *ptr;
uint32_t *ctx;
+   int dep_nreq;
+   int n;
 
ctx = malloc(sizeof(*ctx) * MAX_CONTEXTS);
-   for (int n = 0; n < MAX_CONTEXTS; n++) {
+   for (n = 0; n < MAX_CONTEXTS; n++) {
ctx[n] = gem_context_create(fd);
}
 
+   nreq = gem_measure_ring_inflight(fd, ring, 0) / (4 * XS) * MAX_CONTEXTS;
+   if (nreq > max_req)
+   nreq = max_req;
+   igt_info("Using %d requests (prio range %d)\n", nreq, max_req);
+
result = gem_create(fd, size);
for (int m = 0; m < XS; m ++)
dep[m] = gem_create(fd, size);
@@ -774,7 +782,7 @@ static void deep(int fd, unsigned ring)
const uint32_t bbe = MI_BATCH_BUFFER_END;
 
memset(obj, 0, sizeof(obj));
-   for (int n = 0; n < XS; n++)
+   for (n = 0; n < XS; n++)
obj[n].handle = dep[n];
obj[XS].handle = result;
obj[XS+1].handle = gem_create(fd, 4096);
@@ -784,7 +792,7 @@ static void deep(int fd, unsigned ring)
execbuf.buffers_ptr = to_user_pointer(obj);
execbuf.buffer_count = XS + 2;
execbuf.flags = ring;
-   for (int n = 0; n < MAX_CONTEXTS; n++) {
+   for (n = 0; n < MAX_CONTEXTS; n++) {
execbuf.rsvd1 = ctx[n];
gem_execbuf(fd, &execbuf);
}
@@ -795,15 +803,62 @@ static void deep(int fd, unsigned ring)
plug = igt_cork_plug(&cork, fd);
 
/* Create a deep dependency chain, with a few branches */
-   for (int n = 0; n < nreq && igt_seconds_elapsed(&tv) < 8; n++) {
-   uint32_t context = ctx[n % MAX_CONTEXTS];
-   gem_context_set_priority(fd, context, MAX_PRIO - nreq + n);
+   for (n = 0; n < nreq && igt_seconds_elapsed(&tv) < 2; n++) {
+   const int gen = intel_gen(intel_get_drm_devid(fd));
+   struct drm_i915_gem_exec_object2 obj[3];
+   struct drm_i915_gem_relocation_entry reloc;
+   struct drm_i915_gem_execbuffer2 eb = {
+   .buffers_ptr = to_user_pointer(obj),
+   .buffer_count = 3,
+   .flags = ring | (gen < 6 ? I915_EXEC_SECURE : 0),
+   .rsvd1 = ctx[n % MAX_CONTEXTS],
+   };
+   uint32_t batch[16];
+   int i;
+
+   memset(obj, 0, sizeof(obj));
+   obj[0].handle = plug;
+
+   memset(&reloc, 0, sizeof(reloc));
+   reloc.presumed_offset = 0;
+   reloc.offset = sizeof(uint32_t);
+   reloc.delta = sizeof(uint32_t) * n;
+   reloc.read_domains = I915_GEM_DOMAIN_RENDER;
+   reloc.write_domain = I915_GEM_DOMAIN_RENDER;
+   obj[2].handle = gem_create(fd, 4096);
+   obj[2].relocs_ptr = to_user_pointer(&reloc);
+   obj[2].relocation_count = 1;
+
+   i = 0;
+   batch[i] = MI_STORE_DWORD_IMM | (gen < 6 ? 1 << 22 : 0);
+   if (gen >= 8) {
+   batch[++i] = reloc.delta;
+   batch[++i] = 0;
+   } else if (gen >= 4) {
+   batch[++i] = 0;
+   batch[++i] = reloc.delta;
+   reloc.offset += sizeof(uint32_t);
+   } else {
+   batch[i]--;
+   batch[++i] = reloc.delta;
+   }
+   batch[++i] = eb.rsvd1;
+   batch[++i] = MI_BATCH_BUFFER_END;
+   gem_write(fd, obj[2].handle, 0, batch, sizeof(batch));
 
-   for (int m = 0; m < XS; m++)
-   store_dword(fd, context, ring, dep[m], 4*n, context, 
plug, I915_GEM_DOMAIN_INSTRUCTION);
+   gem_context_set_priority(fd, eb.rsvd1, MAX_PRIO - nreq + n);
+   for (int m = 0; m < XS; m++) {
+   obj[1].handle = de

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Pull unpin map into vma release

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Pull unpin map into vma release
URL   : https://patchwork.freedesktop.org/series/47011/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4522 -> Patchwork_9743 =

== Summary - SUCCESS ==

  No regressions found.

  External URL: 
https://patchwork.freedesktop.org/api/1.0/series/47011/revisions/1/mbox/

== Known issues ==

  Here are the changes found in Patchwork_9743 that come from known issues:

  === IGT changes ===

 Issues hit 

igt@drv_module_reload@basic-reload:
  fi-glk-j4005:   PASS -> DMESG-WARN (fdo#106725, fdo#106248)

igt@drv_selftest@live_hangcheck:
  {fi-cfl-8109u}: PASS -> DMESG-FAIL (fdo#106560)
  fi-kbl-7567u:   PASS -> DMESG-FAIL (fdo#106560, fdo#106947)

igt@drv_selftest@live_workarounds:
  fi-kbl-7560u:   PASS -> DMESG-FAIL (fdo#107292)

igt@kms_chamelium@dp-edid-read:
  fi-kbl-7500u:   PASS -> FAIL (fdo#103841)

igt@kms_flip@basic-flip-vs-wf_vblank:
  fi-glk-j4005:   PASS -> FAIL (fdo#100368)


 Possible fixes 

igt@drv_selftest@live_hangcheck:
  fi-kbl-7560u:   DMESG-FAIL (fdo#106560, fdo#106947) -> PASS
  fi-skl-guc: DMESG-FAIL (fdo#107174) -> PASS

igt@drv_selftest@live_workarounds:
  fi-skl-6700k2:  DMESG-FAIL (fdo#107292) -> PASS

igt@kms_flip@basic-flip-vs-dpms:
  fi-kbl-r:   DMESG-WARN (fdo#105602) -> PASS

igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
  fi-skl-guc: FAIL (fdo#103191) -> PASS


  {name}: This element is suppressed. This means it is ignored when computing
  the status of the difference (SUCCESS, WARNING, or FAILURE).

  fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
  fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
  fdo#103841 https://bugs.freedesktop.org/show_bug.cgi?id=103841
  fdo#105602 https://bugs.freedesktop.org/show_bug.cgi?id=105602
  fdo#106248 https://bugs.freedesktop.org/show_bug.cgi?id=106248
  fdo#106560 https://bugs.freedesktop.org/show_bug.cgi?id=106560
  fdo#106725 https://bugs.freedesktop.org/show_bug.cgi?id=106725
  fdo#106947 https://bugs.freedesktop.org/show_bug.cgi?id=106947
  fdo#107174 https://bugs.freedesktop.org/show_bug.cgi?id=107174
  fdo#107292 https://bugs.freedesktop.org/show_bug.cgi?id=107292


== Participating hosts (47 -> 40) ==

  Missing(7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan 
fi-ctg-p8600 fi-kbl-8809g fi-byt-n2820 


== Build changes ==

* Linux: CI_DRM_4522 -> Patchwork_9743

  CI_DRM_4522: 20532651221ed29af16e2db0a7ec8b9bd482c994 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4571: 65fccc149b85968cdce4737266b056059c1510f3 @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9743: bf4a2d2459c9154e9a197f61fbc1d19584136ea3 @ 
git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

bf4a2d2459c9 drm/i915: Pull unpin map into vma release

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9743/issues.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Only force GGTT coherency w/a on required chipsets (rev2)

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Only force GGTT coherency w/a on required chipsets (rev2)
URL   : https://patchwork.freedesktop.org/series/46915/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4518_full -> Patchwork_9729_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9729_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9729_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9729_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-blt:
  shard-kbl:  SKIP -> PASS


== Known issues ==

  Here are the changes found in Patchwork_9729_full that come from known issues:

  === IGT changes ===

 Issues hit 

igt@drv_suspend@shrink:
  shard-glk:  PASS -> FAIL (fdo#106886)

igt@kms_cursor_legacy@pipe-c-torture-bo:
  shard-apl:  PASS -> DMESG-WARN (fdo#107122)

igt@kms_flip@2x-flip-vs-blocking-wf-vblank:
  shard-glk:  PASS -> FAIL (fdo#100368)


 Possible fixes 

igt@drv_suspend@shrink:
  shard-kbl:  FAIL (fdo#106886) -> PASS

igt@kms_flip@2x-plain-flip-fb-recreate:
  shard-glk:  FAIL (fdo#100368) -> PASS


  fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
  fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886
  fdo#107122 https://bugs.freedesktop.org/show_bug.cgi?id=107122


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4518 -> Patchwork_9729

  CI_DRM_4518: 85bdcb875339b30f7beecbc7cba6bc2041cdd28b @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4569: bf70728a951cd3c08dd9bbc9310e16aaa252164f @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9729: 82c30cd2b76189fb6736c3a0a27bf0293fd13545 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9729/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: GTT remapping for display (rev2)

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: GTT remapping for display (rev2)
URL   : https://patchwork.freedesktop.org/series/46886/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4518_full -> Patchwork_9730_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9730_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9730_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9730_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-blt:
  shard-kbl:  SKIP -> PASS +1

igt@gem_mocs_settings@mocs-rc6-vebox:
  shard-kbl:  PASS -> SKIP +2


== Known issues ==

  Here are the changes found in Patchwork_9730_full that come from known issues:

  === IGT changes ===

 Issues hit 

igt@kms_cursor_legacy@pipe-c-torture-bo:
  shard-apl:  PASS -> DMESG-WARN (fdo#107122)

igt@kms_universal_plane@cursor-fb-leak-pipe-b:
  shard-apl:  PASS -> FAIL (fdo#107241)


 Possible fixes 

igt@drv_suspend@shrink:
  shard-kbl:  FAIL (fdo#106886) -> PASS

igt@kms_flip@plain-flip-fb-recreate:
  shard-glk:  FAIL (fdo#100368) -> PASS


  fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
  fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886
  fdo#107122 https://bugs.freedesktop.org/show_bug.cgi?id=107122
  fdo#107241 https://bugs.freedesktop.org/show_bug.cgi?id=107241


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4518 -> Patchwork_9730

  CI_DRM_4518: 85bdcb875339b30f7beecbc7cba6bc2041cdd28b @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4569: bf70728a951cd3c08dd9bbc9310e16aaa252164f @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9730: f27708878ebf7ec004e94aa31c2989e4b76799dd @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9730/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Show stack (by WARN) for hitting forcewake errors

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Show stack (by WARN) for hitting forcewake errors
URL   : https://patchwork.freedesktop.org/series/46939/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4518_full -> Patchwork_9732_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9732_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9732_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9732_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-blt:
  shard-kbl:  SKIP -> PASS +1

igt@gem_mocs_settings@mocs-rc6-vebox:
  shard-kbl:  PASS -> SKIP +2

igt@kms_atomic@plane_primary_legacy:
  shard-snb:  PASS -> SKIP


== Known issues ==

  Here are the changes found in Patchwork_9732_full that come from known issues:

  === IGT changes ===

 Issues hit 

igt@kms_cursor_legacy@pipe-c-torture-bo:
  shard-apl:  PASS -> DMESG-WARN (fdo#107122)

igt@kms_flip@2x-flip-vs-blocking-wf-vblank:
  shard-glk:  PASS -> FAIL (fdo#100368)

igt@kms_flip@2x-flip-vs-expired-vblank:
  shard-glk:  PASS -> FAIL (fdo#105363)

igt@kms_flip@flip-vs-expired-vblank:
  shard-glk:  PASS -> FAIL (fdo#105189)

igt@prime_vgem@basic-fence-flip:
  shard-kbl:  PASS -> FAIL (fdo#104008)


 Possible fixes 

igt@drv_suspend@shrink:
  shard-kbl:  FAIL (fdo#106886) -> PASS

igt@kms_flip@plain-flip-fb-recreate:
  shard-glk:  FAIL (fdo#100368) -> PASS +1


  fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
  fdo#104008 https://bugs.freedesktop.org/show_bug.cgi?id=104008
  fdo#105189 https://bugs.freedesktop.org/show_bug.cgi?id=105189
  fdo#105363 https://bugs.freedesktop.org/show_bug.cgi?id=105363
  fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886
  fdo#107122 https://bugs.freedesktop.org/show_bug.cgi?id=107122


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4518 -> Patchwork_9732

  CI_DRM_4518: 85bdcb875339b30f7beecbc7cba6bc2041cdd28b @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4569: bf70728a951cd3c08dd9bbc9310e16aaa252164f @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9732: 2a9f353b3958cc8d481a9a8f13236184d789f1e7 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9732/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Clean up power well descriptors

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Clean up power well descriptors
URL   : https://patchwork.freedesktop.org/series/46952/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4518_full -> Patchwork_9734_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9734_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9734_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9734_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-blt:
  shard-kbl:  SKIP -> PASS +1

igt@kms_atomic_transition@plane-all-transition:
  shard-snb:  PASS -> SKIP +3


== Known issues ==

  Here are the changes found in Patchwork_9734_full that come from known issues:

  === IGT changes ===

 Issues hit 

igt@drv_suspend@shrink:
  shard-snb:  PASS -> FAIL (fdo#106886)

igt@kms_cursor_legacy@pipe-c-torture-bo:
  shard-apl:  PASS -> DMESG-WARN (fdo#107122)

igt@kms_flip@2x-plain-flip-ts-check:
  shard-glk:  PASS -> FAIL (fdo#100368)

igt@kms_flip@flip-vs-expired-vblank:
  shard-glk:  PASS -> FAIL (fdo#105189)


 Possible fixes 

igt@drv_suspend@shrink:
  shard-kbl:  FAIL (fdo#106886) -> PASS

igt@kms_flip@2x-plain-flip-fb-recreate:
  shard-glk:  FAIL (fdo#100368) -> PASS


  fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
  fdo#105189 https://bugs.freedesktop.org/show_bug.cgi?id=105189
  fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886
  fdo#107122 https://bugs.freedesktop.org/show_bug.cgi?id=107122


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4518 -> Patchwork_9734

  CI_DRM_4518: 85bdcb875339b30f7beecbc7cba6bc2041cdd28b @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4569: bf70728a951cd3c08dd9bbc9310e16aaa252164f @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9734: 0da627a1550ffb580b98834c960cdc91808d58c5 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9734/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Fix psr sink status report. (rev3)

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Fix psr sink status report. (rev3)
URL   : https://patchwork.freedesktop.org/series/46831/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4519_full -> Patchwork_9735_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9735_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9735_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9735_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-bsd1:
  shard-kbl:  SKIP -> PASS

igt@gem_exec_schedule@deep-render:
  shard-kbl:  PASS -> SKIP

igt@kms_cursor_crc@cursor-256x256-sliding:
  shard-snb:  SKIP -> PASS +2

igt@kms_frontbuffer_tracking@fbc-rgb565-draw-pwrite:
  shard-snb:  PASS -> SKIP +1


== Known issues ==

  Here are the changes found in Patchwork_9735_full that come from known issues:

  === IGT changes ===

 Issues hit 

igt@gem_ppgtt@blt-vs-render-ctx0:
  shard-kbl:  PASS -> INCOMPLETE (fdo#103665, fdo#106023)

igt@kms_flip@2x-flip-vs-blocking-wf-vblank:
  shard-glk:  PASS -> FAIL (fdo#100368)

igt@kms_setmode@basic:
  shard-snb:  PASS -> FAIL (fdo#99912)


 Possible fixes 

igt@kms_cursor_legacy@cursor-vs-flip-varying-size:
  shard-hsw:  FAIL (fdo#103355) -> PASS

igt@kms_flip@2x-plain-flip-ts-check:
  shard-glk:  FAIL (fdo#100368) -> PASS

igt@kms_setmode@basic:
  shard-apl:  FAIL (fdo#99912) -> PASS

igt@kms_universal_plane@cursor-fb-leak-pipe-c:
  shard-apl:  FAIL (fdo#107241) -> PASS


  fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
  fdo#103355 https://bugs.freedesktop.org/show_bug.cgi?id=103355
  fdo#103665 https://bugs.freedesktop.org/show_bug.cgi?id=103665
  fdo#106023 https://bugs.freedesktop.org/show_bug.cgi?id=106023
  fdo#107241 https://bugs.freedesktop.org/show_bug.cgi?id=107241
  fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4519 -> Patchwork_9735

  CI_DRM_4519: f14c0ec8fe9acce6fd1be84766f854ab8874eb33 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4569: bf70728a951cd3c08dd9bbc9310e16aaa252164f @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9735: 15623bcbe147a8278c1ee24a2109347988434426 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9735/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/dp: add extended receiver capability field present bit

2018-07-21 Thread Patchwork
== Series Details ==

Series: series starting with [1/2] drm/dp: add extended receiver capability 
field present bit
URL   : https://patchwork.freedesktop.org/series/46965/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4521_full -> Patchwork_9736_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9736_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9736_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9736_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-bsd2:
  shard-kbl:  SKIP -> PASS


== Known issues ==

  Here are the changes found in Patchwork_9736_full that come from known issues:

  === IGT changes ===

 Issues hit 

igt@gem_ppgtt@blt-vs-render-ctxn:
  shard-kbl:  PASS -> INCOMPLETE (fdo#103665, fdo#106023)

{igt@gem_userptr_blits@readonly-unsync}:
  shard-apl:  PASS -> INCOMPLETE (fdo#103927)

igt@kms_flip@2x-flip-vs-expired-vblank:
  shard-hsw:  PASS -> FAIL (fdo#102887)

igt@perf_pmu@multi-client-vcs1:
  shard-snb:  SKIP -> INCOMPLETE (fdo#105411)


 Possible fixes 

igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
  shard-hsw:  FAIL (fdo#105767) -> PASS

igt@kms_flip@dpms-vs-vblank-race:
  shard-glk:  FAIL (fdo#103060) -> PASS


  {name}: This element is suppressed. This means it is ignored when computing
  the status of the difference (SUCCESS, WARNING, or FAILURE).

  fdo#102887 https://bugs.freedesktop.org/show_bug.cgi?id=102887
  fdo#103060 https://bugs.freedesktop.org/show_bug.cgi?id=103060
  fdo#103665 https://bugs.freedesktop.org/show_bug.cgi?id=103665
  fdo#103927 https://bugs.freedesktop.org/show_bug.cgi?id=103927
  fdo#105411 https://bugs.freedesktop.org/show_bug.cgi?id=105411
  fdo#105767 https://bugs.freedesktop.org/show_bug.cgi?id=105767
  fdo#106023 https://bugs.freedesktop.org/show_bug.cgi?id=106023


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4521 -> Patchwork_9736

  CI_DRM_4521: a4ebbd84c682fd30edbde6ac0e48d150d4c5c066 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4570: 65cdccdc7bcbb791d791acb784a382110a3c @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9736: d20291854091a3f766dd98b37460faf57ef2b30e @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9736/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Show debugfs dpcd read failure directly

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Show debugfs dpcd read failure directly
URL   : https://patchwork.freedesktop.org/series/46977/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4521_full -> Patchwork_9737_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9737_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9737_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9737_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-blt:
  shard-kbl:  SKIP -> PASS

igt@gem_exec_schedule@deep-render:
  shard-kbl:  PASS -> SKIP

igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-pwrite:
  shard-snb:  PASS -> SKIP +1


== Known issues ==

  Here are the changes found in Patchwork_9737_full that come from known issues:

  === IGT changes ===

 Issues hit 

igt@gem_ppgtt@blt-vs-render-ctxn:
  shard-kbl:  PASS -> INCOMPLETE (fdo#103665, fdo#106023)

igt@kms_cursor_legacy@cursor-vs-flip-toggle:
  shard-hsw:  PASS -> FAIL (fdo#103355)

igt@kms_flip@2x-flip-vs-expired-vblank:
  shard-glk:  PASS -> FAIL (fdo#102887)

igt@kms_rotation_crc@primary-rotation-90:
  shard-apl:  PASS -> FAIL (fdo#103925)


 Possible fixes 

igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
  shard-hsw:  FAIL (fdo#105767) -> PASS

igt@kms_flip@dpms-vs-vblank-race:
  shard-glk:  FAIL (fdo#103060) -> PASS


  fdo#102887 https://bugs.freedesktop.org/show_bug.cgi?id=102887
  fdo#103060 https://bugs.freedesktop.org/show_bug.cgi?id=103060
  fdo#103355 https://bugs.freedesktop.org/show_bug.cgi?id=103355
  fdo#103665 https://bugs.freedesktop.org/show_bug.cgi?id=103665
  fdo#103925 https://bugs.freedesktop.org/show_bug.cgi?id=103925
  fdo#105767 https://bugs.freedesktop.org/show_bug.cgi?id=105767
  fdo#106023 https://bugs.freedesktop.org/show_bug.cgi?id=106023


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4521 -> Patchwork_9737

  CI_DRM_4521: a4ebbd84c682fd30edbde6ac0e48d150d4c5c066 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4570: 65cdccdc7bcbb791d791acb784a382110a3c @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9737: 84fb667b4f2eaba40302eaa18d7ca1297008d07c @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9737/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [CI,1/2] drm/i915/dp: Limit link training clock recovery loop

2018-07-21 Thread Patchwork
== Series Details ==

Series: series starting with [CI,1/2] drm/i915/dp: Limit link training clock 
recovery loop
URL   : https://patchwork.freedesktop.org/series/46992/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4521_full -> Patchwork_9740_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9740_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9740_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9740_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-bsd1:
  shard-kbl:  PASS -> SKIP +1

igt@gem_exec_schedule@deep-bsd2:
  shard-kbl:  SKIP -> PASS +1


== Known issues ==

  Here are the changes found in Patchwork_9740_full that come from known issues:

  === IGT changes ===

 Issues hit 

igt@drv_suspend@shrink:
  shard-apl:  PASS -> INCOMPLETE (fdo#103927, fdo#106886)

igt@kms_flip@2x-plain-flip-fb-recreate:
  shard-glk:  PASS -> FAIL (fdo#100368)

igt@kms_rotation_crc@primary-rotation-180:
  shard-apl:  PASS -> FAIL (fdo#103925)

igt@perf_pmu@multi-client-vcs1:
  shard-snb:  SKIP -> INCOMPLETE (fdo#105411)


 Possible fixes 

igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
  shard-hsw:  FAIL (fdo#105767) -> PASS

igt@kms_flip@dpms-vs-vblank-race:
  shard-glk:  FAIL (fdo#103060) -> PASS


  fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
  fdo#103060 https://bugs.freedesktop.org/show_bug.cgi?id=103060
  fdo#103925 https://bugs.freedesktop.org/show_bug.cgi?id=103925
  fdo#103927 https://bugs.freedesktop.org/show_bug.cgi?id=103927
  fdo#105411 https://bugs.freedesktop.org/show_bug.cgi?id=105411
  fdo#105767 https://bugs.freedesktop.org/show_bug.cgi?id=105767
  fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4521 -> Patchwork_9740

  CI_DRM_4521: a4ebbd84c682fd30edbde6ac0e48d150d4c5c066 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4570: 65cdccdc7bcbb791d791acb784a382110a3c @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9740: 5ef35ff56fb327ef9636123ad27755fffdd06f59 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9740/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dsc: Add missing _MMIO() from PPS registers (rev3)

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915/dsc: Add missing _MMIO() from PPS registers (rev3)
URL   : https://patchwork.freedesktop.org/series/46979/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4521_full -> Patchwork_9741_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9741_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9741_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9741_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-bsd2:
  shard-kbl:  SKIP -> PASS +1

igt@gem_exec_schedule@deep-vebox:
  shard-kbl:  PASS -> SKIP +1


== Known issues ==

  Here are the changes found in Patchwork_9741_full that come from known issues:

  === IGT changes ===

 Possible fixes 

igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
  shard-hsw:  FAIL (fdo#105767) -> PASS

igt@kms_flip@dpms-vs-vblank-race:
  shard-glk:  FAIL (fdo#103060) -> PASS


  fdo#103060 https://bugs.freedesktop.org/show_bug.cgi?id=103060
  fdo#105767 https://bugs.freedesktop.org/show_bug.cgi?id=105767


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4521 -> Patchwork_9741

  CI_DRM_4521: a4ebbd84c682fd30edbde6ac0e48d150d4c5c066 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4570: 65cdccdc7bcbb791d791acb784a382110a3c @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9741: 2d67170971143977f59b4852f29c888fcb3b0d18 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9741/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Fix gen-2 check for 128B tiling

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Fix gen-2 check for 128B tiling
URL   : https://patchwork.freedesktop.org/series/47003/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4522_full -> Patchwork_9742_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9742_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9742_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9742_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-bsd1:
  shard-kbl:  PASS -> SKIP +2

igt@gem_mocs_settings@mocs-rc6-vebox:
  shard-kbl:  SKIP -> PASS +2


== Known issues ==

  Here are the changes found in Patchwork_9742_full that come from known issues:

  === IGT changes ===

 Issues hit 

igt@kms_flip@2x-flip-vs-expired-vblank:
  shard-glk:  PASS -> FAIL (fdo#105363)

igt@kms_flip@plain-flip-ts-check:
  shard-glk:  PASS -> FAIL (fdo#100368) +1

igt@kms_setmode@basic:
  shard-hsw:  PASS -> FAIL (fdo#99912)


 Possible fixes 

igt@kms_busy@extended-modeset-hang-newfb-render-c:
  shard-hsw:  DMESG-WARN (fdo#102614) -> PASS


  fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
  fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614
  fdo#105363 https://bugs.freedesktop.org/show_bug.cgi?id=105363
  fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4522 -> Patchwork_9742

  CI_DRM_4522: 20532651221ed29af16e2db0a7ec8b9bd482c994 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4571: 65fccc149b85968cdce4737266b056059c1510f3 @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9742: 4b57e640b38ee3918057e37686cb6b94bd96c2d5 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9742/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Pull unpin map into vma release

2018-07-21 Thread Patchwork
== Series Details ==

Series: drm/i915: Pull unpin map into vma release
URL   : https://patchwork.freedesktop.org/series/47011/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4522_full -> Patchwork_9743_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9743_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9743_full, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

== Possible new issues ==

  Here are the unknown changes that may have been introduced in 
Patchwork_9743_full:

  === IGT changes ===

 Warnings 

igt@gem_exec_schedule@deep-bsd2:
  shard-kbl:  PASS -> SKIP +1

igt@gem_mocs_settings@mocs-rc6-vebox:
  shard-kbl:  SKIP -> PASS +2


== Known issues ==

  Here are the changes found in Patchwork_9743_full that come from known issues:

  === IGT changes ===

 Issues hit 

igt@kms_setmode@basic:
  shard-hsw:  PASS -> FAIL (fdo#99912)

igt@perf@blocking:
  shard-hsw:  PASS -> FAIL (fdo#102252)

igt@perf_pmu@rc6-runtime-pm-long:
  shard-kbl:  PASS -> FAIL (fdo#105010)


 Possible fixes 

igt@kms_busy@extended-modeset-hang-newfb-render-c:
  shard-hsw:  DMESG-WARN (fdo#102614) -> PASS

igt@kms_cursor_legacy@cursor-vs-flip-toggle:
  shard-hsw:  FAIL (fdo#103355) -> PASS


  fdo#102252 https://bugs.freedesktop.org/show_bug.cgi?id=102252
  fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614
  fdo#103355 https://bugs.freedesktop.org/show_bug.cgi?id=103355
  fdo#105010 https://bugs.freedesktop.org/show_bug.cgi?id=105010
  fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

* Linux: CI_DRM_4522 -> Patchwork_9743

  CI_DRM_4522: 20532651221ed29af16e2db0a7ec8b9bd482c994 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4571: 65fccc149b85968cdce4737266b056059c1510f3 @ 
git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9743: bf4a2d2459c9154e9a197f61fbc1d19584136ea3 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ 
git://anongit.freedesktop.org/piglit

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9743/shards.html
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [PATCH] drm/i915: Fix gen-2 check for 128B tiling

2018-07-21 Thread Dhinakaran Pandiyan
On Sat, 2018-07-21 at 10:11 +0100, Chris Wilson wrote:
> Quoting Dhinakaran Pandiyan (2018-07-21 10:06:07)
> > 
> > intel_tile_width_bytes() returns 128B for gen-2 y-tiled buffers
> > while at
> > the same time HAS_128_BYTE_Y_TILING() returns false for gen-2. I am
> > assuming intel_tile_width_bytes() does the right thing.
> > 
> > Cc: Chris Wilson 
> > Cc: Ville Syrjälä 
> > Signed-off-by: Dhinakaran Pandiyan 
> It's rather that gen2 only has 128B tiling. Note that it only makes
> any
> difference for intel_tile_width_bytes()..

Okay, the macro is a bit misleading. Do you have any suggestions to
clarify it or would you prefer I leave it as it is?


> -Chris
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[Intel-gfx] [drm-tip:drm-tip 7/8] debug.c:undefined reference to `save_stack_trace'

2018-07-21 Thread kbuild test robot
Hi Chris,

It's probably a bug fix that unveils the link errors.

tree:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
head:   c49f62682d40bd553d906245815a73976cfb604a
commit: b339ba2c91ecf03b38560c20e88d98dc7b6739f6 [7/8] Merge remote-tracking 
branch 'drm-intel/topic/core-for-CI' into drm-tip
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget 
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O 
~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout b339ba2c91ecf03b38560c20e88d98dc7b6739f6
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=m68k 

All errors (new ones prefixed by >>):

   kernel/dma/debug.o: In function `dma_entry_alloc':
>> debug.c:(.text+0x11d2): undefined reference to `save_stack_trace'
   mm/slub.o: In function `set_track':
>> slub.c:(.text+0x12b4): undefined reference to `save_stack_trace'
   lib/debugobjects.o: In function `save_stack.isra.0':
>> debugobjects.c:(.text+0x9f2): undefined reference to `save_stack_trace'

---
0-DAY kernel test infrastructureOpen Source Technology Center
https://lists.01.org/pipermail/kbuild-all   Intel Corporation


.config.gz
Description: application/gzip
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx