[Intel-gfx] [PULL] drm-intel-next

Hi Dave, Here goes drm-intel-next-2017-12-01. As Gustavo already pointed out, when applying this and drm-misc-next you will get the build failure. And the fix up is: - enum plane plane; + enum i9xx_plane_id plane; Changes on this tag: - Init clock gate fix (Ville) - Execlists event

[Intel-gfx] ✓ Fi.CI.IGT: success for lib: Print other clients when DRM_SET_MASTER fails

== Series Details == Series: lib: Print other clients when DRM_SET_MASTER fails URL : https://patchwork.freedesktop.org/series/35023/ State : success == Summary == Test drv_module_reload: Subgroup basic-reload: dmesg-warn -> PASS (shard-snb) fdo#102848

[Intel-gfx] [PATCH v2] drm/i915/execlists: Cache ELSP register offset

Currently on every submission, we recalculate the ELSP register offset for the engine, after chasing the pointers to find the iomem base. Since this is fixed for the lifetime of the driver record the offset in the execlists struct. In practice the difference is negligible, it just happens to

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/5] igt_dummyload: Wrap function parameters into struct

== Series Details == Series: series starting with [1/5] igt_dummyload: Wrap function parameters into struct URL : https://patchwork.freedesktop.org/series/35059/ State : success == Summary == Test kms_frontbuffer_tracking: Subgroup fbc-1p-offscren-pri-shrfb-draw-render:

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Refactor common list iteration over GGTT vma (rev3)

== Series Details == Series: drm/i915: Refactor common list iteration over GGTT vma (rev3) URL : https://patchwork.freedesktop.org/series/35048/ State : success == Summary == Series 35048v3 drm/i915: Refactor common list iteration over GGTT vma

Re: [Intel-gfx] [PATCH] drm/i915: Drop fb reference on load_detect_pipe failure path

Quoting Chris Wilson (2017-12-07 22:00:25) > When intel_modeset_setup_plane_state() fails drop the local framebuffer > reference before jumping to the error, otherwise we leak the framebuffer. > > Signed-off-by: Chris Wilson > Cc: Maarten Lankhorst

[Intel-gfx] [PATCH i-g-t 1/5] igt_dummyload: Wrap function parameters into struct

Cleanup the interface for creating dummyloads by folding its parameters into a struct. Cc: Chris Wilson Signed-off-by: Antonio Argenziano --- lib/igt_dummyload.c | 19 +++ lib/igt_dummyload.h | 16

[Intel-gfx] [PATCH i-g-t 2/5] igt_hang_ctx: Wrap hang_ctx parameters into struct

Cleanup the interface to create a hang on a context by folding its parameters into a struct. Cc: Chris Wilson Signed-off-by: Antonio Argenziano --- lib/igt_dummyload.c | 25 - lib/igt_gt.c| 41

Re: [Intel-gfx] [PATCH v2] drm/i915/execlists: Cache ELSP register offset

On Thu, Dec 07, 2017 at 10:24:34PM +, Chris Wilson wrote: > Currently on every submission, we recalculate the ELSP register offset > for the engine, after chasing the pointers to find the iomem base. Since > this is fixed for the lifetime of the driver record the offset in the > execlists

[Intel-gfx] [PATCH] drm/i915: Unwind i915_gem_init() failure

Since Michal introduced new errors other than -EIO during i915_gem_init(), we need to actually unwind on the error path as we have to abort the module load (and we expect to do so cleanly!). As we now teardown key state and then mark the driver as wedged (on EIO), we have to be careful to not

[Intel-gfx] [PATCH v2] drm/i915: Unwind i915_gem_init() failure

Since Michal introduced new errors other than -EIO during i915_gem_init(), we need to actually unwind on the error path as we have to abort the module load (and we expect to do so cleanly!). As we now teardown key state and then mark the driver as wedged (on EIO), we have to be careful to not

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Unwind i915_gem_init() failure (rev2)

== Series Details == Series: drm/i915: Unwind i915_gem_init() failure (rev2) URL : https://patchwork.freedesktop.org/series/35060/ State : success == Summary == Series 35060v2 drm/i915: Unwind i915_gem_init() failure https://patchwork.freedesktop.org/api/1.0/series/35060/revisions/2/mbox/

[Intel-gfx] ✗ Fi.CI.BAT: failure for tests/perf: Enable i915 perf tests on CNL

== Series Details == Series: tests/perf: Enable i915 perf tests on CNL URL : https://patchwork.freedesktop.org/series/35067/ State : failure == Summary == IGT patchset build failed on latest successful build 2fc64acf8a4465d5eab3d6cfec9b3c1b5df30d73 igt/perf_pmu: Tweak wait_for_rc6, yet again

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/5] drm/i915: Use snprintf to avoid line-break when pretty-printing engines

== Series Details == Series: series starting with [CI,1/5] drm/i915: Use snprintf to avoid line-break when pretty-printing engines URL : https://patchwork.freedesktop.org/series/35066/ State : success == Summary == Series 35066v1 series starting with [CI,1/5] drm/i915: Use snprintf to avoid

[Intel-gfx] ✗ Fi.CI.IGT: failure for tools: Cannonlake port clock programming

== Series Details == Series: tools: Cannonlake port clock programming URL : https://patchwork.freedesktop.org/series/35028/ State : failure == Summary == Test gem_tiled_swapping: Subgroup non-threaded: incomplete -> PASS (shard-hsw) fdo#104009 Test

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Drop fb reference on load_detect_pipe failure path

== Series Details == Series: drm/i915: Drop fb reference on load_detect_pipe failure path URL : https://patchwork.freedesktop.org/series/35057/ State : success == Summary == Series 35057v1 drm/i915: Drop fb reference on load_detect_pipe failure path

[Intel-gfx] [PATCH i-g-t 3/5] lib/igt_hang_ctx: Use recursive batch to hang ctx.

To hang a context we were effectively reimplementing a spinning batch and never stopping it. This patch reuses the recursive batch from igt_dummyload to hang a context. Cc: Chris Wilson Signed-off-by: Antonio Argenziano ---

[Intel-gfx] [PATCH i-g-t 4/5] igt_dummyload: Add preemptible parameter to recursive batch

This patch adds a parameter that allows to make the spinning batch pre-emptible by conditionally adding an arbitration point to the spinning loop. From RFC: - Implicitly initialize struct members to zero. (Chris) Cc: Chris Wilson Signed-off-by: Antonio

[Intel-gfx] [PATCH i-g-t 5/5] igt_hang_ctx: Add preemptible parameter

This patch adds a parameter to make the hanging context conditionally pre-emptible. Cc: Chris Wilson Signed-off-by: Antonio Argenziano --- lib/igt_gt.c | 2 +- lib/igt_gt.h | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff

[Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915/execlists: Cache ELSP register offset

== Series Details == Series: drm/i915/execlists: Cache ELSP register offset URL : https://patchwork.freedesktop.org/series/35054/ State : warning == Summary == Test kms_flip: Subgroup flip-vs-modeset-vs-hang: pass -> DMESG-WARN (shard-snb) Test kms_cursor_crc:

[Intel-gfx] ✗ Fi.CI.IGT: failure for igt/gem_mocs_settings: Force use of master device

== Series Details == Series: igt/gem_mocs_settings: Force use of master device URL : https://patchwork.freedesktop.org/series/35019/ State : failure == Summary == Test drv_suspend: Subgroup forcewake: skip -> PASS (shard-hsw) Subgroup sysfs-reader:

[Intel-gfx] [PATCH] drm/i915: Drop fb reference on load_detect_pipe failure path

When intel_modeset_setup_plane_state() fails drop the local framebuffer reference before jumping to the error, otherwise we leak the framebuffer. Signed-off-by: Chris Wilson Cc: Maarten Lankhorst Cc: Ville Syrjälä

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/execlists: Cache ELSP register offset (rev2)

== Series Details == Series: drm/i915/execlists: Cache ELSP register offset (rev2) URL : https://patchwork.freedesktop.org/series/35054/ State : success == Summary == Series 35054v2 drm/i915/execlists: Cache ELSP register offset

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/6] meson: Don't install headers

== Series Details == Series: series starting with [1/6] meson: Don't install headers URL : https://patchwork.freedesktop.org/series/35033/ State : failure == Summary == Test kms_flip: Subgroup flip-vs-panning: incomplete -> PASS (shard-hsw) Test

Re: [Intel-gfx] [PATCH igt] lib/i915: Update detection of GuC submission

On Thu, 07 Dec 2017 22:02:59 +0100, Chris Wilson wrote: Recently the kernel has switched to using a combined i915.enable_guc rather than multiple i915.enable_guc_submission parameters. Signed-off-by: Chris Wilson Cc: Michal Wajdeczko

Re: [Intel-gfx] [PATCH] Defined NM doesn't work on KBL and uses automatic N/M.

Hi, Jani I have created a Bugzilla in free desktop for tracking. https://bugs.freedesktop.org/show_bug.cgi?id=104093 Appreciate find audio expert could help us address root cause. Thank you. Quanxian -Original Message- From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org]

[Intel-gfx] [PATCH i-g-t 3/6] tests/perf: factorize max oa buffer size define

We use this value in several places. Signed-off-by: Lionel Landwerlin --- tests/perf.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/tests/perf.c b/tests/perf.c index 08ac106a..7f988d7c 100644 --- a/tests/perf.c +++ b/tests/perf.c

[Intel-gfx] [PATCH i-g-t 5/6] tests/perf: enable testing on Coffelake GT3

Add the test config uuid for GT3. Signed-off-by: Lionel Landwerlin --- tests/perf.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tests/perf.c b/tests/perf.c index ef37ceb3..cc0c21a1 100644 --- a/tests/perf.c +++ b/tests/perf.c @@ -1075,8

[Intel-gfx] [PATCH i-g-t 0/6] tests/perf: Enable i915 perf tests on CNL

Hi, Most of the work on the kernel side landed in drm-next. Time to enable this in IGT. Cheers, Lionel Landwerlin (6): include/drm-uapi: bump headers tests/perf: drop copied i915 defines/structs tests/perf: factorize max oa buffer size define tests/perf: query CS timestamp frequency if

Re: [Intel-gfx] [PATCH] drm/i915/execlists: Cache ELSP register offset

Quoting Michel Thierry (2017-12-07 22:19:05) > On 07/12/17 12:45, Chris Wilson wrote: > > Currently on every submission, we recalculate the ELSP register offset > > for the engine, after chasing the pointers to find the iomem base. Since > > this is fixed for the lifetime of the driver record the

[Intel-gfx] ✓ Fi.CI.IGT: success for lib/i915: Update detection of GuC submission

== Series Details == Series: lib/i915: Update detection of GuC submission URL : https://patchwork.freedesktop.org/series/35055/ State : success == Summary == Test kms_frontbuffer_tracking: Subgroup fbc-1p-offscren-pri-shrfb-draw-render: fail -> PASS

[Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915: Refactor common list iteration over GGTT vma (rev3)

== Series Details == Series: drm/i915: Refactor common list iteration over GGTT vma (rev3) URL : https://patchwork.freedesktop.org/series/35048/ State : warning == Summary == Test kms_pipe_crc_basic: Subgroup read-crc-pipe-b: incomplete -> PASS (shard-hsw) Test

Re: [Intel-gfx] [PATCH v2] drm/i915/execlists: Cache ELSP register offset

Quoting Rodrigo Vivi (2017-12-07 23:04:13) > On Thu, Dec 07, 2017 at 10:24:34PM +, Chris Wilson wrote: > > Currently on every submission, we recalculate the ELSP register offset > > for the engine, after chasing the pointers to find the iomem base. Since > > this is fixed for the lifetime of

Re: [Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915: Refactor common list iteration over GGTT vma (rev3)

Quoting Patchwork (2017-12-08 00:32:47) > == Series Details == > > Series: drm/i915: Refactor common list iteration over GGTT vma (rev3) > URL : https://patchwork.freedesktop.org/series/35048/ > State : warning > > == Summary == > > Test kms_pipe_crc_basic: > Subgroup read-crc-pipe-b:

[Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915: Drop fb reference on load_detect_pipe failure path

== Series Details == Series: drm/i915: Drop fb reference on load_detect_pipe failure path URL : https://patchwork.freedesktop.org/series/35057/ State : warning == Summary == Test kms_flip: Subgroup flip-vs-modeset-vs-hang: pass -> DMESG-WARN (shard-snb) Test

[Intel-gfx] ✗ Fi.CI.IGT: warning for intel/atomic: Stop updating legacy fb parameters (rev2)

== Series Details == Series: intel/atomic: Stop updating legacy fb parameters (rev2) URL : https://patchwork.freedesktop.org/series/34924/ State : warning == Summary == Test kms_cursor_crc: Subgroup cursor-64x64-suspend: skip -> PASS (shard-snb) fdo#102365

[Intel-gfx] linux-next: Signed-off-by missing for commit in the drm-intel-fixes tree

Hi all, Commit 365ad5df9caa ("drm/i915/gvt: Export intel_gvt_render_mmio_to_ring_id()") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org

[Intel-gfx] [PATCH i-g-t 6/6] tests/perf: add test config uuid for Cannonlake

This will enable running the tests on Cannonlake. Signed-off-by: Lionel Landwerlin --- tests/perf.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tests/perf.c b/tests/perf.c index cc0c21a1..99bcdc72 100644 --- a/tests/perf.c +++ b/tests/perf.c @@ -1082,6

[Intel-gfx] [PATCH i-g-t 4/6] tests/perf: query CS timestamp frequency if available

On Cannonlake+ the CS timestamp frequency might vary from one part to another. We have a new param to query this from the kernel (which reads the value from registers). Signed-off-by: Lionel Landwerlin --- tests/perf.c | 31 +-- 1 file

[Intel-gfx] [PATCH i-g-t 2/6] tests/perf: drop copied i915 defines/structs

Now that we have drm uapi headers in tree, we can drop this stuff. Signed-off-by: Lionel Landwerlin --- tests/perf.c | 114 --- 1 file changed, 7 insertions(+), 107 deletions(-) diff --git a/tests/perf.c

[Intel-gfx] [PATCH i-g-t 1/6] include/drm-uapi: bump headers

Taken from drm-next : commit 9c606cd4117a3c45e04a6616b1a0dbeb1862 Merge: c5dd52f653fa 3997eea57caf Author: Dave Airlie Date: Thu Dec 7 06:28:22 2017 +1000 Merge branch 'drm-next-4.16' of git://people.freedesktop.org/~agd5f/linux into drm-next Signed-off-by:

[Intel-gfx] ✓ Fi.CI.IGT: success for drm: More debug info for fb leaks in mode_config_cleanup

== Series Details == Series: drm: More debug info for fb leaks in mode_config_cleanup URL : https://patchwork.freedesktop.org/series/35038/ State : success == Summary == Test drv_suspend: Subgroup forcewake: skip -> PASS (shard-hsw) Test kms_cursor_crc:

Re: [Intel-gfx] [PATCH] drm/i915/execlists: Cache ELSP register offset

On 07/12/17 12:45, Chris Wilson wrote: Currently on every submission, we recalculate the ELSP register offset for the engine, after chasing the pointers to find the iomem base. Since this is fixed for the lifetime of the driver record the offset in the execlists struct. In practice the

[Intel-gfx] ✗ Fi.CI.IGT: warning for tests/kms_color: Rename pipe tests to standard notation

== Series Details == Series: tests/kms_color: Rename pipe tests to standard notation URL : https://patchwork.freedesktop.org/series/35031/ State : warning == Summary == Test kms_pipe_crc_basic: Subgroup read-crc-pipe-b: incomplete -> PASS (shard-hsw) Test

[Intel-gfx] ✗ Fi.CI.IGT: failure for lib/igt_sysfs: Let igt_sysfs_read|write return -errno (rev2)

== Series Details == Series: lib/igt_sysfs: Let igt_sysfs_read|write return -errno (rev2) URL : https://patchwork.freedesktop.org/series/34989/ State : failure == Summary == Test kms_pipe_crc_basic: Subgroup read-crc-pipe-b: incomplete -> PASS (shard-hsw) Test

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Unwind i915_gem_init() failure

== Series Details == Series: drm/i915: Unwind i915_gem_init() failure URL : https://patchwork.freedesktop.org/series/35060/ State : success == Summary == Series 35060v1 drm/i915: Unwind i915_gem_init() failure https://patchwork.freedesktop.org/api/1.0/series/35060/revisions/1/mbox/

Re: [Intel-gfx] [PATCH] drm/i915: Unwind i915_gem_init() failure

Quoting Chris Wilson (2017-12-07 23:56:25) > Since Michal introduced new errors other than -EIO during > i915_gem_init(), we need to actually unwind on the error path as we have > to abort the module load (and we expect to do so cleanly!). > > As we now teardown key state and then mark the driver

[Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915: Support creating a proxy object that links to other object's pages

== Series Details == Series: drm/i915: Support creating a proxy object that links to other object's pages URL : https://patchwork.freedesktop.org/series/35042/ State : warning == Summary == Test kms_setmode: Subgroup basic: fail -> PASS (shard-hsw)

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Drop fb reference on load_detect_pipe failure path

Quoting Patchwork (2017-12-07 22:20:31) > == Series Details == > > Series: drm/i915: Drop fb reference on load_detect_pipe failure path > URL : https://patchwork.freedesktop.org/series/35057/ > State : success > > == Summary == > > Series 35057v1 drm/i915: Drop fb reference on

[Intel-gfx] [CI 3/5] drm/i915: Include engine state on detecting a missed breadcrumb/seqno

Now that we have a common engine state pretty printer, we can use that instead of the adhoc information printed when we miss a breadcrumb. v2: Rearrange intel_engine_disarm_breadcrumbs() to avoid calling intel_engine_dump() under the rb spinlock (Mika) and to pretty-print the error state early so

[Intel-gfx] [CI 2/5] drm/i915: Make engine state pretty-printer header configurable

Pass in a format string (and args) to specify the header to be emitted along with the engine state when pretty-printing. This allows the header to be emitted inside the drm_printer stream, so sharing the same prefix and output characteristics (e.g. debug level and filtering). Signed-off-by: Chris

[Intel-gfx] [CI 5/5] drm/i915: Add is-wedged flag to intel_engine_dump()

Comparing the state tested by intel_engine_is_idle() and printed by intel_engine_dump(), the only bit not shown is whether or not the device is wedged. Add that little bit of information to the pretty printer so that if the engine fails to idle we can see why. Signed-off-by: Chris Wilson

[Intel-gfx] [CI 4/5] drm/i915: Include the global reset count for intel_engine_dump()

Since a global reset affects the engine, include that along side the per-engine reset counter when pretty printing the engine state in intel_engine_dump(). Signed-off-by: Chris Wilson Cc: Mika Kuoppala Reviewed-by: Mika Kuoppala

[Intel-gfx] [CI 1/5] drm/i915: Use snprintf to avoid line-break when pretty-printing engines

When printing the execlist ports, we first print the ELSP header then follow it with the pretty-printed request. Since switching to drm_printer and show the output via printk, it automatically appends a newline to each call (unlike the old seq_printf output). To avoid the unwanted line break,

[Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915/execlists: Cache ELSP register offset (rev2)

== Series Details == Series: drm/i915/execlists: Cache ELSP register offset (rev2) URL : https://patchwork.freedesktop.org/series/35054/ State : warning == Summary == Test kms_cursor_crc: Subgroup cursor-64x64-suspend: pass -> SKIP (shard-snb) fdo#102365

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Refactor common list iteration over GGTT vma

== Series Details == Series: drm/i915: Refactor common list iteration over GGTT vma URL : https://patchwork.freedesktop.org/series/35048/ State : failure == Summary == Test drv_suspend: Subgroup forcewake: pass -> SKIP (shard-snb) skip

Re: [Intel-gfx] [RFC i-g-t 3/5] lib/igt_hang_ctx: Use dummyload batch to hang ctx.

On 07/12/17 03:05, Chris Wilson wrote: Quoting Antonio Argenziano (2017-12-06 23:03:44) To hang a context we were effectively reimplementing a spinning batch and never stopping it. This patch reuses the recursive batch from igt_dummyload to hang a context. Cc: Chris Wilson

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/3] lib/igt_kms: Drop all stale events on first commit.

== Series Details == Series: series starting with [1/3] lib/igt_kms: Drop all stale events on first commit. URL : https://patchwork.freedesktop.org/series/35032/ State : failure == Summary == Test drv_suspend: Subgroup sysfs-reader-hibernate: fail -> SKIP

Re: [Intel-gfx] [PATCH v2] drm/i915/execlists: Cache ELSP register offset

Quoting Rodrigo Vivi (2017-12-07 23:04:13) > On Thu, Dec 07, 2017 at 10:24:34PM +, Chris Wilson wrote: > > Currently on every submission, we recalculate the ELSP register offset > > for the engine, after chasing the pointers to find the iomem base. Since > > this is fixed for the lifetime of

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/5] igt_dummyload: Wrap function parameters into struct

== Series Details == Series: series starting with [1/5] igt_dummyload: Wrap function parameters into struct URL : https://patchwork.freedesktop.org/series/35059/ State : success == Summary == IGT patchset tested on top of latest successful build 2fc64acf8a4465d5eab3d6cfec9b3c1b5df30d73

Re: [Intel-gfx] [PATCH igt] lib/i915: Update detection of GuC submission

Quoting Michal Wajdeczko (2017-12-07 23:30:54) > On Thu, 07 Dec 2017 22:02:59 +0100, Chris Wilson > wrote: > > > Recently the kernel has switched to using a combined i915.enable_guc > > rather than multiple i915.enable_guc_submission parameters. > > > > Signed-off-by:

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Unwind i915_gem_init() failure (rev2)

== Series Details == Series: drm/i915: Unwind i915_gem_init() failure (rev2) URL : https://patchwork.freedesktop.org/series/35060/ State : failure == Summary == Test kms_frontbuffer_tracking: Subgroup fbc-1p-offscren-pri-shrfb-draw-render: pass -> FAIL

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [CI,1/5] drm/i915: Use snprintf to avoid line-break when pretty-printing engines

== Series Details == Series: series starting with [CI,1/5] drm/i915: Use snprintf to avoid line-break when pretty-printing engines URL : https://patchwork.freedesktop.org/series/35066/ State : success == Summary == Test kms_frontbuffer_tracking: Subgroup

[Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915: Unwind i915_gem_init() failure

== Series Details == Series: drm/i915: Unwind i915_gem_init() failure URL : https://patchwork.freedesktop.org/series/35060/ State : warning == Summary == Test drv_module_reload: Subgroup basic-reload: pass -> DMESG-WARN (shard-snb) fdo#102848 Test kms_flip:

Re: [Intel-gfx] [PATCH] drm/i915: Increase max texture to 16k for gen9+

looks it's not that easy as I thought. This change is for https://bugs.freedesktop.org/show_bug.cgi?id=102508 , and the hardware configuration is * 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:591d] (rev 04) * Dell Thunderbolt BME dock :

Re: [Intel-gfx] [PATCH] kthread: finer-grained lockdep/cross-release completion

On Thu, Dec 07, 2017 at 08:57:09PM +0100, Peter Zijlstra wrote: > On Thu, Dec 07, 2017 at 03:58:28PM +0100, Daniel Vetter wrote: > > > [ 85.069417] gem_exec_captur/2810 is trying to acquire lock: > > [ 85.069419] ((completion)>parked){+.+.}, at: [] > > kthread_park+0x3d/0x50 > > [

Re: [Intel-gfx] [PATCH i-g-t v2] lib/igt_sysfs: Let igt_sysfs_read|write return -errno

On Thu, Dec 07, 2017 at 04:59:36PM +, Chris Wilson wrote: > Quoting Michal Wajdeczko (2017-12-07 16:52:46) > > In some cases debugfs or sysfs may return errors that we > > want to check. Return -errno from helper functions to make > > asserts easier. > > > > v2: don't forget about EOF ret=0

[Intel-gfx] [PATCH igt] lib/i915: Update detection of GuC submission

Recently the kernel has switched to using a combined i915.enable_guc rather than multiple i915.enable_guc_submission parameters. Signed-off-by: Chris Wilson Cc: Michal Wajdeczko --- lib/i915/gem_submission.c | 5 + 1 file changed, 5

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/execlists: Cache ELSP register offset

== Series Details == Series: drm/i915/execlists: Cache ELSP register offset URL : https://patchwork.freedesktop.org/series/35054/ State : success == Summary == Series 35054v1 drm/i915/execlists: Cache ELSP register offset

[Intel-gfx] [PATCH v2] drm/i915: Refactor common list iteration over GGTT vma

In quite a few places, we have a list iteration over the vma on an object that only want to inspect GGTT vma. By construction, these are placed at the start of the list, so we have copied that knowledge into many callsites. Pull that knowledge back to i915_vma.h and provide a for_each_ggtt_vma()

[Intel-gfx] [PATCH v3] drm/i915: Refactor common list iteration over GGTT vma

In quite a few places, we have a list iteration over the vma on an object that only want to inspect GGTT vma. By construction, these are placed at the start of the list, so we have copied that knowledge into many callsites. Pull that knowledge back to i915_vma.h and provide a for_each_ggtt_vma()

[Intel-gfx] ✓ Fi.CI.BAT: success for lib/i915: Update detection of GuC submission

== Series Details == Series: lib/i915: Update detection of GuC submission URL : https://patchwork.freedesktop.org/series/35055/ State : success == Summary == IGT patchset tested on top of latest successful build 2fc64acf8a4465d5eab3d6cfec9b3c1b5df30d73 igt/perf_pmu: Tweak wait_for_rc6, yet

Re: [Intel-gfx] [PATCH v4 6/9] drm/i915: Make use of indexed write GMBUS feature

On Wed, Dec 06, 2017 at 07:00:09PM -0500, Sean Paul wrote: > This patch enables the indexed write feature of the GMBUS to concatenate > 2 consecutive messages into one. The criteria for an indexed write is > that both messages are writes, the first is length == 1, and the second > is length > 0.

Re: [Intel-gfx] [PATCH] kthread: finer-grained lockdep/cross-release completion

On Thu, Dec 07, 2017 at 11:08:49AM +0100, Daniel Vetter wrote: > Since -rc1 we're hitting a bunch of lockdep splats using the new > cross-release stuff around the 2 kthread completions. In all cases > they are because totally independent uses of kthread are mixed up by > lockdep into the same

[Intel-gfx] [PATCH 0/9] make stolen resource centric

Continuation of Paulo' stolen series[1], addressing the feedback from Joonas and Chris. [1] https://patchwork.freedesktop.org/series/30923/ Joonas Lahtinen (1): x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit Matthew Auld (8): x86/early-quirks: replace the

[Intel-gfx] [PATCH 7/9] drm/i915: make mappable struct resource centric

Now that we are using struct resource to track the stolen region, it is more convenient if we track the mappable region in a resource as well. v2: prefer iomap and gmadr naming scheme prefer DEFINE_RES_MEM Signed-off-by: Matthew Auld Cc: Joonas Lahtinen

[Intel-gfx] [PATCH i-g-t 3/3] tests/kms_cursor_legacy: Rework the 2x-*-vs-cursor-* tests.

Using the fancy new DRM_CAP_CRTC_IN_VBLANK_EVENT cap I can finally make this test the work I originally intended to. For the !modeset case that means performing a pageflip on both crtc's, then requeueing as soon as the event is delivered and then check the vblank counter against the original

[Intel-gfx] [PATCH i-g-t] tests/kms_color: Rename pipe tests to standard notation

Signed-off-by: Maarten Lankhorst --- tests/kms_color.c | 26 +- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/tests/kms_color.c b/tests/kms_color.c index dcda12de3a39..3b0a88802c93 100644 --- a/tests/kms_color.c +++

[Intel-gfx] [PATCH i-g-t 3/6] meson: Install benchmarks to $libexec/intel-gpu-tools/benchmarks

Signed-off-by: Petri Latvala Cc: Daniel Vetter --- benchmarks/meson.build | 4 1 file changed, 4 insertions(+) diff --git a/benchmarks/meson.build b/benchmarks/meson.build index 4afd204f..26d65c4b 100644 --- a/benchmarks/meson.build +++

[Intel-gfx] [PATCH i-g-t 1/3] lib/igt_kms: Drop all stale events on first commit.

I've been trying to make kms_cursor_legacy work when subtests fail. Other subtests will start failing too because of expired events or stale pipe crc. The latter can be resolved in the test, but the former could affect other tests Signed-off-by: Maarten Lankhorst

[Intel-gfx] [PATCH i-g-t 2/3] tests/kms_cursor_legacy: Perform lazy cleanup between tests

Instead of assuming each subtest cleans up after itself, assume it fails and doesn't. Now that igt_kms can clean up stale events, we can just force each subtest to only clean up its framebuffers, which isn't harmful if it failed. Signed-off-by: Maarten Lankhorst

[Intel-gfx] [PATCH i-g-t 6/6] meson: Install .testlist files

Signed-off-by: Petri Latvala Cc: Daniel Vetter --- tests/intel-ci/meson.build | 7 +++ tests/meson.build | 2 ++ 2 files changed, 9 insertions(+) create mode 100644 tests/intel-ci/meson.build diff --git a/tests/intel-ci/meson.build

[Intel-gfx] [PATCH i-g-t 1/6] meson: Don't install headers

Until we can at least check for a matching ABI, the only supported way of building is having the headers from the source checkout. Signed-off-by: Petri Latvala Cc: Daniel Vetter --- lib/meson.build | 2 -- 1 file changed, 2 deletions(-) diff

[Intel-gfx] [PATCH i-g-t 5/6] meson: Also install gem_stress.

Signed-off-by: Petri Latvala Cc: Daniel Vetter --- tests/meson.build | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tests/meson.build b/tests/meson.build index 45517a59..1d1cbe3a 100644 --- a/tests/meson.build +++

[Intel-gfx] [PATCH i-g-t 4/6] meson: Install test-list.txt to libexecdir

Piglit needs test-list.txt to be in the same directory as the test binaries. Signed-off-by: Petri Latvala Cc: Daniel Vetter --- tests/meson.build | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/meson.build

[Intel-gfx] [PATCH i-g-t 2/6] meson: Don't install selfcheck binaries

Signed-off-by: Petri Latvala Cc: Daniel Vetter --- lib/tests/meson.build | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/tests/meson.build b/lib/tests/meson.build index 29bdb2c4..55ab2b3d 100644 ---

Re: [Intel-gfx] [PATCH] drm/i915: Call intel_opregion_notify_encoder in intel_sanitize_encoder

On Wed, Dec 06, 2017 at 09:52:51AM +0100, Maarten Lankhorst wrote: > Op 01-12-17 om 14:32 schreef Ville Syrjälä: > > On Thu, Nov 30, 2017 at 04:18:53PM +0100, Maarten Lankhorst wrote: > >> Normally this is called on a modeset, but the call is missing when > >> we inherit the mode from the BIOS, so

[Intel-gfx] [PATCH] drm/i915: add FTRACE dependency for DRM_I915_TRACE_GEM

The new trace option gratuitously added a 'select TRACING' statement, which now causes build failures in other code that assumed tracepoints were only available with FTRACE: ERROR: "__tracepoint_ucsi_command" [drivers/usb/typec/ucsi/typec_ucsi.ko] undefined! ERROR:

Re: [Intel-gfx] [PATCH v3 04/11] drm/exynos: Use drm_fb_helper_lastclose() and _poll_changed()

Den 07.12.2017 01.50, skrev Inki Dae: 2017년 12월 06일 03:24에 Noralf Trønnes 이(가) 쓴 글: This driver can use drm_fb_helper_lastclose() as its .lastclose callback. It can also use drm_fb_helper_output_poll_changed() as its .output_poll_changed callback. Cc: Inki Dae Cc:

Re: [Intel-gfx] [PATCH] drm/i915: Increase max texture to 16k for gen9+

On Thu, Dec 07, 2017 at 05:26:00PM +0800, Alex Tu wrote: > Rrefer to another patch [1] on mesa to extend width/height to 16384. > For issue : > - https://bugs.freedesktop.org/show_bug.cgi?id=102508 > - LP: #1714178 Triple monitor display failed with Dell Dock (HiDPI) > > [1]

Re: [Intel-gfx] [PATCH] drm: More debug info for fb leaks in mode_config_cleanup

Den 07.12.2017 15.49, skrev Daniel Vetter: We're spotting this very rarely in CI, but have no idea. Let's add more debug info about what's going on here. References: https://bugs.freedesktop.org/show_bug.cgi?id=102707 Signed-off-by: Daniel Vetter --- Acked-by:

Re: [Intel-gfx] [RFC PATCH 1/6] drm: Add Content Protection property

> If you want to actually lock down a machine to implement content > protection, then you need secure boot without unlockable boot-loader and a > pile more bits in userspace. So let me take my Intel hat off for a moment. The upstream policy has always been that we don't merge things which don't

Re: [Intel-gfx] [RFC PATCH 1/6] drm: Add Content Protection property

> How about for sensitive video streams in government offices where you > want to avoid a spy potentially tapping the cable to see the video > stream? Last time I checked HDCP did not meet government security requirements - which is hardly surprising since you can buy $10 boxes from China to

Re: [Intel-gfx] [PATCH] intel/atomic: Stop updating legacy fb parameters

Op 07-12-17 om 15:32 schreef Daniel Vetter: > Even fbc isn't using this stuff anymore, so time to remove it. > > Cleaning up one small piece of the atomic conversion cruft at the time > ... > > Quick explanation on why the plane->fb assignment is ok to delete: The > core code takes care of the

Re: [Intel-gfx] [PATCH i-g-t 1/3] lib/igt_kms: Drop all stale events on first commit.

Quoting Maarten Lankhorst (2017-12-07 13:40:25) > I've been trying to make kms_cursor_legacy work when subtests fail. > Other subtests will start failing too because of expired events or > stale pipe crc. The latter can be resolved in the test, but the former > could affect other tests > >

[Intel-gfx] [PULL] drm-misc-fixes

Hi Dave, drm-misc-fixes-2017-12-07: regression fix for vc4 + rpm stable fix for analogix bridge Of course I do a pull, 2 more patches show up. Flushed them out since you'll be out next week. Cheers, Daniel The following changes since commit a703c55004e1c5076d57e43771b3e7796ea0: drm:

Re: [Intel-gfx] [PATCH i-g-t 1/3] lib/igt_kms: Drop all stale events on first commit.

Op 07-12-17 om 16:03 schreef Chris Wilson: > Quoting Maarten Lankhorst (2017-12-07 13:40:25) >> I've been trying to make kms_cursor_legacy work when subtests fail. >> Other subtests will start failing too because of expired events or >> stale pipe crc. The latter can be resolved in the test, but

[Intel-gfx] [PATCH] intel/atomic: Stop updating legacy fb parameters

Even fbc isn't using this stuff anymore, so time to remove it. Cleaning up one small piece of the atomic conversion cruft at the time ... Quick explanation on why the plane->fb assignment is ok to delete: The core code takes care of the refcounting and legacy ->fb pointer updating, but drivers

[Intel-gfx] [PATCH] drm: More debug info for fb leaks in mode_config_cleanup

We're spotting this very rarely in CI, but have no idea. Let's add more debug info about what's going on here. References: https://bugs.freedesktop.org/show_bug.cgi?id=102707 Signed-off-by: Daniel Vetter --- drivers/gpu/drm/drm_mode_config.c | 3 +++ 1 file changed, 3

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: add FTRACE dependency for DRM_I915_TRACE_GEM

== Series Details == Series: drm/i915: add FTRACE dependency for DRM_I915_TRACE_GEM URL : https://patchwork.freedesktop.org/series/35035/ State : success == Summary == Series 35035v1 drm/i915: add FTRACE dependency for DRM_I915_TRACE_GEM

  1   2   >