[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Allow user to override PWM backlight frequency and duty cycle (rev2)

== Series Details == Series: drm/i915: Allow user to override PWM backlight frequency and duty cycle (rev2) URL : https://patchwork.freedesktop.org/series/36540/ State : success == Summary == Series 36540v2 drm/i915: Allow user to override PWM backlight frequency and duty cycle

[Intel-gfx] [PATCH] drm/i915: Allow user to override PWM backlight frequency and duty cycle

Fixed to merge against drm-tip branch Signed-off-by: Alex Ivanov --- drivers/gpu/drm/i915/i915_params.c | 6 ++ drivers/gpu/drm/i915/i915_params.h | 2 ++ drivers/gpu/drm/i915/intel_panel.c | 17 + 3 files changed, 25 insertions(+) diff --git

Re: [Intel-gfx] [PATCH i-g-t v13] tests/kms_frontbuffer_tracking: Including DRRS test coverage

Summary from IRC discussions with Rodrigo: drrs_disable will get called on all test setups(including the drrs non-capable). So we cant fail/skip the sub_test based on the return value from drrs_set(0) drrs_enable will get called only when the test setup is capable of drrs. And also after

[Intel-gfx] [PULL] gvt-next fixes for 4.16

Hi, Here's queued gvt-next fixes for 4.16-rc1. Mostly with regression fixes on vGPU display dmabuf, mmio switch and other misc changes, details below. thanks -- The following changes since commit 4fafba2d73fcaf1b433c26e753a98ad4b231754a: drm/i915/gvt: move write protect handler out of mmio

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/guc: Don't enable GuC when vGPU is active

On Tue, Jan 16, 2018 at 11:17:39AM +0100, Michal Wajdeczko wrote: > On Tue, 16 Jan 2018 10:53:47 +0100, Joonas Lahtinen > wrote: > > > On Mon, 2018-01-15 at 13:10 +0200, Tomi Sarvela wrote: > > > On 15/01/18 12:28, Zhenyu Wang wrote: > > > > On 2018.01.15

[Intel-gfx] ✓ Fi.CI.IGT: success for tests/gem_reset_stats: Fix retrieval of hangcheck stats expectation (rev3)

== Series Details == Series: tests/gem_reset_stats: Fix retrieval of hangcheck stats expectation (rev3) URL : https://patchwork.freedesktop.org/series/35101/ State : success == Summary == Test gem_tiled_swapping: Subgroup non-threaded: incomplete -> PASS

[Intel-gfx] ✓ Fi.CI.IGT: success for igt/kms_frontbuffer_tracking: Show FBC status at the start of the wait (rev5)

== Series Details == Series: igt/kms_frontbuffer_tracking: Show FBC status at the start of the wait (rev5) URL : https://patchwork.freedesktop.org/series/35699/ State : success == Summary == Test perf: Subgroup polling: fail -> PASS (shard-hsw) fdo#102252

Re: [Intel-gfx] [PATCH] drm/i915: Do not WARN_ON with small framebuffers.

On Tue, Jan 16, 2018 at 03:53:31PM +, Maarten Lankhorst wrote: > It's perfectly legal to create a fb with stride < 512, and one of > the kms_plane_scaling subtests creates a very small fb. > > Downgrade the WARN_ON to a simple check check, and because this > function is potentially called on

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: expose RCS topology to userspace

== Series Details == Series: drm/i915: expose RCS topology to userspace URL : https://patchwork.freedesktop.org/series/36567/ State : success == Summary == Test kms_flip: Subgroup flip-vs-fences-interruptible: dmesg-warn -> PASS (shard-hsw) fdo#102614 Test

Re: [Intel-gfx] [PATCH v7 6/6] drm/i915: expose rcs topology through query uAPI

Quoting Lionel Landwerlin (2018-01-16 19:18:24) > diff --git a/drivers/gpu/drm/i915/i915_query.c > b/drivers/gpu/drm/i915/i915_query.c > index 51736af7f573..038f292e1f2a 100644 > --- a/drivers/gpu/drm/i915/i915_query.c > +++ b/drivers/gpu/drm/i915/i915_query.c > @@ -25,8 +25,102 @@ > #include

Re: [Intel-gfx] [PATCH i-g-t v3] tests/gem_reset_stats: Fix retrieval of hangcheck stats expectation

On 1/16/2018 12:56 PM, Antonio Argenziano wrote: The test expected IOCTL 'I915_GET_RESET_STATS' would return an error when not root. That is no longer true in the driver since commit 4c9c0d09741d ("drm/i915: Fix retrieval of hangcheck stats") and therefore the test was incorrectly failing. v2:

[Intel-gfx] ✓ Fi.CI.BAT: success for tests/gem_reset_stats: Fix retrieval of hangcheck stats expectation (rev3)

== Series Details == Series: tests/gem_reset_stats: Fix retrieval of hangcheck stats expectation (rev3) URL : https://patchwork.freedesktop.org/series/35101/ State : success == Summary == IGT patchset tested on top of latest successful build 5f5b4a65e672bd10a4422cc1cb3c466659c52db8

Re: [Intel-gfx] [PATCH i-g-t 2/2] tests: add i915 query tests

Quoting Chris Wilson (2018-01-16 21:34:34) > Quoting Lionel Landwerlin (2018-01-16 16:07:28) > > Signed-off-by: Lionel Landwerlin > > --- > > tests/Makefile.sources | 1 + > > tests/meson.build | 1 + > > tests/query.c | 268 > >

Re: [Intel-gfx] [PATCH i-g-t 2/2] tests: add i915 query tests

Quoting Lionel Landwerlin (2018-01-16 16:07:28) > Signed-off-by: Lionel Landwerlin > --- > tests/Makefile.sources | 1 + > tests/meson.build | 1 + > tests/query.c | 268 > + > 3 files changed, 270

Re: [Intel-gfx] [PATCH 1/5] drm/vblank: Fix return type for drm_vblank_count()

On Mon, 2018-01-15 at 10:38 +0100, Daniel Vetter wrote: > On Fri, Jan 12, 2018 at 01:57:03PM -0800, Dhinakaran Pandiyan wrote: > > drm_vblank_count() has a u32 type returning what is a 64-bit vblank count. > > The effect of this is when drm_wait_vblank_ioctl() tries to widen the user > > space

[Intel-gfx] ✓ Fi.CI.BAT: success for igt/kms_frontbuffer_tracking: Show FBC status at the start of the wait (rev5)

== Series Details == Series: igt/kms_frontbuffer_tracking: Show FBC status at the start of the wait (rev5) URL : https://patchwork.freedesktop.org/series/35699/ State : success == Summary == IGT patchset tested on top of latest successful build 5f5b4a65e672bd10a4422cc1cb3c466659c52db8

[Intel-gfx] ✗ Fi.CI.IGT: warning for series starting with [1/2] include: bump drm uAPI headers

== Series Details == Series: series starting with [1/2] include: bump drm uAPI headers URL : https://patchwork.freedesktop.org/series/36561/ State : warning == Summary == Test kms_frontbuffer_tracking: Subgroup fbc-1p-offscren-pri-shrfb-draw-render: fail -> PASS

[Intel-gfx] [PATCH i-g-t v3] tests/gem_reset_stats: Fix retrieval of hangcheck stats expectation

The test expected IOCTL 'I915_GET_RESET_STATS' would return an error when not root. That is no longer true in the driver since commit 4c9c0d09741d ("drm/i915: Fix retrieval of hangcheck stats") and therefore the test was incorrectly failing. v2: - Add the commit that changed the behaviour

[Intel-gfx] [PATCH igt] igt/kms_frontbuffer_tracking: Show FBC status at the start of the wait

Signed-off-by: Chris Wilson --- tests/kms_frontbuffer_tracking.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/tests/kms_frontbuffer_tracking.c b/tests/kms_frontbuffer_tracking.c index 1601cab45..f35e40593 100644 ---

[Intel-gfx] ✓ Fi.CI.IGT: success for igt/kms_frontbuffer_tracking: Show FBC status at the start of the wait (rev4)

== Series Details == Series: igt/kms_frontbuffer_tracking: Show FBC status at the start of the wait (rev4) URL : https://patchwork.freedesktop.org/series/35699/ State : success == Summary == Test kms_flip: Subgroup flip-vs-fences-interruptible: dmesg-warn -> PASS

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/5] igt/gem_ctx_isolation: Check isolation of registers between contexts

== Series Details == Series: series starting with [1/5] igt/gem_ctx_isolation: Check isolation of registers between contexts URL : https://patchwork.freedesktop.org/series/36548/ State : failure == Summary == Test perf: Subgroup polling: fail -> PASS

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: expose RCS topology to userspace

== Series Details == Series: drm/i915: expose RCS topology to userspace URL : https://patchwork.freedesktop.org/series/36567/ State : success == Summary == Series 36567v1 drm/i915: expose RCS topology to userspace https://patchwork.freedesktop.org/api/1.0/series/36567/revisions/1/mbox/ Test

Re: [Intel-gfx] [PATCH 4/5] drm/i915: Introduce a non-blocking power domain for vblank interrupts

On Tue, 2018-01-09 at 10:38 +0100, Maarten Lankhorst wrote: > Op 08-01-18 om 20:59 schreef Pandiyan, Dhinakaran: > > On Thu, 2018-01-04 at 18:08 -0800, Rodrigo Vivi wrote: > >> I will probably have more comments later, but just doing a brain dump now > >> since I end up forgetting to write

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Allow user to override PWM backlight frequency and duty cycle

HI, > -Original Message- > From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of > gnido...@ya.ru > Sent: tiistai 16. tammikuuta 2018 17.36 > To: intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Allow user to > override

Re: [Intel-gfx] [PATCH v6 6/6] drm/i915: expose rcs topology through query uAPI

On 16/01/18 17:40, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-01-16 16:22:52) On 16/01/2018 16:02, Lionel Landwerlin wrote: diff --git a/drivers/gpu/drm/i915/i915_query.c b/drivers/gpu/drm/i915/i915_query.c index 6468ca613d27..81367c8224ee 100644 --- a/drivers/gpu/drm/i915/i915_query.c

[Intel-gfx] [PATCH v7 5/6] drm/i915: add query uAPI

There are a number of information that are readable from hardware registers and that we would like to make accessible to userspace. One particular example is the topology of the execution units (how are execution units grouped in subslices and slices and also which ones have been fused off for die

[Intel-gfx] [PATCH v7 6/6] drm/i915: expose rcs topology through query uAPI

With the introduction of asymmetric slices in CNL, we cannot rely on the previous SUBSLICE_MASK getparam to tell userspace what subslices are available. Here we introduce a more detailed way of querying the Gen's GPU topology that doesn't aggregate numbers. This is essential for monitoring parts

[Intel-gfx] [PATCH v7 2/6] drm/i915/debugfs: reuse max slice/subslices already stored in sseu

Now that we have that information in topology fields, let's just reused it. v2: Style tweaks (Tvrtko) Signed-off-by: Lionel Landwerlin Reviewed-by: Tvrtko Ursulin --- drivers/gpu/drm/i915/i915_debugfs.c | 27 +++

[Intel-gfx] [PATCH v7 4/6] drm/i915: add rcs topology to error state

This might be useful information for developers looking at an error state. v2: Place topology towards the end of the error state (Chris) v3: Reuse common printing code (Michal) v4: Make this a one-liner (Chris) Signed-off-by: Lionel Landwerlin Reviewed-by:

[Intel-gfx] [PATCH v7 3/6] drm/i915/debugfs: add rcs topology entry

While the end goal is to make this information available to userspace through a new ioctl, there is no reason we can't display it in a human readable fashion through debugfs. slice0: 3 subslice(s) (0x7): subslice0: 8 EUs (0xff) subslice1: 8 EUs (0xff) subslice2: 8 EUs

[Intel-gfx] [PATCH v7 0/6] drm/i915: expose RCS topology to userspace

A few tweaks following comments from Chris. Cheers, Lionel Landwerlin (6): drm/i915: store all subslice masks drm/i915/debugfs: reuse max slice/subslices already stored in sseu drm/i915/debugfs: add rcs topology entry drm/i915: add rcs topology to error state drm/i915: add query uAPI

[Intel-gfx] [PATCH v7 1/6] drm/i915: store all subslice masks

Up to now, subslice mask was assumed to be uniform across slices. But starting with Cannonlake, slices can be asymmetric (for example slice0 has different number of subslices as slice1+). This change stores all subslices masks for all slices rather than having a single mask that applies to all

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/reset_stats: Only allow root to read reset_stats

== Series Details == Series: drm/i915/reset_stats: Only allow root to read reset_stats URL : https://patchwork.freedesktop.org/series/36562/ State : success == Summary == Test kms_flip: Subgroup vblank-vs-modeset-suspend-interruptible: pass -> SKIP

Re: [Intel-gfx] [PATCH i-g-t v2] tests/gem_reset_stats: Fix retrieval of hangcheck stats expectation

On 1/16/2018 10:44 AM, Antonio Argenziano wrote: On 13/12/17 16:48, Antonio Argenziano wrote: The test expected IOCTL 'I915_GET_RESET_STATS' would return an error when not root. That is no longer true in the driver since commit 4c9c0d09741d ("drm/i915: Fix retrieval of hangcheck stats") and

Re: [Intel-gfx] [PATCH i-g-t v2] tests/gem_reset_stats: Fix retrieval of hangcheck stats expectation

On 13/12/17 16:48, Antonio Argenziano wrote: The test expected IOCTL 'I915_GET_RESET_STATS' would return an error when not root. That is no longer true in the driver since commit 4c9c0d09741d ("drm/i915: Fix retrieval of hangcheck stats") and therefore the test was incorrectly failing. v2:

[Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915: expose RCS topology to userspace

== Series Details == Series: drm/i915: expose RCS topology to userspace URL : https://patchwork.freedesktop.org/series/36560/ State : warning == Summary == Test perf: Subgroup polling: fail -> PASS (shard-hsw) fdo#102252 Test kms_flip: Subgroup

Re: [Intel-gfx] [PATCH] drm/i915/reset_stats: Only allow root to read reset_stats

On 16/01/18 09:27, Chris Wilson wrote: Quoting Antonio Argenziano (2018-01-16 16:09:35) Instead of returning a zero value for non root users, return an EPERM error. What? reset-stats are per-context, private to the client, with the exception of the global value which is solely protected by

Re: [Intel-gfx] [PATCH v2] drm/i915: Use the engine name directly in the error_state file

On 1/15/2018 9:15 AM, Tvrtko Ursulin wrote: On 10/01/2018 01:21, Michel Thierry wrote: Instead of using local string names that we will have to keep maintaining, use the engine->name directly. v2: Better invalid engine_id handling, capture_bo will not be able know the engine_id and end up

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] include: bump drm uAPI headers

== Series Details == Series: series starting with [1/2] include: bump drm uAPI headers URL : https://patchwork.freedesktop.org/series/36561/ State : success == Summary == IGT patchset tested on top of latest successful build 5f5b4a65e672bd10a4422cc1cb3c466659c52db8 igt/gem_linear_blits:

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Do not WARN_ON with small framebuffers.

== Series Details == Series: drm/i915: Do not WARN_ON with small framebuffers. URL : https://patchwork.freedesktop.org/series/36558/ State : success == Summary == Test kms_flip: Subgroup vblank-vs-modeset-suspend: pass -> SKIP (shard-snb) fdo#102365

[Intel-gfx] ✓ Fi.CI.BAT: success for igt/kms_frontbuffer_tracking: Show FBC status at the start of the wait (rev4)

== Series Details == Series: igt/kms_frontbuffer_tracking: Show FBC status at the start of the wait (rev4) URL : https://patchwork.freedesktop.org/series/35699/ State : success == Summary == IGT patchset tested on top of latest successful build 5f5b4a65e672bd10a4422cc1cb3c466659c52db8

Re: [Intel-gfx] [PATCH] drm/i915: Always call to intel_display_set_init_power() in resume_early.

Op 16-01-18 om 17:44 schreef Imre Deak: > On Tue, Jan 16, 2018 at 04:53:24PM +0100, Maarten Lankhorst wrote: >> intel_power_domains_init_hw() calls set_init_power, but when using >> runtime power management this call is skipped. > It's skipped during suspend-to-idle. > >> This prevents hw readout

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Always call to intel_display_set_init_power() in resume_early.

== Series Details == Series: drm/i915: Always call to intel_display_set_init_power() in resume_early. URL : https://patchwork.freedesktop.org/series/36557/ State : success == Summary == Test kms_cursor_crc: Subgroup cursor-128x128-suspend: pass -> SKIP

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/5] igt/gem_ctx_isolation: Check isolation of registers between contexts

== Series Details == Series: series starting with [1/5] igt/gem_ctx_isolation: Check isolation of registers between contexts URL : https://patchwork.freedesktop.org/series/36548/ State : success == Summary == IGT patchset tested on top of latest successful build

Re: [Intel-gfx] [PATCH v6 6/6] drm/i915: expose rcs topology through query uAPI

Quoting Tvrtko Ursulin (2018-01-16 16:22:52) > > On 16/01/2018 16:02, Lionel Landwerlin wrote: > > diff --git a/drivers/gpu/drm/i915/i915_query.c > > b/drivers/gpu/drm/i915/i915_query.c > > index 6468ca613d27..81367c8224ee 100644 > > --- a/drivers/gpu/drm/i915/i915_query.c > > +++

Re: [Intel-gfx] [PATCH v2] drm/i915: Shrink the GEM kmem_caches upon idling

Quoting Tvrtko Ursulin (2018-01-16 17:25:25) > > On 16/01/2018 15:21, Chris Wilson wrote: > > Quoting Tvrtko Ursulin (2018-01-16 15:12:43) > >> > >> On 16/01/2018 13:05, Chris Wilson wrote: > >>> When we finally decide the gpu is idle, that is a good time to shrink > >>> our kmem_caches. > >>> >

Re: [Intel-gfx] [PATCH] drm/i915/reset_stats: Only allow root to read reset_stats

Quoting Antonio Argenziano (2018-01-16 16:09:35) > Instead of returning a zero value for non root users, return an EPERM > error. What? reset-stats are per-context, private to the client, with the exception of the global value which is solely protected by capable(). There is a genuine debate over

Re: [Intel-gfx] [PATCH v2] drm/i915: Shrink the GEM kmem_caches upon idling

On 16/01/2018 15:21, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-01-16 15:12:43) On 16/01/2018 13:05, Chris Wilson wrote: When we finally decide the gpu is idle, that is a good time to shrink our kmem_caches. v2: Comment upon the random sprinkling of rcu_barrier() inside the idle

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/reset_stats: Only allow root to read reset_stats

== Series Details == Series: drm/i915/reset_stats: Only allow root to read reset_stats URL : https://patchwork.freedesktop.org/series/36562/ State : success == Summary == Series 36562v1 drm/i915/reset_stats: Only allow root to read reset_stats

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: expose RCS topology to userspace

== Series Details == Series: drm/i915: expose RCS topology to userspace URL : https://patchwork.freedesktop.org/series/36560/ State : success == Summary == Series 36560v1 drm/i915: expose RCS topology to userspace https://patchwork.freedesktop.org/api/1.0/series/36560/revisions/1/mbox/ Test

Re: [Intel-gfx] [PATCH] drm/i915: Always call to intel_display_set_init_power() in resume_early.

On Tue, Jan 16, 2018 at 04:53:24PM +0100, Maarten Lankhorst wrote: > intel_power_domains_init_hw() calls set_init_power, but when using > runtime power management this call is skipped. It's skipped during suspend-to-idle. > This prevents hw readout from taking place. > > Signed-off-by: Maarten

[Intel-gfx] ✗ Fi.CI.IGT: warning for kms_plane_scaling tests. (rev3)

== Series Details == Series: kms_plane_scaling tests. (rev3) URL : https://patchwork.freedesktop.org/series/36485/ State : warning == Summary == Test kms_flip: Subgroup flip-vs-fences-interruptible: dmesg-warn -> PASS (shard-hsw) fdo#102614 Subgroup

Re: [Intel-gfx] [PATCH] [v2] drm/i915: use static const array for PICK macro

On Mon, Dec 11, 2017 at 7:40 PM, Chris Wilson wrote: > Quoting Chris Wilson (2017-12-11 12:51:42) >> Quoting Arnd Bergmann (2017-12-11 12:46:22) >> > v2: rebased after a1986f4174a4 ("drm/i915: Remove unnecessary PORT3 >> > definition.") >> > --- >> >

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Do not WARN_ON with small framebuffers.

== Series Details == Series: drm/i915: Do not WARN_ON with small framebuffers. URL : https://patchwork.freedesktop.org/series/36558/ State : success == Summary == Series 36558v1 drm/i915: Do not WARN_ON with small framebuffers.

[Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915: expose RCS topology to userspace

== Series Details == Series: drm/i915: expose RCS topology to userspace URL : https://patchwork.freedesktop.org/series/36539/ State : warning == Summary == Test gem_tiled_swapping: Subgroup non-threaded: incomplete -> PASS (shard-snb) fdo#104218 Test perf:

Re: [Intel-gfx] [PATCH i-g-t 3/3] debugger: No longer rely on compatability define in intel_bufmgr.h

On 18-01-09 23:25:11, Rhys Kidd wrote: Symbol rename from dri_* to drm_intel_* introduced a number of compatability defines within intel_bufmgr.h. Replace the old function with the new function, consistent with the balance of this file. Signed-off-by: Rhys Kidd ---

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Always call to intel_display_set_init_power() in resume_early.

== Series Details == Series: drm/i915: Always call to intel_display_set_init_power() in resume_early. URL : https://patchwork.freedesktop.org/series/36557/ State : success == Summary == Series 36557v1 drm/i915: Always call to intel_display_set_init_power() in resume_early.

Re: [Intel-gfx] [PATCH v6 6/6] drm/i915: expose rcs topology through query uAPI

On 16/01/2018 16:02, Lionel Landwerlin wrote: With the introduction of asymmetric slices in CNL, we cannot rely on the previous SUBSLICE_MASK getparam to tell userspace what subslices are available. Here we introduce a more detailed way of querying the Gen's GPU topology that doesn't aggregate

[Intel-gfx] [PATCH] drm/i915/reset_stats: Only allow root to read reset_stats

Instead of returning a zero value for non root users, return an EPERM error. Signed-off-by: Antonio Argenziano Cc: Chris Wilson Cc: Michel Thierry --- drivers/gpu/drm/i915/i915_drv.c | 2 +-

[Intel-gfx] [PATCH i-g-t 2/2] tests: add i915 query tests

Signed-off-by: Lionel Landwerlin --- tests/Makefile.sources | 1 + tests/meson.build | 1 + tests/query.c | 268 + 3 files changed, 270 insertions(+) create mode 100644 tests/query.c diff --git

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

Signed-off-by: Lionel Landwerlin --- include/drm-uapi/i915_drm.h | 126 lib/igt_perf.h | 7 --- 2 files changed, 126 insertions(+), 7 deletions(-) diff --git a/include/drm-uapi/i915_drm.h

[Intel-gfx] ✗ Fi.CI.BAT: warning for drm/i915/vlv: Ramp up gpu freq gradually

== Series Details == Series: drm/i915/vlv: Ramp up gpu freq gradually URL : https://patchwork.freedesktop.org/series/36550/ State : warning == Summary == Series 36550v1 drm/i915/vlv: Ramp up gpu freq gradually https://patchwork.freedesktop.org/api/1.0/series/36550/revisions/1/mbox/ Test

[Intel-gfx] [PATCH v6 4/6] drm/i915: add rcs topology to error state

This might be useful information for developers looking at an error state. v2: Place topology towards the end of the error state (Chris) v3: Reuse common printing code (Michal) v4: Make this a one-liner (Chris) Signed-off-by: Lionel Landwerlin Reviewed-by:

[Intel-gfx] [PATCH v6 0/6] drm/i915: expose RCS topology to userspace

Hi again, A few more changes following Chris' comments. Cheers, Lionel Landwerlin (6): drm/i915: store all subslice masks drm/i915/debugfs: reuse max slice/subslices already stored in sseu drm/i915/debugfs: add rcs topology entry drm/i915: add rcs topology to error state drm/i915: add

[Intel-gfx] [PATCH v6 3/6] drm/i915/debugfs: add rcs topology entry

While the end goal is to make this information available to userspace through a new ioctl, there is no reason we can't display it in a human readable fashion through debugfs. slice0: 3 subslice(s) (0x7): subslice0: 8 EUs (0xff) subslice1: 8 EUs (0xff) subslice2: 8 EUs

[Intel-gfx] [PATCH v6 2/6] drm/i915/debugfs: reuse max slice/subslices already stored in sseu

Now that we have that information in topology fields, let's just reused it. v2: Style tweaks (Tvrtko) Signed-off-by: Lionel Landwerlin Reviewed-by: Tvrtko Ursulin --- drivers/gpu/drm/i915/i915_debugfs.c | 27 +++

[Intel-gfx] [PATCH v6 6/6] drm/i915: expose rcs topology through query uAPI

With the introduction of asymmetric slices in CNL, we cannot rely on the previous SUBSLICE_MASK getparam to tell userspace what subslices are available. Here we introduce a more detailed way of querying the Gen's GPU topology that doesn't aggregate numbers. This is essential for monitoring parts

[Intel-gfx] [PATCH v6 1/6] drm/i915: store all subslice masks

Up to now, subslice mask was assumed to be uniform across slices. But starting with Cannonlake, slices can be asymmetric (for example slice0 has different number of subslices as slice1+). This change stores all subslices masks for all slices rather than having a single mask that applies to all

[Intel-gfx] [PATCH v6 5/6] drm/i915: add query uAPI

There are a number of information that are readable from hardware registers and that we would like to make accessible to userspace. One particular example is the topology of the execution units (how are execution units grouped in subslices and slices and also which ones have been fused off for die

[Intel-gfx] [PATCH] drm/i915: Do not WARN_ON with small framebuffers.

It's perfectly legal to create a fb with stride < 512, and one of the kms_plane_scaling subtests creates a very small fb. Downgrade the WARN_ON to a simple check check, and because this function is potentially called on every atomic update/pageflip, downgrade the other WARN_ON to a WARN_ON_ONCE,

[Intel-gfx] [PATCH] drm/i915: Always call to intel_display_set_init_power() in resume_early.

intel_power_domains_init_hw() calls set_init_power, but when using runtime power management this call is skipped. This prevents hw readout from taking place. Signed-off-by: Maarten Lankhorst Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104172 Cc:

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Allow user to override PWM backlight frequency and duty cycle

What branch CI tests against? I've created the patch against current torvalds/linux 16.01.2018, 17:42, "Patchwork" : > == Series Details == > > Series: drm/i915: Allow user to override PWM backlight frequency and duty > cycle > URL :

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [01/10] drm/i915: Only attempt to scan the requested number of shrinker slabs (rev4)

== Series Details == Series: series starting with [01/10] drm/i915: Only attempt to scan the requested number of shrinker slabs (rev4) URL : https://patchwork.freedesktop.org/series/36501/ State : success == Summary == Test kms_flip: Subgroup flip-vs-fences-interruptible:

Re: [Intel-gfx] [PATCH v2 01/11] drm/i915: Disable preemption and sleeping while using the punit sideband

Chris Wilson writes: > Quoting Mika Kuoppala (2018-01-15 12:04:40) >> Chris Wilson writes: >> >> > While we talk to the punit over its sideband, we need to prevent the cpu >> > from sleeping in order to prevent a potential machine hang. >> >

Re: [Intel-gfx] [PATCH RFC] drm/i915/vlv: Ramp up gpu freq gradually

Quoting Mika Kuoppala (2018-01-16 15:21:16) > There is a suspicion that with aggressive upclocking, power rail > voltage fluctuations can disrupt c state transition, leading > to system hang. > > When upclocking with 4 cpu Baytrails, bring up cpus to c1 and then > go through bins gradually

Re: [Intel-gfx] [PATCH v2] drm/i915: Shrink the GEM kmem_caches upon idling

Quoting Tvrtko Ursulin (2018-01-16 15:12:43) > > On 16/01/2018 13:05, Chris Wilson wrote: > > When we finally decide the gpu is idle, that is a good time to shrink > > our kmem_caches. > > > > v2: Comment upon the random sprinkling of rcu_barrier() inside the idle > > worker. > > > >

[Intel-gfx] [PATCH RFC] drm/i915/vlv: Ramp up gpu freq gradually

There is a suspicion that with aggressive upclocking, power rail voltage fluctuations can disrupt c state transition, leading to system hang. When upclocking with 4 cpu Baytrails, bring up cpus to c1 and then go through bins gradually towards target frequency to give leeway for hw. We go towards

Re: [Intel-gfx] [PATCH v2] drm/i915: Shrink the request kmem_cache on allocation error

On 16/01/2018 13:15, Chris Wilson wrote: If we fail to allocate a new request, make sure we recover the pages that are in the process of being freed by inserting an RCU barrier. v2: Comment before the shrink and barrier in the error path. Signed-off-by: Chris Wilson

Re: [Intel-gfx] [PATCH v2] drm/i915: Shrink the GEM kmem_caches upon idling

On 16/01/2018 15:12, Tvrtko Ursulin wrote: On 16/01/2018 13:05, Chris Wilson wrote: When we finally decide the gpu is idle, that is a good time to shrink our kmem_caches. v2: Comment upon the random sprinkling of rcu_barrier() inside the idle worker. Signed-off-by: Chris Wilson

Re: [Intel-gfx] [PATCH v2] drm/i915: Shrink the GEM kmem_caches upon idling

On 16/01/2018 13:05, Chris Wilson wrote: When we finally decide the gpu is idle, that is a good time to shrink our kmem_caches. v2: Comment upon the random sprinkling of rcu_barrier() inside the idle worker. Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin

[Intel-gfx] [PATCH igt] igt/kms_frontbuffer_tracking: Show FBC status at the start of the wait

Signed-off-by: Chris Wilson --- tests/kms_frontbuffer_tracking.c | 4 1 file changed, 4 insertions(+) diff --git a/tests/kms_frontbuffer_tracking.c b/tests/kms_frontbuffer_tracking.c index 1601cab45..8b440dadc 100644 --- a/tests/kms_frontbuffer_tracking.c +++

[Intel-gfx] [PATCH igt 3/5] igt/gem_ctx_switch: Exercise all engines at once

Just a small variant to apply a continuous context-switch load to all engines. --- tests/gem_ctx_switch.c | 76 ++ 1 file changed, 76 insertions(+) diff --git a/tests/gem_ctx_switch.c b/tests/gem_ctx_switch.c index 159554e52..fe919f7d6 100644 ---

[Intel-gfx] [PATCH igt 2/5] igt/gem_ctx_switch: Do a warmup pass over all contexts

Ensure that we always use every context at least once before we start running the stress-test. Signed-off-by: Chris Wilson --- tests/gem_ctx_switch.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/tests/gem_ctx_switch.c b/tests/gem_ctx_switch.c index

[Intel-gfx] [PATCH igt 1/5] igt/gem_ctx_isolation: Check isolation of registers between contexts

A new context assumes that all of its registers are in the default state when it is created. What may happen is that a register written by one context may leak into the second, causing mass confusion. v2: Extend back to Sandybridge (etc) v3: Check context preserves registers across

[Intel-gfx] [PATCH igt 5/5] igt/gem_exec_fence: Exercise merging fences

Execute the same batch on each engine and check that the composite fence across all engines completes only after the batch is completed on every engine. Signed-off-by: Chris Wilson --- tests/gem_exec_fence.c | 127 + 1

[Intel-gfx] [PATCH igt 4/5] igt/gem_exec_capture: Exercise readback of userptr

EXEC_OBJECT_CAPTURE extends the type of buffers we may read during error capture. Previously we knew that we would only see batch buffers (which limited the objects to being from gem_create()), but now we need to check that any buffer the user can create can be read. The first alternate buffer

[Intel-gfx] ✓ Fi.CI.BAT: success for kms_plane_scaling tests. (rev3)

== Series Details == Series: kms_plane_scaling tests. (rev3) URL : https://patchwork.freedesktop.org/series/36485/ State : success == Summary == IGT patchset tested on top of latest successful build 7b685d5790c1770eeac43c17d6b207a6df602985 Update NEWS, bump version to 1.21. with latest

Re: [Intel-gfx] [PATCH v5 6/6] drm/i915: expose rcs topology through query uAPI

On 16/01/18 14:22, Chris Wilson wrote: Quoting Lionel Landwerlin (2018-01-16 13:40:10) With the introduction of asymmetric slices in CNL, we cannot rely on the previous SUBSLICE_MASK getparam to tell userspace what subslices are available. Here we introduce a more detailed way of querying the

[Intel-gfx] [ANNOUNCE] intel-gpu-tools 1.21

A new intel-gpu-tools quarterly release is available with the following changes: Library changes: - Added helpers for using DRM syncobj. (Jason Ekstrand) - Refactored several i915 helpers into library functions. (Michał Winiarski) - Improved the GPU quiescing code to more thoroughly flush

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Allow user to override PWM backlight frequency and duty cycle

== Series Details == Series: drm/i915: Allow user to override PWM backlight frequency and duty cycle URL : https://patchwork.freedesktop.org/series/36540/ State : failure == Summary == Applying: drm/i915: Allow user to override PWM backlight frequency and duty cycle error: Failed to merge in

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: expose RCS topology to userspace

== Series Details == Series: drm/i915: expose RCS topology to userspace URL : https://patchwork.freedesktop.org/series/36539/ State : success == Summary == Series 36539v1 drm/i915: expose RCS topology to userspace https://patchwork.freedesktop.org/api/1.0/series/36539/revisions/1/mbox/ Test

Re: [Intel-gfx] [PATCH v5 5/6] drm/i915: add query uAPI

On 16/01/18 14:08, Chris Wilson wrote: Quoting Lionel Landwerlin (2018-01-16 13:40:09) +int i915_query_ioctl(struct drm_device *dev, void *data, struct drm_file *file) +{ + struct drm_i915_query *args = data; + struct drm_i915_query_item __user *user_item_ptr = +

Re: [Intel-gfx] [PATCH v5 6/6] drm/i915: expose rcs topology through query uAPI

Quoting Lionel Landwerlin (2018-01-16 13:40:10) > With the introduction of asymmetric slices in CNL, we cannot rely on > the previous SUBSLICE_MASK getparam to tell userspace what subslices > are available. Here we introduce a more detailed way of querying the > Gen's GPU topology that doesn't

Re: [Intel-gfx] [PATCH i-g-t] tests/kms_plane_scaling: test scaling with tiling rotation and pixel formats, v3.

On Tue, 2018-01-16 at 15:00 +0100, Maarten Lankhorst wrote: > From: Jyoti Yadav > > This patch adds subtest for testing scaling in combination with > rotation > and pixel formats. > > Changes since v1: > - Rework test to work with the other changes to kms_plane_scaling.

Re: [Intel-gfx] [PATCH v5 4/6] drm/i915: add rcs topology to error state

On 16/01/18 13:57, Chris Wilson wrote: Quoting Lionel Landwerlin (2018-01-16 13:40:08) This might be useful information for developers looking at an error state. v2: Place topology towards the end of the error state (Chris) v3: Reuse common printing code (Michal) Signed-off-by: Lionel

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/4] meson: Build cnl_compute_wrpll

== Series Details == Series: series starting with [1/4] meson: Build cnl_compute_wrpll URL : https://patchwork.freedesktop.org/series/36525/ State : failure == Summary == Test perf: Subgroup polling: fail -> PASS (shard-hsw) fdo#102252 Test kms_flip:

Re: [Intel-gfx] [PATCH v5 5/6] drm/i915: add query uAPI

Quoting Lionel Landwerlin (2018-01-16 13:40:09) > +int i915_query_ioctl(struct drm_device *dev, void *data, struct drm_file > *file) > +{ > + struct drm_i915_query *args = data; > + struct drm_i915_query_item __user *user_item_ptr = > + u64_to_user_ptr(args->items_ptr);

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v2,1/2] drm/i915: Add display WA #1175 for planes ending close to right screen edge

== Series Details == Series: series starting with [v2,1/2] drm/i915: Add display WA #1175 for planes ending close to right screen edge URL : https://patchwork.freedesktop.org/series/36526/ State : failure == Summary == Test drv_selftest: Subgroup mock_fence: pass

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [01/10] drm/i915: Only attempt to scan the requested number of shrinker slabs (rev4)

== Series Details == Series: series starting with [01/10] drm/i915: Only attempt to scan the requested number of shrinker slabs (rev4) URL : https://patchwork.freedesktop.org/series/36501/ State : success == Summary == Series 36501v4 series starting with [01/10] drm/i915: Only attempt to

[Intel-gfx] [PATCH i-g-t] tests/kms_plane_scaling: test scaling with tiling rotation and pixel formats, v3.

From: Jyoti Yadav This patch adds subtest for testing scaling in combination with rotation and pixel formats. Changes since v1: - Rework test to work with the other changes to kms_plane_scaling. (Maarten) - Remove hardcodes for MIN/MAX_SRC_WIDTH, and use the value

  1   2   >