Re: [Intel-gfx] [PATCH 3/4] drm/i915: peel dma-fence-chains wait fences

2020-04-10 Thread kbuild test robot
Hi Venkata, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on drm-tip/drm-tip] [cannot apply to drm-intel/for-linux-next linus/master v5.6 next-20200410] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we

[Intel-gfx] ✓ Fi.CI.IGT: success for cpufreq/pstate: Only mention the BIOS disabling turbo mode once

2020-04-10 Thread Patchwork
== Series Details == Series: cpufreq/pstate: Only mention the BIOS disabling turbo mode once URL : https://patchwork.freedesktop.org/series/75815/ State : success == Summary == CI Bug Log - changes from CI_DRM_8290_full -> Patchwork_17280_full

Re: [Intel-gfx] [PATCH i-g-t] kms_flip: Reduce hang tests to minimum duration

2020-04-10 Thread Andi Shyti
Hi Chris, On Wed, Apr 08, 2020 at 11:24:08AM +0100, Chris Wilson wrote: > Hang tests are slow since we must wait for the kernel to detect the GPU > hang before it forcibly completes the execution and signals the fence. > The flip is not allowed before the fence is signaled and so must wait. > Our

[Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [v3,1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD

2020-04-10 Thread Patchwork
== Series Details == Series: series starting with [v3,1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD URL : https://patchwork.freedesktop.org/series/75820/ State : failure == Summary == Applying: drm/dp: DRM DP helper for reading Ignore MSA from DPCD Applying: drm/i915/dp: Attach

[Intel-gfx] [PATCH v3 3/3] drm/i915/dp: Expose connector VRR info via debugfs

2020-04-10 Thread Manasi Navare
From: Bhanuprakash Modem [Why] It's useful to know the min and max vrr range for IGT testing. [How] Expose the min and max vfreq for the connector via a debugfs file on the connector, "i915_vrr_info". Example usage: cat /sys/kernel/debug/dri/0/DP-1/i915_vrr_info v2: * Fix the typo in

[Intel-gfx] [PATCH v3 2/3] drm/i915/dp: Attach and set drm connector VRR property

2020-04-10 Thread Manasi Navare
From: Aditya Swarup This function sets the VRR property for connector based on the platform support, EDID monitor range and DP sink DPCD capability of outputing video without msa timing information. v3: * intel_dp_is_vrr_capable can be used for debugfs, make it non static (Manasi) v2: * Just

[Intel-gfx] [PATCH v3 1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD

2020-04-10 Thread Manasi Navare
DP sink device sets the Ignore MSA bit in its DP_DOWNSTREAM_PORT_COUNT register to indicate its ability to ignore the MSA video timing parameters and its ability to support seamless video timing change over a range of timing exposed by DisplayID and EDID. This is required for the sink to indicate

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/gt: remove redundant assignment to variable x

2020-04-10 Thread Patchwork
== Series Details == Series: drm/i915/gt: remove redundant assignment to variable x URL : https://patchwork.freedesktop.org/series/75814/ State : success == Summary == CI Bug Log - changes from CI_DRM_8290_full -> Patchwork_17279_full

Re: [Intel-gfx] [PATCH 4/4] drm/selftests: selftest for timeline semaphore

2020-04-10 Thread kbuild test robot
Hi Venkata, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on drm-tip/drm-tip] [cannot apply to drm-intel/for-linux-next linus/master v5.6 next-20200410] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we

[Intel-gfx] ✓ Fi.CI.BAT: success for cpufreq/pstate: Only mention the BIOS disabling turbo mode once

2020-04-10 Thread Patchwork
== Series Details == Series: cpufreq/pstate: Only mention the BIOS disabling turbo mode once URL : https://patchwork.freedesktop.org/series/75815/ State : success == Summary == CI Bug Log - changes from CI_DRM_8290 -> Patchwork_17280

Re: [Intel-gfx] Linus, please revert 7dc8f11437: regression in 5.7-rc0, hangs while attempting to run X

2020-04-10 Thread Linus Torvalds
On Tue, Apr 7, 2020 at 12:48 AM Pavel Machek wrote: > > > > > Beyond the fix already submitted? > > I did not get that one, can I have a pointer? What's the status of this one? I'm assuming the fix is commit 721017cf4bd8 ("drm/i915/gem: Ignore readonly failures when updating relics"), but

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: remove redundant assignment to variable x

2020-04-10 Thread Patchwork
== Series Details == Series: drm/i915/gt: remove redundant assignment to variable x URL : https://patchwork.freedesktop.org/series/75814/ State : success == Summary == CI Bug Log - changes from CI_DRM_8290 -> Patchwork_17279 Summary

Re: [Intel-gfx] [PATCH] drm/i915: Flush async power domains on probe failure

2020-04-10 Thread Souza, Jose
On Fri, 2020-04-10 at 15:43 +0100, Chris Wilson wrote: > Flush the async power domain work after aborting the module probe: > > <3> [307.785552] ODEBUG: free active (active state 0) object type: > timer_list hint: intel_display_power_put_async_work+0x0/0xf0 [i915] > > Closes:

Re: [Intel-gfx] [PATCH 5/7] PM: sleep: core: Rename DPM_FLAG_NEVER_SKIP

2020-04-10 Thread Bjorn Helgaas
On Fri, Apr 10, 2020 at 05:56:13PM +0200, Rafael J. Wysocki wrote: > From: "Rafael J. Wysocki" > > Rename DPM_FLAG_NEVER_SKIP to DPM_FLAG_NO_DIRECT_COMPLETE which > matches its purpose more closely. > > No functional impact. > > Signed-off-by: Rafael J. Wysocki Acked-by: Bjorn Helgaas # for

[Intel-gfx] [PATCH] cpufreq/pstate: Only mention the BIOS disabling turbo mode once

2020-04-10 Thread Chris Wilson
Make a note of the first time we discover the turbo mode has been disabled by the BIOS, as otherwise we complain every time we try to update the mode. Signed-off-by: Chris Wilson Cc: Srinivas Pandruvada Cc: Len Brown Cc: "Rafael J. Wysocki" Cc: Viresh Kumar ---

[Intel-gfx] [PATCH] drm/i915/gt: remove redundant assignment to variable x

2020-04-10 Thread Colin King
From: Colin Ian King The variable x is being initialized with a value that is never read and it is being updated later with a new value. The initialization is redundant and can be removed. Addresses-Coverity: ("Unused value") Signed-off-by: Colin Ian King ---

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Flush async power domains on probe failure

2020-04-10 Thread Patchwork
== Series Details == Series: drm/i915: Flush async power domains on probe failure URL : https://patchwork.freedesktop.org/series/75805/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8290_full -> Patchwork_17277_full

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/4] drm/i915: introduce a mechanism to extend execbuf2

2020-04-10 Thread Patchwork
== Series Details == Series: series starting with [1/4] drm/i915: introduce a mechanism to extend execbuf2 URL : https://patchwork.freedesktop.org/series/75810/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8290 -> Patchwork_17278

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for SAGV support for Gen12+ (rev18)

2020-04-10 Thread Lisovskiy, Stanislav
Seems to be some issue in lmem self tests: :<4> [342.485150] intel_pstate: Turbo disabled by BIOS or unavailable on processor. This is not related to SAGV. Best Regards, Lisovskiy Stanislav Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/4] drm/i915: introduce a mechanism to extend execbuf2

2020-04-10 Thread Patchwork
== Series Details == Series: series starting with [1/4] drm/i915: introduce a mechanism to extend execbuf2 URL : https://patchwork.freedesktop.org/series/75810/ State : warning == Summary == $ dim sparse origin/drm-tip Sparse version: v0.6.0 Commit: drm/i915: introduce a mechanism to extend

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915: introduce a mechanism to extend execbuf2

2020-04-10 Thread Patchwork
== Series Details == Series: series starting with [1/4] drm/i915: introduce a mechanism to extend execbuf2 URL : https://patchwork.freedesktop.org/series/75810/ State : warning == Summary == $ dim checkpatch origin/drm-tip f52f98b82c3b drm/i915: introduce a mechanism to extend execbuf2

[Intel-gfx] [PATCH 4/4] drm/selftests: selftest for timeline semaphore

2020-04-10 Thread Venkata Sandeep Dhanalakota
simple tests using drm api for timeline semaphore. Signed-off-by: Venkata Sandeep Dhanalakota --- drivers/gpu/drm/selftests/Makefile| 2 +- .../drm/selftests/drm_timeline_selftests.h| 16 + .../selftests/test-drm_timeline_semaphore.c | 545 ++ 3 files

[Intel-gfx] [PATCH 3/4] drm/i915: peel dma-fence-chains wait fences

2020-04-10 Thread Venkata Sandeep Dhanalakota
From: Lionel Landwerlin To allow faster engine to engine synchronization, peel the layer of dma-fence-chain to expose potential i915 fences so that the i915-request code can emit HW semaphore wait/signal operations in the ring which is faster than waking up the host to submit unblocked workloads

[Intel-gfx] [PATCH 2/4] drm/i915: add syncobj timeline support

2020-04-10 Thread Venkata Sandeep Dhanalakota
Introduces a new parameters to execbuf so that we can specify syncobj handles as well as timeline points. v2: Reuse i915_user_extension_fn v3: Check that the chained extension is only present once (Chris) v4: Check that dma_fence_chain_find_seqno returns a non NULL fence (Lionel) v5: Use

[Intel-gfx] [PATCH 1/4] drm/i915: introduce a mechanism to extend execbuf2

2020-04-10 Thread Venkata Sandeep Dhanalakota
From: Lionel Landwerlin We're planning to use this for a couple of new feature where we need to provide additional parameters to execbuf. v2: Check for invalid flags in execbuffer2 (Lionel) v3: Rename I915_EXEC_EXT -> I915_EXEC_USE_EXTENSIONS (Chris) Signed-off-by: Lionel Landwerlin

Re: [Intel-gfx] [PATCH 05/10] dma-buf: Exercise dma-fence-chain under selftests

2020-04-10 Thread Lionel Landwerlin
On 03/04/2020 12:12, Chris Wilson wrote: A few very simple testcases to exercise the dma-fence-chain API. Signed-off-by: Chris Wilson --- drivers/dma-buf/Makefile | 3 +- drivers/dma-buf/selftests.h | 1 + drivers/dma-buf/st-dma-fence-chain.c | 713

[Intel-gfx] [PATCH 5/7] PM: sleep: core: Rename DPM_FLAG_NEVER_SKIP

2020-04-10 Thread Rafael J. Wysocki
From: "Rafael J. Wysocki" Rename DPM_FLAG_NEVER_SKIP to DPM_FLAG_NO_DIRECT_COMPLETE which matches its purpose more closely. No functional impact. Signed-off-by: Rafael J. Wysocki --- Documentation/driver-api/pm/devices.rst| 6 +++--- Documentation/power/pci.rst| 10

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Check for an already completed timeslice

2020-04-10 Thread Andi Shyti
Hi Chris, > With timeslice yielding on a semaphore, we may complete timeslices much > faster than we were expecting and already have yielded the stuck > request. Before complaining that timeslicing is not enabled, check that > we haven't already applied the switch. > > Signed-off-by: Chris

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Flush async power domains on probe failure

2020-04-10 Thread Patchwork
== Series Details == Series: drm/i915: Flush async power domains on probe failure URL : https://patchwork.freedesktop.org/series/75805/ State : success == Summary == CI Bug Log - changes from CI_DRM_8290 -> Patchwork_17277 Summary ---

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Flush async power domains on probe failure

2020-04-10 Thread Patchwork
== Series Details == Series: drm/i915: Flush async power domains on probe failure URL : https://patchwork.freedesktop.org/series/75805/ State : warning == Summary == $ dim checkpatch origin/drm-tip a52e41b23f79 drm/i915: Flush async power domains on probe failure -:11:

[Intel-gfx] [PATCH] drm/i915: Flush async power domains on probe failure

2020-04-10 Thread Chris Wilson
Flush the async power domain work after aborting the module probe: <3> [307.785552] ODEBUG: free active (active state 0) object type: timer_list hint: intel_display_power_put_async_work+0x0/0xf0 [i915] Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/1647 Fixes: b664259f3fe2

[Intel-gfx] ✓ Fi.CI.IGT: success for agp/intel: Reinforce the barrier after GTT updates (rev2)

2020-04-10 Thread Patchwork
== Series Details == Series: agp/intel: Reinforce the barrier after GTT updates (rev2) URL : https://patchwork.freedesktop.org/series/75785/ State : success == Summary == CI Bug Log - changes from CI_DRM_8289_full -> Patchwork_17274_full

Re: [Intel-gfx] [PATCH] agp/intel: Reinforce the barrier after GTT updates

2020-04-10 Thread Andi Shyti
Hi Chris, > After changing the timing between GTT updates and execution on the GPU, > we started seeing sporadic failures on Ironlake. These were narrowed > down to being an insufficiently strong enough barrier/delay after > updating the GTT and scheduling execution on the GPU. By forcing the >

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display: Poison the async power domain on shutdown

2020-04-10 Thread Patchwork
== Series Details == Series: drm/i915/display: Poison the async power domain on shutdown URL : https://patchwork.freedesktop.org/series/75784/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8289_full -> Patchwork_17273_full

[Intel-gfx] ✗ Fi.CI.BAT: failure for SAGV support for Gen12+ (rev18)

2020-04-10 Thread Patchwork
== Series Details == Series: SAGV support for Gen12+ (rev18) URL : https://patchwork.freedesktop.org/series/75129/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8289 -> Patchwork_17276 Summary --- **FAILURE**

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftests: Check for an already completed timeslice

2020-04-10 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Check for an already completed timeslice URL : https://patchwork.freedesktop.org/series/75783/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8288_full -> Patchwork_17272_full

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for SAGV support for Gen12+ (rev18)

2020-04-10 Thread Patchwork
== Series Details == Series: SAGV support for Gen12+ (rev18) URL : https://patchwork.freedesktop.org/series/75129/ State : warning == Summary == $ dim sparse origin/drm-tip Sparse version: v0.6.0 Commit: drm/i915: Start passing latency as parameter Okay! Commit: drm/i915: Eliminate magic

[Intel-gfx] [PATCH v23 09/13] drm/i915: Add TGL+ SAGV support

2020-04-10 Thread Stanislav Lisovskiy
Starting from TGL we need to have a separate wm0 values for SAGV and non-SAGV which affects how calculations are done. v2: Remove long lines Signed-off-by: Stanislav Lisovskiy --- drivers/gpu/drm/i915/display/intel_display.c | 8 +- .../drm/i915/display/intel_display_types.h| 3 +

[Intel-gfx] [PATCH v23 08/13] drm/i915: Separate icl and skl SAGV checking

2020-04-10 Thread Stanislav Lisovskiy
Introduce platform dependent SAGV checking in combination with bandwidth state pipe SAGV mask. v2: Fix rebase conflict Signed-off-by: Stanislav Lisovskiy --- drivers/gpu/drm/i915/intel_pm.c | 39 +++-- 1 file changed, 27 insertions(+), 12 deletions(-) diff --git

[Intel-gfx] [PATCH v23 07/13] drm/i915: Use bw state for per crtc SAGV evaluation

2020-04-10 Thread Stanislav Lisovskiy
Future platforms require per-crtc SAGV evaluation and serializing global state when those are changed from different commits. v2: - Add has_sagv check to intel_crtc_can_enable_sagv so that it sets bit in reject mask. - Use bw_state in intel_pre/post_plane_enable_sagv instead of

[Intel-gfx] [PATCH v23 05/13] drm/i915: Prepare to extract gen specific functions from intel_can_enable_sagv

2020-04-10 Thread Stanislav Lisovskiy
Addressing one of the comments, recommending to extract platform specific code from intel_can_enable_sagv as a preparation, before we are going to add support for tgl+. v2: - Removed whitespace Signed-off-by: Stanislav Lisovskiy --- drivers/gpu/drm/i915/intel_pm.c | 66

[Intel-gfx] ✗ Fi.CI.BUILD: failure for Patch "drm/i915: Fix ref->mutex deadlock in i915_active_wait()" has been added to the 5.4-stable tree

2020-04-10 Thread Patchwork
== Series Details == Series: Patch "drm/i915: Fix ref->mutex deadlock in i915_active_wait()" has been added to the 5.4-stable tree URL : https://patchwork.freedesktop.org/series/75798/ State : failure == Summary == Patch is empty. When you have resolved this problem, run "git am --continue".

[Intel-gfx] Patch "drm/i915: Fix ref->mutex deadlock in i915_active_wait()" has been added to the 5.4-stable tree

2020-04-10 Thread gregkh
This is a note to let you know that I've just added the patch titled drm/i915: Fix ref->mutex deadlock in i915_active_wait() to the 5.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is:

[Intel-gfx] ✓ Fi.CI.BAT: success for agp/intel: Reinforce the barrier after GTT updates (rev2)

2020-04-10 Thread Patchwork
== Series Details == Series: agp/intel: Reinforce the barrier after GTT updates (rev2) URL : https://patchwork.freedesktop.org/series/75785/ State : success == Summary == CI Bug Log - changes from CI_DRM_8289 -> Patchwork_17274 Summary

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for agp/intel: Reinforce the barrier after GTT updates (rev2)

2020-04-10 Thread Patchwork
== Series Details == Series: agp/intel: Reinforce the barrier after GTT updates (rev2) URL : https://patchwork.freedesktop.org/series/75785/ State : warning == Summary == $ dim checkpatch origin/drm-tip c1e1db29df8c agp/intel: Reinforce the barrier after GTT updates -:42:

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Poison the async power domain on shutdown

2020-04-10 Thread Patchwork
== Series Details == Series: drm/i915/display: Poison the async power domain on shutdown URL : https://patchwork.freedesktop.org/series/75784/ State : success == Summary == CI Bug Log - changes from CI_DRM_8289 -> Patchwork_17273 Summary

Re: [Intel-gfx] [PATCH v2] drm/i915: Fix ref->mutex deadlock in i915_active_wait()

2020-04-10 Thread Greg KH
On Tue, Apr 07, 2020 at 12:18:09AM -0700, Sultan Alsawaf wrote: > From: Sultan Alsawaf > > The following deadlock exists in i915_active_wait() due to a double lock > on ref->mutex (call chain listed in order from top to bottom): > i915_active_wait(); > mutex_lock_interruptible(>mutex); <--

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Check for an already completed timeslice

2020-04-10 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Check for an already completed timeslice URL : https://patchwork.freedesktop.org/series/75783/ State : success == Summary == CI Bug Log - changes from CI_DRM_8288 -> Patchwork_17272 Summary

[Intel-gfx] [PATCH] agp/intel: Reinforce the barrier after GTT updates

2020-04-10 Thread Chris Wilson
After changing the timing between GTT updates and execution on the GPU, we started seeing sporadic failures on Ironlake. These were narrowed down to being an insufficiently strong enough barrier/delay after updating the GTT and scheduling execution on the GPU. By forcing the uncached read, and

[Intel-gfx] [PATCH] agp/intel: Reinforce the barrier after GTT updates

2020-04-10 Thread Chris Wilson
From: Chris Wilson After changing the timing between GTT updates and execution on the GPU, we started seeing sporadic failures on Ironlake. These were narrowed down to being an insufficiently strong enough barrier/delay after updating the GTT and scheduling execution on the GPU. By forcing the

[Intel-gfx] [PATCH] drm/i915/display: Poison the async power domain on shutdown

2020-04-10 Thread Chris Wilson
Lets see if we can find who is still running after the driver has been removed! Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/display/intel_display_power.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/i915/display/intel_display_power.c

[Intel-gfx] [PATCH] drm/i915/selftests: Check for an already completed timeslice

2020-04-10 Thread Chris Wilson
With timeslice yielding on a semaphore, we may complete timeslices much faster than we were expecting and already have yielded the stuck request. Before complaining that timeslicing is not enabled, check that we haven't already applied the switch. Signed-off-by: Chris Wilson ---

[Intel-gfx] ✗ Fi.CI.IGT: failure for SAGV support for Gen12+ (rev14)

2020-04-10 Thread Patchwork
== Series Details == Series: SAGV support for Gen12+ (rev14) URL : https://patchwork.freedesktop.org/series/75129/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8285_full -> Patchwork_17271_full Summary ---

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915: remove unneeded ccflags-y from gvt/Makefile

2020-04-10 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915: remove unneeded ccflags-y from gvt/Makefile URL : https://patchwork.freedesktop.org/series/75756/ State : success == Summary == CI Bug Log - changes from CI_DRM_8284_full -> Patchwork_17270_full

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: remove redundant assignment to variable err

2020-04-10 Thread Patchwork
== Series Details == Series: drm/i915: remove redundant assignment to variable err URL : https://patchwork.freedesktop.org/series/75747/ State : success == Summary == CI Bug Log - changes from CI_DRM_8284_full -> Patchwork_17269_full

[Intel-gfx] ✓ Fi.CI.IGT: success for HAX timer: Describe the delayed_work for a freed timer (rev2)

2020-04-10 Thread Patchwork
== Series Details == Series: HAX timer: Describe the delayed_work for a freed timer (rev2) URL : https://patchwork.freedesktop.org/series/75740/ State : success == Summary == CI Bug Log - changes from CI_DRM_8283_full -> Patchwork_17268_full