Re: [Intel-gfx] [PATCH 4/4] drm/i915/intel_dsi: Read back pclk set by GOP and use that as pclk

2018-07-06 Thread Hans de Goede
Hi, On 07/06/2018 04:16 PM, Ville Syrjälä wrote: On Tue, Jun 19, 2018 at 10:18:27PM +0200, Hans de Goede wrote: On BYT and CHT the GOP sometimes initializes the pclk at a (slightly) different frequency then the pclk which we've calculated. This commit makes the DSI code read-back the pclk set

Re: [Intel-gfx] [PATCH 0/4] drm/i915/intel_dsi: Read back and use pclk set by the GOP

2018-07-06 Thread Hans de Goede
Hi, On 07/06/2018 03:14 PM, Jani Nikula wrote: On Fri, 29 Jun 2018, Hans de Goede wrote: Hi, On 19-06-18 22:18, Hans de Goede wrote: Hi All, This patch-set is the result of the work I've been doing recently to give people a smooth "flickerfree" boot experience where the display keeps displa

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Flush the WCB following a WC write

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Flush the WCB following a WC write URL : https://patchwork.freedesktop.org/series/46070/ State : failure == Summary == = CI Bug Log - changes from CI_DRM__full -> Patchwork_9566_full = == Summary - FAILURE == Serious unknown changes coming with Pa

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftests: Skip live_execlists if the GPU is terminally wedged

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Skip live_execlists if the GPU is terminally wedged URL : https://patchwork.freedesktop.org/series/46069/ State : failure == Summary == = CI Bug Log - changes from CI_DRM__full -> Patchwork_9565_full = == Summary - FAILURE == Serious unk

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915: Record logical context support in driver caps (rev2)

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915: Record logical context support in driver caps (rev2) URL : https://patchwork.freedesktop.org/series/46065/ State : failure == Summary == = CI Bug Log - changes from CI_DRM__full -> Patchwork_9563_full = == Summary - FAILUR

Re: [Intel-gfx] [PATCH 2/2] drm/i915: use the ICL stolen memory

2018-07-06 Thread Lucas De Marchi
On Fri, May 4, 2018 at 1:33 PM Paulo Zanoni wrote: > > Now that our stolen memory is already reserved by the x86 subsystem > (since commit "x86/gpu: reserve ICL's graphics stolen memory"), make > use of it. > > Cc: Joonas Lahtinen > Cc: Daniele Ceraolo Spurio > Cc: x...@kernel.org > Signed-off-b

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Introduce BITS_PER_TYPE

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Introduce BITS_PER_TYPE URL : https://patchwork.freedesktop.org/series/46055/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4443_full -> Patchwork_9562_full = == Summary - WARNING == Minor unknown changes coming with Patchwork_9562_

[Intel-gfx] ✗ Fi.CI.BAT: failure for i915 HDMI connector status is connected after disconnection

2018-07-06 Thread Patchwork
== Series Details == Series: i915 HDMI connector status is connected after disconnection URL : https://patchwork.freedesktop.org/series/46108/ State : failure == Summary == Applying: i915 HDMI connector status is connected after disconnection error: patch fragment without header at line 7: @@

Re: [Intel-gfx] [BUG] i915 HDMI connector status is connected after disconnection

2018-07-06 Thread Guang Bai
On Fri, 6 Jul 2018 13:38:06 -0700 Rodrigo Vivi wrote: > On Fri, Jul 06, 2018 at 10:41:18AM -0700, Guang Bai wrote: > > On Fri, 6 Jul 2018 14:44:58 +0800 > > Chris Chiu wrote: > > > > > On Thu, Jul 5, 2018 at 10:40 PM, Ville Syrjälä > > > wrote: > > > > On Thu, Jul 05, 2018 at 03:58:36PM +0

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update URL : https://patchwork.freedesktop.org/series/46104/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4449 -> Patchwork_9580 = == Summary - SUCCESS == No regressions found.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update URL : https://patchwork.freedesktop.org/series/46104/ State : warning == Summary == $ dim checkpatch origin/drm-tip 27f7762e393d drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe upda

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Replace nested subclassing with explicit subclasses

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Replace nested subclassing with explicit subclasses URL : https://patchwork.freedesktop.org/series/46103/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4449 -> Patchwork_9579 = == Summary - SUCCESS == No regressions found. Extern

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Avoid warning if runtime pm is disabled

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Avoid warning if runtime pm is disabled URL : https://patchwork.freedesktop.org/series/46101/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4449 -> Patchwork_9578 = == Summary - SUCCESS == No regressions found. External

[Intel-gfx] ✓ Fi.CI.IGT: success for ICELAKE DSI DRIVER (rev4)

2018-07-06 Thread Patchwork
== Series Details == Series: ICELAKE DSI DRIVER (rev4) URL : https://patchwork.freedesktop.org/series/44823/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4441_full -> Patchwork_9561_full = == Summary - WARNING == Minor unknown changes coming with Patchwork_9561_full nee

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [01/27] drm/i915: Squelch very verbose error logging

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [01/27] drm/i915: Squelch very verbose error logging URL : https://patchwork.freedesktop.org/series/46051/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4441_full -> Patchwork_9560_full = == Summary - FAILURE == Serious

Re: [Intel-gfx] [PATCH] drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 02:13:18PM -0700, Tarun Vyas wrote: > In commit "drm/i915: Wait for PSR exit before checking for vblank > evasion", the idea was to limit the PSR IDLE checks when PSR is > actually supported. While CAN_PSR does do that check, it doesn't > applies on a per-crtc basis. crtc_st

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Avoid warning if runtime pm is disabled

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 09:59:47PM +0100, Chris Wilson wrote: > Inside the mock GEM device, we try to grab the runtime pm for the fake > device to prevent it from ever suspending. However, if CONFIG_PM is not > set, trying to obtain the wakref returns an error which we WARN about. > Suppress the ex

[Intel-gfx] [PATCH] drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update

2018-07-06 Thread Tarun Vyas
In commit "drm/i915: Wait for PSR exit before checking for vblank evasion", the idea was to limit the PSR IDLE checks when PSR is actually supported. While CAN_PSR does do that check, it doesn't applies on a per-crtc basis. crtc_state->has_psr is a more granular check that avoids everything but pip

[Intel-gfx] [CI] drm/i915: Replace nested subclassing with explicit subclasses

2018-07-06 Thread Chris Wilson
In the next patch, we will want a third distinct class of timeline that may overlap with the current pair of client and engine timeline classes. Rather than use the ad hoc markup of SINGLE_DEPTH_NESTING, initialise the different timeline classes with an explicit subclass. Signed-off-by: Chris Wils

[Intel-gfx] [PATCH] drm/i915/selftests: Avoid warning if runtime pm is disabled

2018-07-06 Thread Chris Wilson
Inside the mock GEM device, we try to grab the runtime pm for the fake device to prevent it from ever suspending. However, if CONFIG_PM is not set, trying to obtain the wakref returns an error which we WARN about. Suppress the expected warning. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i91

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Chris Wilson
Quoting Rodrigo Vivi (2018-07-06 21:55:37) > On Fri, Jul 06, 2018 at 09:39:14PM +0100, Chris Wilson wrote: > > Quoting Rodrigo Vivi (2018-07-06 21:27:52) > > > On Fri, Jul 06, 2018 at 06:15:37PM +0100, Chris Wilson wrote: > > > > Older machines do not have the 128-byte tile width format for > > > >

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 09:39:14PM +0100, Chris Wilson wrote: > Quoting Rodrigo Vivi (2018-07-06 21:27:52) > > On Fri, Jul 06, 2018 at 06:15:37PM +0100, Chris Wilson wrote: > > > Older machines do not have the 128-byte tile width format for > > > I915_TILING_Y and so we must adapt our reference swi

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Chris Wilson
Quoting Rodrigo Vivi (2018-07-06 21:27:52) > On Fri, Jul 06, 2018 at 06:15:37PM +0100, Chris Wilson wrote: > > Older machines do not have the 128-byte tile width format for > > I915_TILING_Y and so we must adapt our reference swizzle. > > > > Testcase: igt/drv_selftest/live_objects #gdg > > The c

Re: [Intel-gfx] [BUG] i915 HDMI connector status is connected after disconnection

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 10:41:18AM -0700, Guang Bai wrote: > On Fri, 6 Jul 2018 14:44:58 +0800 > Chris Chiu wrote: > > > On Thu, Jul 5, 2018 at 10:40 PM, Ville Syrjälä > > wrote: > > > On Thu, Jul 05, 2018 at 03:58:36PM +0800, Chris Chiu wrote: > > >> Hi, > > >> We have few ASUS laptops X7

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 09:27:47PM +0100, Chris Wilson wrote: > Quoting Rodrigo Vivi (2018-07-06 21:23:00) > > On Fri, Jul 06, 2018 at 06:49:26PM +0100, Chris Wilson wrote: > > > clflush is an unserialised instruction and the IA manual strongly advises > > > you to serialise it with a mb. To be cau

Re: [Intel-gfx] [PATCH] Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE()

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 03:04:24PM -0400, Peter Jones wrote: > This was sort of annoying me: > > random:~$ dmesg | tail -1 > [523884.039227] [drm] Reducing the compressed framebuffer size. This may lead > to less power savings than a non-reduced-size. Try to increase stolen memory > size if avai

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Chris Wilson
Quoting Rodrigo Vivi (2018-07-06 21:23:00) > On Fri, Jul 06, 2018 at 06:49:26PM +0100, Chris Wilson wrote: > > clflush is an unserialised instruction and the IA manual strongly advises > > you to serialise it with a mb. To be cautious, apply one before and one > > after, > > my understanding is th

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 06:15:37PM +0100, Chris Wilson wrote: > Older machines do not have the 128-byte tile width format for > I915_TILING_Y and so we must adapt our reference swizzle. > > Testcase: igt/drv_selftest/live_objects #gdg The change below itself makes sense to me, but I'm trying to u

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 06:49:26PM +0100, Chris Wilson wrote: > clflush is an unserialised instruction and the IA manual strongly advises > you to serialise it with a mb. To be cautious, apply one before and one > after, my understanding is that we need one before and one after anyways, not just a

[Intel-gfx] ✓ Fi.CI.BAT: success for Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE()

2018-07-06 Thread Patchwork
== Series Details == Series: Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE() URL : https://patchwork.freedesktop.org/series/46092/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4448 -> Patchwork_9577 = == Summary - SUCCESS == No regressions fou

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix assert_plane() warning on bootup with external display (rev8)

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Fix assert_plane() warning on bootup with external display (rev8) URL : https://patchwork.freedesktop.org/series/44909/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4448 -> Patchwork_9576 = == Summary - SUCCESS == No regressions f

[Intel-gfx] [PATCH] Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE()

2018-07-06 Thread Peter Jones
This was sort of annoying me: random:~$ dmesg | tail -1 [523884.039227] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. random:~$ dmesg | grep -c "Reducing the compressed" 47 Th

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix assert_plane() warning on bootup with external display (rev7)

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Fix assert_plane() warning on bootup with external display (rev7) URL : https://patchwork.freedesktop.org/series/44909/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4448 -> Patchwork_9575 = == Summary - SUCCESS == No regressions f

[Intel-gfx] [PATCH v8] drm/i915: Fix assert_plane() warning on bootup with external display

2018-07-06 Thread Azhar Shaikh
On KBL, WHL RVPs, booting up with an external display connected, triggers below warning, when the BiOS brings up the external display too. This warning is not seen during hotplug. [3.615226] [ cut here ] [3.619829] plane 1A assertion failure (expected on, current of

Re: [Intel-gfx] [PATCH v7] drm/i915: Fix assert_plane() warning on bootup with external display

2018-07-06 Thread Shaikh, Azhar
>-Original Message- >From: Shaikh, Azhar >Sent: Friday, July 6, 2018 11:28 AM >To: intel-gfx@lists.freedesktop.org >Cc: ville.syrj...@linux.intel.com; Navare, Manasi D >; Shaikh, Azhar >Subject: [PATCH v7] drm/i915: Fix assert_plane() warning on bootup with >external display > >On KBL, W

[Intel-gfx] [PATCH v7] drm/i915: Fix assert_plane() warning on bootup with external display

2018-07-06 Thread Azhar Shaikh
On KBL, WHL RVPs, booting up with an external display connected, triggers below warning, when the BiOS brings up the external display too. This warning is not seen during hotplug. [3.615226] [ cut here ] [3.619829] plane 1A assertion failure (expected on, current of

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Provide full mb() around clflush URL : https://patchwork.freedesktop.org/series/46085/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4448 -> Patchwork_9574 = == Summary - SUCCESS == No regressions found. External URL:

Re: [Intel-gfx] [PATCH v6] drm/i915: Fix assert_plane() warning on bootup with external display

2018-07-06 Thread Ville Syrjälä
On Tue, Jul 03, 2018 at 01:21:02PM -0700, Azhar Shaikh wrote: > On KBL, WHL RVPs, booting up with an external display connected, triggers > below warning, when the BiOS brings up the external display too. > This warning is not seen during hotplug. > > [3.615226] [ cut here ]---

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Provide full mb() around clflush URL : https://patchwork.freedesktop.org/series/46085/ State : warning == Summary == $ dim checkpatch origin/drm-tip cdfe0eb01ba9 drm/i915/selftests: Provide full mb() around clflush -:24: WARNING:MEMORY_BARRIER:

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Adjust y-tiling height for older machines URL : https://patchwork.freedesktop.org/series/46084/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4448 -> Patchwork_9573 = == Summary - SUCCESS == No regressions found. Extern

[Intel-gfx] [PATCH] drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Chris Wilson
clflush is an unserialised instruction and the IA manual strongly advises you to serialise it with a mb. To be cautious, apply one before and one after, so that it is serialised with both writes and reads without worrying too much about the required direction. Signed-off-by: Chris Wilson --- ...

Re: [Intel-gfx] [BUG] i915 HDMI connector status is connected after disconnection

2018-07-06 Thread Guang Bai
On Fri, 6 Jul 2018 14:44:58 +0800 Chris Chiu wrote: > On Thu, Jul 5, 2018 at 10:40 PM, Ville Syrjälä > wrote: > > On Thu, Jul 05, 2018 at 03:58:36PM +0800, Chris Chiu wrote: > >> Hi, > >> We have few ASUS laptops X705FD (The new WiskyLake), X560UD > >> (intel i5-8250U), X530UN (intel i7-85

[Intel-gfx] [PATCH] drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Chris Wilson
Older machines do not have the 128-byte tile width format for I915_TILING_Y and so we must adapt our reference swizzle. Testcase: igt/drv_selftest/live_objects #gdg Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/selftests/i915_gem_object.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion

Re: [Intel-gfx] [PATCH 2/8] drm/i915: Introduce intel_encoder_is_dig_port()

2018-07-06 Thread Rodrigo Vivi
On Thu, Jul 05, 2018 at 07:43:51PM +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Add intel_encoder_is_dig_port() to match intel_encoder_is_dp(). > > Signed-off-by: Ville Syrjälä Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/intel_drv.h | 24 +++- > 1 fil

Re: [Intel-gfx] [PATCH 3/8] drm/i915: Rewrite mst suspend/resume in terms of encoders

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 01:42:35PM +0300, Ville Syrjälä wrote: > On Thu, Jul 05, 2018 at 02:29:59PM -0700, Rodrigo Vivi wrote: > > On Thu, Jul 05, 2018 at 07:43:52PM +0300, Ville Syrjala wrote: > > > From: Ville Syrjälä > > > > > > Rather than looping over all the ports and picking the encoder ba

Re: [Intel-gfx] [PATCH] drm/i915: Flush the WCB following a WC write

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 12:54:02PM +0100, Chris Wilson wrote: > If we have just completed a WC write, we must ensure that the WCB (Write > Combining Buffer) is flushed out to main memory before we can expect to > see the results. This is especially important when mixing WC with GTT as > the physica

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gen11: Preempt-to-idle support in execlists. (rev5)

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/gen11: Preempt-to-idle support in execlists. (rev5) URL : https://patchwork.freedesktop.org/series/40747/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4446 -> Patchwork_9572 = == Summary - SUCCESS == No regressions found. Externa

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Skip over live context testing when wedged

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 07:42:00AM +0100, Chris Wilson wrote: > Quoting Rodrigo Vivi (2018-07-05 21:52:10) > > On Thu, Jul 05, 2018 at 03:58:45PM +0100, Chris Wilson wrote: > > > If the GPU is terminally wedged we cannot submit any requests into a > > > context, completely unfulfilling our purpose

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/gen11: Preempt-to-idle support in execlists. (rev5)

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/gen11: Preempt-to-idle support in execlists. (rev5) URL : https://patchwork.freedesktop.org/series/40747/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915/gen11: Preempt-to-idle support in execlists. -drivers/gpu/drm/i915/selftest

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gen11: Preempt-to-idle support in execlists. (rev5)

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/gen11: Preempt-to-idle support in execlists. (rev5) URL : https://patchwork.freedesktop.org/series/40747/ State : warning == Summary == $ dim checkpatch origin/drm-tip 90f487fed124 drm/i915/gen11: Preempt-to-idle support in execlists. -:141: CHECK:COMPARIS

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/selftests: Replace magic 1<<22 with MI_USE_GGTT/MI_MEM_VIRTUAL

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/selftests: Replace magic 1<<22 with MI_USE_GGTT/MI_MEM_VIRTUAL URL : https://patchwork.freedesktop.org/series/46078/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4446 -> Patchwork_9570 = == Summary - SUCCESS

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/6] dma-buf: add caching of sg_table

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/6] dma-buf: add caching of sg_table URL : https://patchwork.freedesktop.org/series/46080/ State : failure == Summary == Applying: dma-buf: add caching of sg_table Applying: drm: remove prime sg_table caching Applying: dma-buf: add dma_buf_(u

[Intel-gfx] [PATCH v5] drm/i915/gen11: Preempt-to-idle support in execlists.

2018-07-06 Thread Tomasz Lis
The patch adds support of preempt-to-idle requesting by setting a proper bit within Execlist Control Register, and receiving preemption result from Context Status Buffer. Preemption in previous gens required a special batch buffer to be executed, so the Command Streamer never preempted to idle dir

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Limit live_gtt allocation test to fit within RAM

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Limit live_gtt allocation test to fit within RAM URL : https://patchwork.freedesktop.org/series/46075/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4446 -> Patchwork_9569 = == Summary - SUCCESS == No regressions found.

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/selftests: Limit live_gtt allocation test to fit within RAM

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Limit live_gtt allocation test to fit within RAM URL : https://patchwork.freedesktop.org/series/46075/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915/selftests: Limit live_gtt allocation test to fit within RAM +driver

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2)

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2) URL : https://patchwork.freedesktop.org/series/46067/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4446 -> Patchwork_9568 = == Summary - SUCCES

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2)

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2) URL : https://patchwork.freedesktop.org/series/46067/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915: Refactor export_fence() after i915

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2)

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2) URL : https://patchwork.freedesktop.org/series/46067/ State : warning == Summary == $ dim checkpatch origin/drm-tip c404016bcc1d drm/i915: Refactor export_fence() a

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/gtt: Suppress warnings for dma_map_page

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/gtt: Suppress warnings for dma_map_page URL : https://patchwork.freedesktop.org/series/46072/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4446 -> Patchwork_9567 = == Summary - SUCCESS == No regressions f

Re: [Intel-gfx] [PATCH 1/2] drm/i915/selftests: Replace magic 1<<22 with MI_USE_GGTT/MI_MEM_VIRTUAL

2018-07-06 Thread Chris Wilson
Quoting Ville Syrjälä (2018-07-06 15:47:25) > On Fri, Jul 06, 2018 at 03:23:22PM +0100, Chris Wilson wrote: > > diff --git a/drivers/gpu/drm/i915/selftests/i915_gem_coherency.c > > b/drivers/gpu/drm/i915/selftests/i915_gem_coherency.c > > index cb9eef1635e1..294c58aba2c1 100644 > > --- a/drivers/g

Re: [Intel-gfx] [PATCH 2/2] drm/i915/selftests: Fixup missing MI_MEM_VIRTUAL for live_hangcheck

2018-07-06 Thread Ville Syrjälä
On Fri, Jul 06, 2018 at 03:23:23PM +0100, Chris Wilson wrote: > We always want to use a virtual address (i.e. use the GTT) for > MI_STORE_DWORD_IMM, but forgot the ever so important flag in > live_hangcheck for gen3. Reviewed-by: Ville Syrjälä > > Signed-off-by: Chris Wilson > --- > drivers/g

Re: [Intel-gfx] [PATCH 1/2] drm/i915/selftests: Replace magic 1<<22 with MI_USE_GGTT/MI_MEM_VIRTUAL

2018-07-06 Thread Ville Syrjälä
On Fri, Jul 06, 2018 at 03:23:22PM +0100, Chris Wilson wrote: > Replace the magic bit with the proper symbolic name for instructing > MI_STORE_DWORD_IMM to use a virtual address (on gen3) or the global GTT > address (still virtual!) on gen4+. > > Signed-off-by: Chris Wilson > --- > drivers/gpu/d

[Intel-gfx] [PATCH 6/6] drm/amdgpu: add independent DMA-buf import v4

2018-07-06 Thread Christian König
Instead of relying on the DRM functions just implement our own import functions. This prepares support for taking care of unpinned DMA-buf. v2: enable for all exporters, not just amdgpu, fix invalidation handling, lock reservation object while setting callback v3: change to new dma_buf attach

[Intel-gfx] [PATCH 2/6] drm: remove prime sg_table caching

2018-07-06 Thread Christian König
That is now done by the DMA-buf helpers instead. Signed-off-by: Christian König --- drivers/gpu/drm/drm_prime.c | 78 +++-- 1 file changed, 18 insertions(+), 60 deletions(-) diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c index 186d

[Intel-gfx] [PATCH 1/6] dma-buf: add caching of sg_table

2018-07-06 Thread Christian König
To allow a smooth transition from pinning buffer objects to dynamic invalidation we first start to cache the sg_table for an attachment unless the driver explicitly says to not do so. Signed-off-by: Christian König --- drivers/dma-buf/dma-buf.c | 24 include/linux/dma-bu

[Intel-gfx] [PATCH 3/6] dma-buf: add dma_buf_(un)map_attachment_locked variants v3

2018-07-06 Thread Christian König
Add function variants which can be called with the reservation lock already held. v2: reordered, add lockdep asserts, fix kerneldoc v3: rebased on sgt caching Signed-off-by: Christian König --- drivers/dma-buf/dma-buf.c | 63 +++ include/linux/dma-buf

[Intel-gfx] [PATCH 5/6] drm/amdgpu: add independent DMA-buf export v3

2018-07-06 Thread Christian König
The caching of SGT's is actually quite harmful and should probably removed altogether when all drivers are audited. Start by providing a separate DMA-buf export implementation in amdgpu. This is also a prerequisite of unpinned DMA-buf handling. v2: fix unintended recursion, remove debugging lefto

[Intel-gfx] (no subject)

2018-07-06 Thread Christian König
Next try of prework for unpinned DMA-buf operation. Only send to intel-gfx to trigger unit tests on the following patches. Christian. ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx

[Intel-gfx] [PATCH 4/6] dma-buf: lock the reservation object during (un)map_dma_buf v3

2018-07-06 Thread Christian König
First step towards unpinned DMA buf operation. I've checked the DRM drivers to potential locking of the reservation object, but essentially we need to audit all implementations of the dma_buf _ops for this to work. v2: reordered v3: rebased on sgt caching Signed-off-by: Christian König --- dri

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/3] drm: Extract __setplane_check() (rev3)

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/3] drm: Extract __setplane_check() (rev3) URL : https://patchwork.freedesktop.org/series/45589/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4438_full -> Patchwork_9557_full = == Summary - WARNING == Minor unknown cha

[Intel-gfx] [PATCH 2/2] drm/i915/selftests: Fixup missing MI_MEM_VIRTUAL for live_hangcheck

2018-07-06 Thread Chris Wilson
We always want to use a virtual address (i.e. use the GTT) for MI_STORE_DWORD_IMM, but forgot the ever so important flag in live_hangcheck for gen3. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/selftests/intel_hangcheck.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[Intel-gfx] [PATCH 1/2] drm/i915/selftests: Replace magic 1<<22 with MI_USE_GGTT/MI_MEM_VIRTUAL

2018-07-06 Thread Chris Wilson
Replace the magic bit with the proper symbolic name for instructing MI_STORE_DWORD_IMM to use a virtual address (on gen3) or the global GTT address (still virtual!) on gen4+. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/selftests/huge_pages.c | 4 ++-- drivers/gpu/drm/i915/selfte

Re: [Intel-gfx] [PATCH 4/4] drm/i915/intel_dsi: Read back pclk set by GOP and use that as pclk

2018-07-06 Thread Ville Syrjälä
On Tue, Jun 19, 2018 at 10:18:27PM +0200, Hans de Goede wrote: > On BYT and CHT the GOP sometimes initializes the pclk at a (slightly) > different frequency then the pclk which we've calculated. > > This commit makes the DSI code read-back the pclk set by the GOP and > if that is within a reasonab

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/psr: Split sink status into a separate debugfs node

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/psr: Split sink status into a separate debugfs node URL : https://patchwork.freedesktop.org/series/45952/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4438_full -> Patchwork_9555_full = == Summary - WARNING == Minor unknown changes

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t] igt/gem_pwrite_pread: Requires GEM

2018-07-06 Thread Tvrtko Ursulin
On 04/07/2018 15:38, Chris Wilson wrote: Mark up gem_pwrite_pread's dependence on a functioning GPU, by calling igt_require_gem in its setup fixture. Signed-off-by: Chris Wilson --- tests/gem_pwrite_pread.c | 1 + tests/gem_tiled_partial_pwrite_pread.c | 1 + 2 files changed,

Re: [Intel-gfx] [PATCH 17/27] drm/i915: Replace nested subclassing with explicit subclasses

2018-07-06 Thread Tvrtko Ursulin
On 06/07/2018 07:53, Chris Wilson wrote: In the next patch, we will want a third distinct class of timeline that may overlap with the current pair of client and engine timeline classes. Rather than use the ad hoc markup of SINGLE_DEPTH_NESTING, initialise the different timeline classes with an e

Re: [Intel-gfx] [PATCH 0/4] drm/i915/intel_dsi: Read back and use pclk set by the GOP

2018-07-06 Thread Jani Nikula
On Fri, 29 Jun 2018, Hans de Goede wrote: > Hi, > > On 19-06-18 22:18, Hans de Goede wrote: >> Hi All, >> >> This patch-set is the result of the work I've been doing recently to >> give people a smooth "flickerfree" boot experience where the display >> keeps displaying the logo put there by the f

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Limit live_gtt allocation test to fit within RAM

2018-07-06 Thread Matthew Auld
On 6 July 2018 at 13:53, Chris Wilson wrote: > Limit the GTT size we try and allocate to ensure that it fits within RAM > and does not trigger the oomkiller indiscriminately. > > Signed-off-by: Chris Wilson > Cc: Matthew Auld Reviewed-by: Matthew Auld ___

Re: [Intel-gfx] [PATCH] drm/crc: Only report a single overflow when a CRC fd is opened

2018-07-06 Thread Maarten Lankhorst
Op 18-04-18 om 17:37 schreef Ville Syrjälä: > On Wed, Apr 18, 2018 at 02:51:21PM +0200, Maarten Lankhorst wrote: >> This reduces the amount of spam when you debug a CRC reading >> program. >> >> Signed-off-by: Maarten Lankhorst >> --- >> drivers/gpu/drm/drm_debugfs_crc.c | 9 - >> include

Re: [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/ddi: Simplify get_encoder_power_domains()

2018-07-06 Thread Imre Deak
On Thu, Jul 05, 2018 at 04:33:50PM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/ddi: Simplify get_encoder_power_domains() > URL : https://patchwork.freedesktop.org/series/45980/ > State : success Pushed to -dinq, thanks for the review. > > == Summary == > > = CI Bug Lo

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Flush the WCB following a WC write

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Flush the WCB following a WC write URL : https://patchwork.freedesktop.org/series/46070/ State : success == Summary == = CI Bug Log - changes from CI_DRM_ -> Patchwork_9566 = == Summary - SUCCESS == No regressions found. External URL: https://

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gtt: Control cache domain of dma_map_page() directly

2018-07-06 Thread Matthew Auld
On 6 July 2018 at 13:26, Chris Wilson wrote: > We already maually control the CPU cache for our page table directories, > so we can tell the dma mapper to skip doing it as well. > > Signed-off-by: Chris Wilson > Cc: Matthew Auld Reviewed-by: Matthew Auld

[Intel-gfx] [PATCH] drm/i915/selftests: Limit live_gtt allocation test to fit within RAM

2018-07-06 Thread Chris Wilson
Limit the GTT size we try and allocate to ensure that it fits within RAM and does not trigger the oomkiller indiscriminately. Signed-off-by: Chris Wilson Cc: Matthew Auld --- drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 20 --- 1 file changed, 13 insertions(+), 7 deletions(-)

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftests: Destroy partial tiling vma after use

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Destroy partial tiling vma after use URL : https://patchwork.freedesktop.org/series/46031/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4438_full -> Patchwork_9554_full = == Summary - FAILURE == Serious unknown changes co

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Flush the WCB following a WC write

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Flush the WCB following a WC write URL : https://patchwork.freedesktop.org/series/46070/ State : warning == Summary == $ dim checkpatch origin/drm-tip 1442df0746fe drm/i915: Flush the WCB following a WC write -:25: WARNING:MEMORY_BARRIER: memory barrier w

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Skip live_execlists if the GPU is terminally wedged

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Skip live_execlists if the GPU is terminally wedged URL : https://patchwork.freedesktop.org/series/46069/ State : success == Summary == = CI Bug Log - changes from CI_DRM_ -> Patchwork_9565 = == Summary - SUCCESS == No regressions found.

Re: [Intel-gfx] [PATCH 1/2] drm/i915/gtt: Suppress warnings for dma_map_page

2018-07-06 Thread Matthew Auld
On 6 July 2018 at 13:26, Chris Wilson wrote: > As we propagate back the error to the caller for them to handle, we do > not need the lowest level spitting out a redundant warning upon an > allocation failure inside dma_map_page(). > > Signed-off-by: Chris Wilson > Cc: Matthew Auld Reviewed-by: M

Re: [Intel-gfx] [PATCH] drm/i915: Flush the WCB following a WC write

2018-07-06 Thread Tvrtko Ursulin
On 06/07/2018 12:54, Chris Wilson wrote: If we have just completed a WC write, we must ensure that the WCB (Write Combining Buffer) is flushed out to main memory before we can expect to see the results. This is especially important when mixing WC with GTT as the physical paths are different and

[Intel-gfx] [PATCH v5] drm/i915: Track the last-active inside the i915_vma

2018-07-06 Thread Chris Wilson
Using a VMA on more than one timeline concurrently is the exception rather than the rule (using it concurrently on multiple engines). As we expect to only use one active tracker, store the most recently used tracker inside the i915_vma itself and only fallback to the rbtree if we need a second or m

[Intel-gfx] [PATCH 2/2] drm/i915/gtt: Control cache domain of dma_map_page() directly

2018-07-06 Thread Chris Wilson
We already maually control the CPU cache for our page table directories, so we can tell the dma mapper to skip doing it as well. Signed-off-by: Chris Wilson Cc: Matthew Auld --- drivers/gpu/drm/i915/i915_gem_gtt.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/i915/i915_g

[Intel-gfx] [PATCH 1/2] drm/i915/gtt: Suppress warnings for dma_map_page

2018-07-06 Thread Chris Wilson
As we propagate back the error to the caller for them to handle, we do not need the lowest level spitting out a redundant warning upon an allocation failure inside dma_map_page(). Signed-off-by: Chris Wilson Cc: Matthew Auld --- drivers/gpu/drm/i915/i915_gem_gtt.c | 12 1 file chan

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active()

2018-07-06 Thread Chris Wilson
Quoting Patchwork (2018-07-06 13:20:19) > == Series Details == > > Series: series starting with [1/6] drm/i915: Refactor export_fence() after > i915_vma_move_to_active() > URL : https://patchwork.freedesktop.org/series/46067/ > State : failure > > == Summary == > > = CI Bug Log - changes from

Re: [Intel-gfx] [PATCH v3 00/12] drm/i915: Some plane init cleanups

2018-07-06 Thread Lisovskiy, Stanislav
On Fri, 2018-06-01 at 20:00 +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Another version of these cleansup. Last time there was some kind of > smtp > fail when sending and patchwork got confused at the wonky threading. > So > best to repost fully I thought. Additionally I had to resolve

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active()

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() URL : https://patchwork.freedesktop.org/series/46067/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_ -> Patchwork_9564 = == Summary - FAILURE ==

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Skip live_execlists if the GPU is terminally wedged

2018-07-06 Thread Matthew Auld
On 6 July 2018 at 12:45, Chris Wilson wrote: > If the GPU is irrecoverably wedged, we can not execute any requests > making testing execlists (request execution) pointless. Skip! > > Signed-off-by: Chris Wilson > Cc: Matthew Auld Reviewed-by: Matthew Auld ___

Re: [Intel-gfx] [PATCH] drm/i915: Flush the WCB following a WC write

2018-07-06 Thread Matthew Auld
On 6 July 2018 at 12:54, Chris Wilson wrote: > If we have just completed a WC write, we must ensure that the WCB (Write > Combining Buffer) is flushed out to main memory before we can expect to > see the results. This is especially important when mixing WC with GTT as > the physical paths are diff

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active()

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() URL : https://patchwork.freedesktop.org/series/46067/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915: Refactor export_fence() after i915_vma_mo

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active()

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() URL : https://patchwork.freedesktop.org/series/46067/ State : warning == Summary == $ dim checkpatch origin/drm-tip 478556e2da64 drm/i915: Refactor export_fence() after i9

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Record logical context support in driver caps (rev2)

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915: Record logical context support in driver caps (rev2) URL : https://patchwork.freedesktop.org/series/46065/ State : success == Summary == = CI Bug Log - changes from CI_DRM_ -> Patchwork_9563 = == Summary - SUCCESS == No

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/selftests: Detect unknown swizzling correctly

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Detect unknown swizzling correctly URL : https://patchwork.freedesktop.org/series/46026/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4438_full -> Patchwork_9553_full = == Summary - WARNING == Minor unknown changes coming

  1   2   >