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

[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

[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

[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 ---

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

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.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: 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: 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

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 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

[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] [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

Re: [Intel-gfx] [PATCH i-g-t v3 4/8] tests/kms_plane_scaling: Move get_num_scalers to a function.

On Mon, 2018-01-15 at 15:28 +0100, Maarten Lankhorst wrote: > The number of scalers can depend on the pipe, so require at least 1 > scaler before running any subtests. > > Signed-off-by: Maarten Lankhorst > --- >  tests/kms_plane_scaling.c | 20

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

On 15/01/2018 18:23, Lionel Landwerlin wrote: On 15/01/18 17:54, Tvrtko Ursulin wrote: On 15/01/2018 14:41, 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

Re: [Intel-gfx] Prevent trivial oom from gem_exec_nop/sequential

On 15/01/2018 21:24, Chris Wilson wrote: About the third resend of this series that tries to curtail the prolonged reference lifetimes of fences via the signaler thread when the CPUs are saturated by interrupts. Happens on CI, regularly, occasionally? In the real-world it shouldnt right?

Re: [Intel-gfx] [PATCH] drm/i915/bxt: Enable VBT based BL control for DP (v2)

On Wed, 10 Jan 2018, Mustamin B Mustaffa wrote: > Currently, BXT_PP is hardcoded with value '0'. > It practically disabled eDP backlight on MRB (BXT) platform. > > This patch will tell which BXT_PP registers (there are two set of PP_CONTROL > in the spec) > to be

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

On 15/01/2018 21:24, 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. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/i915_gem_request.c | 3 +++ 1

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, 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 12:07:28 +0200, Joonas Lahtinen wrote: > > On Fri, 2018-01-12 at 14:08 +0800, Du, Changbin

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

== Series Details == Series: kms_plane_scaling tests. (rev2) URL : https://patchwork.freedesktop.org/series/36485/ State : success == Summary == IGT patchset tested on top of latest successful build 84a308022028a55903a1916fcee516aab768ed48 tests/kms_plane: Run test for all supported pixel

Re: [Intel-gfx] [PATCH v2] drm/i915/selftests: Test i915_sw_fence/dma_fence interop

Quoting Tvrtko Ursulin (2018-01-16 09:48:48) > > On 15/01/2018 20:43, Chris Wilson wrote: > > Check that we can successfully wait upon a dma_fence using the > > i915_sw_fence, including the optional timeout mechanism. > > > > v2: Account for the rounding up of the timeout to the next second. > >

Re: [Intel-gfx] [PATCH i-g-t v3 7/8] tests/kms_plane_scaling: test scaler with clipping clamping, v3.

On Mon, 2018-01-15 at 15:28 +0100, Maarten Lankhorst wrote: > From: Jyoti Yadav > > This patch adds subtest to test scaler clipping and clamping > scenario. > > Changes since v1: > - Modify test to work with the changes to kms_plane_scaling. > (Maarten) > Changes since

Re: [Intel-gfx] [PATCH i-g-t v3 5/8] tests/kms_plane_scaling: Clean up tests to work better with igt_kms, v2.

On Mon, 2018-01-15 at 15:28 +0100, Maarten Lankhorst wrote: > The test only runs on gen9+, so we can safely replace all calls with > COMMIT_ATOMIC. > > Also perform some cleanups by making fb an array, and cleaning up in > prepare_crtc. This way failed subtests won't cause failures in other >

Re: [Intel-gfx] [PATCH v2] drm/i915/selftests: Test i915_sw_fence/dma_fence interop

On 15/01/2018 20:43, Chris Wilson wrote: Check that we can successfully wait upon a dma_fence using the i915_sw_fence, including the optional timeout mechanism. v2: Account for the rounding up of the timeout to the next second. Unfortunately, the minimum delay is then 1 second. Signed-off-by:

[Intel-gfx] [PATCH i-g-t] tests/kms_plane_scaling: Move get_num_scalers to a function, v2.

The number of scalers can depend on the pipe, so require at least 1 scaler before running any subtests. Changes since v1: - More closely match kernel implementation. (Mika) Signed-off-by: Maarten Lankhorst --- tests/kms_plane_scaling.c | 22

Re: [Intel-gfx] [PATCH 05/10] drm/i915: Trim the retired request queue after submitting

Quoting Tvrtko Ursulin (2018-01-16 10:18:55) > > On 15/01/2018 21:24, Chris Wilson wrote: > > If we submit a request and see that the previous request on this > > timeline was already signaled, we first do not need to add the > > dependency tracker for that completed request and secondly we know

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Extend partial vma coverage to check parallel creation

== Series Details == Series: drm/i915/selftests: Extend partial vma coverage to check parallel creation URL : https://patchwork.freedesktop.org/series/36520/ State : success == Summary == Series 36520v1 drm/i915/selftests: Extend partial vma coverage to check parallel creation

[Intel-gfx] [PATCH v2 1/2] drm/i915: Add display WA #1175 for planes ending close to right screen edge

As described in the WA on GLK and CNL planes on the right edge of the screen that have less than 4 pixels visible from the beginning of the plane to the edge of the screen can cause FIFO underflow and display corruption. On GLK/CNL I could trigger the problem only if the plane was at the same

[Intel-gfx] [PATCH v2 2/2] drm/i915: Add WA for planes ending close to left screen edge

While running the kms_plane clipping test I noticed a similar problem to the one described in Display WA #1175. In this case, similarly for planes other than the cursor, with 1 or 3 pixels visible from the left edge of the screen to the end of the plane and an odd plane X offset used for clipping

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

== Series Details == Series: kms_plane_scaling tests. URL : https://patchwork.freedesktop.org/series/36485/ State : success == Summary == IGT patchset tested on top of latest successful build 84a308022028a55903a1916fcee516aab768ed48 tests/kms_plane: Run test for all supported pixel formats,

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 Mon, 2018-01-15 at 13:10 +0200, Tomi Sarvela wrote: > On 15/01/18 12:28, Zhenyu Wang wrote: > > On 2018.01.15 12:07:28 +0200, Joonas Lahtinen wrote: > > > On Fri, 2018-01-12 at 14:08 +0800, Du, Changbin wrote: > > > > On Fri, Jan 12, 2018 at 11:32:30AM +0530, Sagar Arun Kamble wrote: > > > > >

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

On 15/01/2018 21:24, Chris Wilson wrote: When we finally decide the gpu is idle, that is a good time to shrink our kmem_caches. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/i915_gem.c | 22 ++ 1 file changed, 22 insertions(+) diff

[Intel-gfx] [PATCH] drm/i915/selftests: Extend partial vma coverage to check parallel creation

One important use of partial vma is to provide mappable access to the object while it is being used elsewhere (pinned entirely into the unmappable portion of the Global GTT, i.e. for use as a display scanout). Signed-off-by: Chris Wilson Cc: Joonas Lahtinen

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

Quoting Tvrtko Ursulin (2018-01-16 10:00:16) > > On 15/01/2018 21:24, Chris Wilson wrote: > > When we finally decide the gpu is idle, that is a good time to shrink > > our kmem_caches. > > > > Signed-off-by: Chris Wilson > > --- > > drivers/gpu/drm/i915/i915_gem.c |

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

Quoting Tvrtko Ursulin (2018-01-16 10:10:28) > > On 15/01/2018 21:24, 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. > > > > Signed-off-by: Chris Wilson

Re: [Intel-gfx] [PATCH 1/3] drm/i915: Convert intel_hpd_irq_event() into an encoder hotplug hook

On Fri, 12 Jan 2018, Ville Syrjala wrote: > From: Ville Syrjälä > > Allow encoders to customize their hotplug processing by moving the > intel_hpd_irq_event() code into an encoder hotplug vfunc. Currently > only SDVO needs this to

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

On 16/01/18 08:42, Tvrtko Ursulin wrote: On 15/01/2018 18:23, Lionel Landwerlin wrote: On 15/01/18 17:54, Tvrtko Ursulin wrote: On 15/01/2018 14:41, Lionel Landwerlin wrote: With the introduction of asymmetric slices in CNL, we cannot rely on the previous SUBSLICE_MASK getparam to tell

[Intel-gfx] [PATCH i-g-t 4/4] meson: Name the project intel-gpu-tools

Eventually we're switching the official name to "IGT GPU Tools", but right now there's still a lot of hardcoding to intel-gpu-tools that is to be fixed in the near future. Rename the project in toplevel meson.build to intel-gpu-tools to get meson to generate tarballs roughly the same as autotools

[Intel-gfx] [PATCH i-g-t 1/4] meson: Build cnl_compute_wrpll

Signed-off-by: Petri Latvala --- tools/meson.build | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/meson.build b/tools/meson.build index 7fc5390a..4258853e 100644 --- a/tools/meson.build +++ b/tools/meson.build @@ -1,4 +1,5 @@ tools_progs_noisnt = [ +

[Intel-gfx] [PATCH i-g-t 3/4] meson: Add quotes in assembler/test/run-test.sh

If the directories contain spaces, run-test.sh fails. Signed-off-by: Petri Latvala --- assembler/test/run-test.sh | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/assembler/test/run-test.sh b/assembler/test/run-test.sh index

[Intel-gfx] [PATCH i-g-t 2/4] meson: Add quotes in man/rst2man.sh

If the directories contain spaces, rst2man.sh fails. Signed-off-by: Petri Latvala --- man/rst2man.sh | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/man/rst2man.sh b/man/rst2man.sh index fc2b5ed8..8106ca4b 100755 --- a/man/rst2man.sh +++

Re: [Intel-gfx] [PATCH] drm/i915: Rewrite some comments around RCU-deferred object free

On 15/01/2018 20:57, Chris Wilson wrote: Tvrtko noticed that the comments describing the interaction of RCU and the deferred worker for freeing drm_i915_gem_object were a little confusing, so attempt to bring some sense to them. Signed-off-by: Chris Wilson Cc: Tvrtko

Re: [Intel-gfx] Prevent trivial oom from gem_exec_nop/sequential

Quoting Tvrtko Ursulin (2018-01-16 09:52:10) > > On 15/01/2018 21:24, Chris Wilson wrote: > > About the third resend of this series that tries to curtail the prolonged > > reference lifetimes of fences via the signaler thread when the CPUs are > > saturated by interrupts. > > Happens on CI,

Re: [Intel-gfx] [PATCH v2] drm/i915/selftests: Test i915_sw_fence/dma_fence interop

Quoting Tvrtko Ursulin (2018-01-16 09:48:48) > > On 15/01/2018 20:43, Chris Wilson wrote: > > +static struct dma_fence *alloc_dma_fence(void) > > +{ > > + struct dma_fence *dma; > > + > > + dma = kmalloc(sizeof(*dma), GFP_KERNEL); > > + if (dma) > > + dma_fence_init(dma,

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

== Series Details == Series: kms_plane_scaling tests. (rev2) URL : https://patchwork.freedesktop.org/series/36485/ State : failure == Summary == Test kms_cursor_crc: Subgroup cursor-128x128-suspend: skip -> PASS (shard-snb) fdo#103880 Test gem_softpin:

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/selftests: Extend partial vma coverage to check parallel creation

== Series Details == Series: drm/i915/selftests: Extend partial vma coverage to check parallel creation URL : https://patchwork.freedesktop.org/series/36520/ State : success == Summary == Warning: bzip Patchwork_7679/shard-snb7/results4.json.bz2 wasn't in correct JSON format Test

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

== Series Details == Series: series starting with [01/10] drm/i915: Only attempt to scan the requested number of shrinker slabs URL : https://patchwork.freedesktop.org/series/36501/ State : success == Summary == Test kms_frontbuffer_tracking: Subgroup fbc-rgb565-draw-render:

Re: [Intel-gfx] [PATCH 05/10] drm/i915: Trim the retired request queue after submitting

On 15/01/2018 21:24, Chris Wilson wrote: If we submit a request and see that the previous request on this timeline was already signaled, we first do not need to add the dependency tracker for that completed request and secondly we know that we there is then a large backlog in retiring requests

Re: [Intel-gfx] [PATCH i-g-t] tests/kms_plane_scaling: Move get_num_scalers to a function, v2.

On Tue, 2018-01-16 at 11:03 +0100, Maarten Lankhorst wrote: > The number of scalers can depend on the pipe, so require at least 1 > scaler before running any subtests. > > Changes since v1: > - More closely match kernel implementation. (Mika) > Reviewed-by: Mika Kahola

[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] [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: 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

[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 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] 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.BAT: success 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 : success == Summary == Series 36526v1 series starting with [v2,1/2] drm/i915: Add display WA

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

On Mon, 2018-01-15 at 15:28 +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 v4 4/6] drm/i915: add rcs topology to error state

On 15/01/18 17:43, Tvrtko Ursulin wrote: On 15/01/2018 14:41, Lionel Landwerlin wrote: 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] [PATCH v5 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 v5 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) Signed-off-by: Lionel Landwerlin Reviewed-by: Tvrtko Ursulin

[Intel-gfx] [PATCH v5 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 v5 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 v5 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 v5 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 v5 0/6] drm/i915: expose RCS topology to userspace

Hi all, Hopefully this is the last iteration. A few more tweaks only on patch 6 for uapi define/struct naming and factored out code in the data exchange between kernel & userspace. Thanks, Lionel Landwerlin (6): drm/i915: store all subslice masks drm/i915/debugfs: reuse max slice/subslices

Re: [Intel-gfx] [PATCH i-g-t v3 8/8] tests/kms_plane_scaling: test for multi pipe with scaling, v3.

Op 16-01-18 om 14:46 schreef Mika Kahola: > On Mon, 2018-01-15 at 15:28 +0100, Maarten Lankhorst wrote: >> From: Jyoti Yadav >> >> Add a subtest to display primary and overlay planes on two >> connected pipes and runs scaling test on both pipes >> >> Changes since v1: >>

Re: [Intel-gfx] [PATCH i-g-t v3 8/8] tests/kms_plane_scaling: test for multi pipe with scaling, v3.

On Tue, 2018-01-16 at 14:47 +0100, Maarten Lankhorst wrote: > Op 16-01-18 om 14:46 schreef Mika Kahola: > > > > On Mon, 2018-01-15 at 15:28 +0100, Maarten Lankhorst wrote: > > > > > > From: Jyoti Yadav > > > > > > Add a subtest to display primary and overlay planes on

[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

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);

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

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 = +

[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: 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 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

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 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

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

[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

[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

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

[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

[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

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] [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 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 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] [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 +++

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

[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 > > +++

[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

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.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

[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

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

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. > >>> >

[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

  1   2   >