[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Determine uses-full-ppgtt from context for execbuf

2018-09-01 Thread Patchwork
== Series Details == Series: drm/i915: Determine uses-full-ppgtt from context for execbuf URL : https://patchwork.freedesktop.org/series/49041/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4751_full -> Patchwork_10064_full = == Summary - SUCCESS == No regressions

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Determine uses-full-ppgtt from context for execbuf

2018-09-01 Thread Patchwork
== Series Details == Series: drm/i915: Determine uses-full-ppgtt from context for execbuf URL : https://patchwork.freedesktop.org/series/49041/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4751 -> Patchwork_10064 = == Summary - SUCCESS == No regressions found.

Re: [Intel-gfx] [PATCH] drm/i915: Explicitly mark Global GTT address spaces

2018-09-01 Thread Chris Wilson
Quoting Chris Wilson (2018-08-31 16:47:24) > Quoting Tvrtko Ursulin (2018-08-31 15:36:43) > > From: Tvrtko Ursulin > > > > So far we have been relying on vm->file pointer being NULL to declare > > something GGTT. > > > > This has the unfortunate consequence that the default kernel context is >

[Intel-gfx] [PATCH] drm/i915: Determine uses-full-ppgtt from context for execbuf

2018-09-01 Thread Chris Wilson
Rather than inspect the global module parameter for whether full-ppgtt maybe enabled, we can inspect the context directly as to whether it has its own vm. Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin Cc: Bob Paauwe Cc: Rodrigo Vivi --- drivers/gpu/drm/i915/i915_gem_execbuffer.c | 9

Re: [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dp_mst: Fix enabling pipe clock for all streams

2018-09-01 Thread Imre Deak
On Sat, Sep 01, 2018 at 04:38:23AM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/dp_mst: Fix enabling pipe clock for all streams > URL : https://patchwork.freedesktop.org/series/49025/ > State : success Pushed to -dinq, thanks for the report, review and testing. > > ==