[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Skip an engine reset if it recovered before our preparations (rev2)

== Series Details == Series: drm/i915: Skip an engine reset if it recovered before our preparations (rev2) URL : https://patchwork.freedesktop.org/series/35453/ State : failure == Summary == Warning: bzip CI_DRM_3525/shard-glkb6/results10.json.bz2 wasn't in correct JSON format Test gem_eio:

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Restore the kernel context after a GPU reset on an idle engine

== Series Details == Series: drm/i915: Restore the kernel context after a GPU reset on an idle engine URL : https://patchwork.freedesktop.org/series/35454/ State : failure == Summary == Warning: bzip CI_DRM_3525/shard-glkb6/results10.json.bz2 wasn't in correct JSON format Test

Re: [Intel-gfx] [PATCH i-g-t 1/4] lib: copy intel_aub.h from libdrm

Reviewed-by: Jordan Justen On 2017-12-06 15:11:20, Scott D Phillips wrote: > No functionality related to aub is provided by libdrm aside from > intel_aub.h which somewhat defines the file format. Move the > header into this project to ease aub-related development. > >

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Skip an engine reset if it recovered before our preparations

== Series Details == Series: drm/i915: Skip an engine reset if it recovered before our preparations URL : https://patchwork.freedesktop.org/series/35453/ State : success == Summary == Warning: bzip CI_DRM_3525/shard-glkb6/results10.json.bz2 wasn't in correct JSON format Test perf:

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Skip an engine reset if it recovered before our preparations (rev2)

== Series Details == Series: drm/i915: Skip an engine reset if it recovered before our preparations (rev2) URL : https://patchwork.freedesktop.org/series/35453/ State : success == Summary == Series 35453v2 drm/i915: Skip an engine reset if it recovered before our preparations

[Intel-gfx] ✗ Fi.CI.BAT: warning for series starting with [1/2] drm/i915: Implement WaDisableVFclkgate.

== Series Details == Series: series starting with [1/2] drm/i915: Implement WaDisableVFclkgate. URL : https://patchwork.freedesktop.org/series/35456/ State : warning == Summary == Series 35456v1 series starting with [1/2] drm/i915: Implement WaDisableVFclkgate.

Re: [Intel-gfx] [PATCH] drm/i915: Restore the kernel context after a GPU reset on an idle engine

On 12/15/2017 4:03 PM, Chris Wilson wrote: As part of the system requirement for powersaving is that we always have a context loaded. Upon boot and resume, we load the kernel_context to ensure that some valid state is set before powersaving kicks in, we should do so after a full GPU reset as

Re: [Intel-gfx] [PATCH] drm/i915/trace: add hw_id to gem requests trace points

On 15/12/17 21:15, Chris Wilson wrote: Quoting Tvrtko Ursulin (2017-12-15 17:22:57) On 15/12/2017 16:18, Lionel Landwerlin wrote: On 15/12/17 16:08, Chris Wilson wrote: Quoting Lionel Landwerlin (2017-12-15 15:51:36) When monitoring the GPU with i915 perf, reports are tagged with a hw id.

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Restore the kernel context after a GPU reset on an idle engine

== Series Details == Series: drm/i915: Restore the kernel context after a GPU reset on an idle engine URL : https://patchwork.freedesktop.org/series/35454/ State : success == Summary == Series 35454v1 drm/i915: Restore the kernel context after a GPU reset on an idle engine

Re: [Intel-gfx] [PATCH v2] drm/i915: Skip an engine reset if it recovered before our preparations

On 12/15/2017 4:22 PM, Chris Wilson wrote: At the beginning of a reset, we disable the submission method and find the stuck request. We expect to find a stuck request for we have declared the engine stalled. However, if we find no active request, the engine must have recovered from its stall

[Intel-gfx] [PATCH v2] drm/i915: Skip an engine reset if it recovered before our preparations

At the beginning of a reset, we disable the submission method and find the stuck request. We expect to find a stuck request for we have declared the engine stalled. However, if we find no active request, the engine must have recovered from its stall before we could issue a reset, so let the engine

Re: [Intel-gfx] [PATCH] drm/i915: Skip an engine reset if it recovered before our preparations

On 12/15/2017 4:16 PM, Chris Wilson wrote: Quoting Michel Thierry (2017-12-16 00:02:47) Hi, On 12/15/2017 3:52 PM, Chris Wilson wrote: At the beginning of a reset, we disable the submission method and find the stuck request. We expect to find a stuck request for we have declared the engine

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Skip an engine reset if it recovered before our preparations

== Series Details == Series: drm/i915: Skip an engine reset if it recovered before our preparations URL : https://patchwork.freedesktop.org/series/35453/ State : success == Summary == Series 35453v1 drm/i915: Skip an engine reset if it recovered before our preparations

Re: [Intel-gfx] [PATCH] drm/i915: Skip an engine reset if it recovered before our preparations

Quoting Michel Thierry (2017-12-16 00:02:47) > Hi, > > On 12/15/2017 3:52 PM, Chris Wilson wrote: > > At the beginning of a reset, we disable the submission method and find > > the stuck request. We expect to find a stuck request for we have > > declared the engine stalled. However, if we find no

Re: [Intel-gfx] [PATCH i-g-t] tests/gem_ctx_param: Update invalid param

Quoting Antonio Argenziano (2017-12-15 19:01:11) > Since commit: drm/i915/scheduler: Support user-defined priorities, the > driver support an extra context param to set context's priority. Add > tests for that interface and update invalid tests. > > Signed-off-by: Antonio Argenziano

[Intel-gfx] [PATCH 1/2] drm/i915: Implement WaDisableVFclkgate.

This workaround supposedly fixes some hangs in the VF unit. Signed-off-by: Rafael Antognolli Reviewed-by: Lucas De Marchi --- drivers/gpu/drm/i915/i915_reg.h | 3 +++ drivers/gpu/drm/i915/intel_pm.c | 5 + 2 files changed, 8

[Intel-gfx] [PATCH 2/2] drm/i915: Implement WaDisableEarlyEOT.

There seems to be another clock gating issue which the workaround is described as: "WA: Set 0xE4F0[1] = 1 to disable Early EOT of thread." Signed-off-by: Rafael Antognolli Reviewed-by: Lucas De Marchi ---

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Protect DDI port to DPLL map from theoretical race. (rev2)

== Series Details == Series: drm/i915: Protect DDI port to DPLL map from theoretical race. (rev2) URL : https://patchwork.freedesktop.org/series/35446/ State : failure == Summary == Warning: bzip CI_DRM_3525/shard-glkb6/results10.json.bz2 wasn't in correct JSON format Test gem_softpin:

[Intel-gfx] [PATCH] drm/i915: Restore the kernel context after a GPU reset on an idle engine

As part of the system requirement for powersaving is that we always have a context loaded. Upon boot and resume, we load the kernel_context to ensure that some valid state is set before powersaving kicks in, we should do so after a full GPU reset as well. We only need to do so for an idle engine,

Re: [Intel-gfx] [PATCH] drm/i915: Skip an engine reset if it recovered before our preparations

Hi, On 12/15/2017 3:52 PM, Chris Wilson wrote: At the beginning of a reset, we disable the submission method and find the stuck request. We expect to find a stuck request for we have declared the engine stalled. However, if we find no active request, the engine must have recovered from its

[Intel-gfx] [PATCH] drm/i915: Skip an engine reset if it recovered before our preparations

At the beginning of a reset, we disable the submission method and find the stuck request. We expect to find a stuck request for we have declared the engine stalled. However, if we find no active request, the engine must have recovered from its stall before we could issue a reset, so let the engine

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/cnl: Add support for horizontal plane flipping (rev2)

== Series Details == Series: drm/i915/cnl: Add support for horizontal plane flipping (rev2) URL : https://patchwork.freedesktop.org/series/29114/ State : success == Summary == Warning: bzip CI_DRM_3525/shard-glkb6/results10.json.bz2 wasn't in correct JSON format Test gem_eio:

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Protect DDI port to DPLL map from theoretical race. (rev2)

== Series Details == Series: drm/i915: Protect DDI port to DPLL map from theoretical race. (rev2) URL : https://patchwork.freedesktop.org/series/35446/ State : success == Summary == Series 35446v2 drm/i915: Protect DDI port to DPLL map from theoretical race.

Re: [Intel-gfx] [PATCH] drm/i915/glk: Disable Guc and HuC on GLK

On Fri, Dec 15, 2017 at 06:07:27AM +, Michal Wajdeczko wrote: > On Thu, 14 Dec 2017 23:30:56 +0100, Srivatsa, Anusha > wrote: > > > > > > > > -Original Message- > > > From: Wajdeczko, Michal > > > Sent: Thursday, December 14, 2017 2:18 PM > > > To:

[Intel-gfx] [PATCH v2] drm/i915: Protect DDI port to DPLL map from theoretical race.

In case we have multiple modesets for different connectors happening in parallel we could have a race on the RMW on these shared registers. This possibility was initially raised by Paulo when reviewing commit '555e38d27317 ("drm/i915/cnl: DDI - PLL mapping")' but the original possibility comes

[Intel-gfx] ✓ Fi.CI.IGT: success for tests/gem_ctx_param: Update invalid param

== Series Details == Series: tests/gem_ctx_param: Update invalid param URL : https://patchwork.freedesktop.org/series/35438/ State : success == Summary == Warning: bzip CI_DRM_3524/shard-glkb6/results10.json.bz2 wasn't in correct JSON format Test gem_ctx_param: Subgroup

Re: [Intel-gfx] [PATCH] drm/i915/cnl: Add support for horizontal plane flipping

Quoting Rodrigo Vivi (2017-12-15 21:38:00) > From: Joonas Lahtinen > > CNL supports horizontal plane flipping on non-linear plane formats. > > v2: > - Avoid BUG unlike elsewhere in the code (Ville) > - Hoist the rotation-tiling restriction check (Ville) > > v3

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Protect DDI port to DPLL map from theoretical race.

== Series Details == Series: drm/i915: Protect DDI port to DPLL map from theoretical race. URL : https://patchwork.freedesktop.org/series/35446/ State : failure == Summary == Applying: drm/i915: Protect DDI port to DPLL map from theoretical race. error: sha1 information is lacking or useless

[Intel-gfx] [PATCH] drm/i915: Protect DDI port to DPLL map from theoretical race.

In case we have multiple modesets for different connectors happening in parallel we could have a race on the RMW on these shared registers. This possibility was initially raised by Paulo when reviewing commit '555e38d27317 ("drm/i915/cnl: DDI - PLL mapping")' but the original possibility comes

[Intel-gfx] ✓ Fi.CI.IGT: success for trace.pl: handle request tracepoint fields regardless of their order

== Series Details == Series: trace.pl: handle request tracepoint fields regardless of their order URL : https://patchwork.freedesktop.org/series/35434/ State : success == Summary == Warning: bzip CI_DRM_3524/shard-glkb6/results10.json.bz2 wasn't in correct JSON format Test

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/cnl: Add support for horizontal plane flipping (rev2)

== Series Details == Series: drm/i915/cnl: Add support for horizontal plane flipping (rev2) URL : https://patchwork.freedesktop.org/series/29114/ State : success == Summary == Series 29114v2 drm/i915/cnl: Add support for horizontal plane flipping

[Intel-gfx] [PATCH] drm/i915/cnl: Add support for horizontal plane flipping

From: Joonas Lahtinen CNL supports horizontal plane flipping on non-linear plane formats. v2: - Avoid BUG unlike elsewhere in the code (Ville) - Hoist the rotation-tiling restriction check (Ville) v3 (Rodrigo): - Rebased after a while. - Fix small indentation

Re: [Intel-gfx] [PATCH v2] x86/gpu: add CFL to early quirks

On Fri, Dec 15, 2017 at 04:39:25PM +, Ingo Molnar wrote: > > * Lucas De Marchi wrote: > > > CFL was missing from intel_early_ids[]. The PCI ID needs to be there to > > allow the memory region to be stolen, otherwise we could have RAM being > > arbitrarily

Re: [Intel-gfx] [PATCH] drm/i915/trace: add hw_id to gem requests trace points

Quoting Tvrtko Ursulin (2017-12-15 17:22:57) > > On 15/12/2017 16:18, Lionel Landwerlin wrote: > > On 15/12/17 16:08, Chris Wilson wrote: > >> Quoting Lionel Landwerlin (2017-12-15 15:51:36) > >>> When monitoring the GPU with i915 perf, reports are tagged with a hw > >>> id. When also tracking

Re: [Intel-gfx] [PATCH igt] igt/perf_pmu: Speed up frequency measurement

Quoting Tvrtko Ursulin (2017-12-15 18:24:42) > > On 15/12/2017 17:05, Chris Wilson wrote: > > Use the normal batch_duration_ns and display the sampled frequency: > > > > Frequency: min=100, max=750, boost=750 MHz > > Min frequency: requested 100.0, actual 100.0 > > Max

Re: [Intel-gfx] [PATCH i-g-t] intel_vbt_decode: Typo fixes

Quoting Adam Jackson (2017-12-15 19:59:36) > Signed-off-by: Adam Jackson > --- > tools/intel_vbt_decode.c | 4 ++-- > tools/intel_vbt_defs.h | 6 +++--- > 2 files changed, 5 insertions(+), 5 deletions(-) > > diff --git a/tools/intel_vbt_decode.c b/tools/intel_vbt_decode.c >

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/trace: add hw_id to gem requests trace points (rev2)

== Series Details == Series: drm/i915/trace: add hw_id to gem requests trace points (rev2) URL : https://patchwork.freedesktop.org/series/35420/ State : success == Summary == Test kms_setmode: Subgroup basic: fail -> WARN (shard-snb) fdo#99912 Test

Re: [Intel-gfx] [PATCH igt v2 1/4] igt/perf_pmu: Tighten busy measurement

Quoting Tvrtko Ursulin (2017-12-15 18:16:52) > > On 15/12/2017 16:10, Chris Wilson wrote: > > Sleep for a known duration. In particular, CI once saw a measurement for > > busyness greater than the intended batch_duration! > > > > v2: Go back to starting pmu sampling outside of spinner; the GPU

Re: [Intel-gfx] [PATCH i-g-t 3/4] hw-tests: Fix and update gem_bad_address

Quoting Petri Latvala (2017-12-13 12:58:15) > From: Antonio Argenziano > > When writing to an invalid memory location, the HW should be clever > enough to silently discard the write without disrupting execution. > gem_bad_address aim at just that. The test has been

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v2,1/4] igt/perf_pmu: Tighten busy measurement

== Series Details == Series: series starting with [v2,1/4] igt/perf_pmu: Tighten busy measurement URL : https://patchwork.freedesktop.org/series/35421/ State : failure == Summary == Test kms_flip: Subgroup flip-vs-panning: pass -> DMESG-WARN (shard-hsw)

[Intel-gfx] ✗ Fi.CI.IGT: failure for igt/perf_pmu: Tighten measurements for most-busy

== Series Details == Series: igt/perf_pmu: Tighten measurements for most-busy URL : https://patchwork.freedesktop.org/series/35414/ State : failure == Summary == Test kms_flip: Subgroup blt-wf_vblank-vs-modeset-interruptible: incomplete -> PASS (shard-hsw)

[Intel-gfx] [PATCH i-g-t] intel_vbt_decode: Typo fixes

Signed-off-by: Adam Jackson --- tools/intel_vbt_decode.c | 4 ++-- tools/intel_vbt_defs.h | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/tools/intel_vbt_decode.c b/tools/intel_vbt_decode.c index 9d90c69d..ce7da2c0 100644 ---

Re: [Intel-gfx] [PATCH i-g-t 2/4] tests: Move gem_bad_address to hw-tests

On 13/12/17 05:26, Chris Wilson wrote: Quoting Petri Latvala (2017-12-13 12:58:14) Since the test is considered to be HW focused, meaning that it doesn't really exercise the driver but rather an HW feature, it is placed in tests/hw-tests. Do we really want to keep this test at all? It's an

[Intel-gfx] ✗ Fi.CI.IGT: failure for igt/perf_pmu: Tighten busy measurement

== Series Details == Series: igt/perf_pmu: Tighten busy measurement URL : https://patchwork.freedesktop.org/series/35412/ State : failure == Summary == Test kms_flip: Subgroup flip-vs-panning-vs-hang: dmesg-warn -> PASS (shard-snb) fdo#103821 Subgroup

[Intel-gfx] ✓ Fi.CI.BAT: success for tests/gem_ctx_param: Update invalid param

== Series Details == Series: tests/gem_ctx_param: Update invalid param URL : https://patchwork.freedesktop.org/series/35438/ State : success == Summary == IGT patchset tested on top of latest successful build c0be3310715e2f744b892c51f09e62273bcc8e57 tests/kms_frontbuffer_tracking: Correctly

[Intel-gfx] ✓ Fi.CI.BAT: success for trace.pl: handle request tracepoint fields regardless of their order

== Series Details == Series: trace.pl: handle request tracepoint fields regardless of their order URL : https://patchwork.freedesktop.org/series/35434/ State : success == Summary == IGT patchset tested on top of latest successful build c0be3310715e2f744b892c51f09e62273bcc8e57

Re: [Intel-gfx] [PATCH v4 3/5] drm/i915/guc: Implement dynamic WOPCM partitioning

On 12/15/2017 02:21 AM, Joonas Lahtinen wrote: On Thu, 2017-12-14 at 20:55 -0800, Yaodong Li wrote: On 12/14/2017 03:43 AM, Joonas Lahtinen wrote: On Wed, 2017-12-13 at 14:59 -0800, Yaodong Li wrote: On 12/13/2017 01:34 PM, Michal Wajdeczko wrote: On Wed, 13 Dec 2017 19:19:06 +0100, Yaodong

[Intel-gfx] [PATCH i-g-t] tests/gem_ctx_param: Update invalid param

Since commit: drm/i915/scheduler: Support user-defined priorities, the driver support an extra context param to set context's priority. Add tests for that interface and update invalid tests. Signed-off-by: Antonio Argenziano Cc: Chris Wilson

[Intel-gfx] ✓ Fi.CI.IGT: success for igt: Exercise creating context with shared GTT

== Series Details == Series: igt: Exercise creating context with shared GTT URL : https://patchwork.freedesktop.org/series/35406/ State : success == Summary == Warning: bzip IGTPW_680/shard-snb5/results13.json.bz2 wasn't in correct JSON format Test gem_exec_suspend: Subgroup

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/trace: add hw_id to gem requests trace points (rev2)

== Series Details == Series: drm/i915/trace: add hw_id to gem requests trace points (rev2) URL : https://patchwork.freedesktop.org/series/35420/ State : success == Summary == Series 35420v2 drm/i915/trace: add hw_id to gem requests trace points

Re: [Intel-gfx] [PATCH igt] igt/perf_pmu: Speed up frequency measurement

On 15/12/2017 17:05, Chris Wilson wrote: Use the normal batch_duration_ns and display the sampled frequency: Frequency: min=100, max=750, boost=750 MHz Min frequency: requested 100.0, actual 100.0 Max frequency: requested 755.6, actual 755.6 Signed-off-by: Chris Wilson

[Intel-gfx] ✗ Fi.CI.BAT: warning for igt/perf_pmu: Speed up frequency measurement

== Series Details == Series: igt/perf_pmu: Speed up frequency measurement URL : https://patchwork.freedesktop.org/series/35429/ State : warning == Summary == IGT patchset tested on top of latest successful build c0be3310715e2f744b892c51f09e62273bcc8e57 tests/kms_frontbuffer_tracking:

Re: [Intel-gfx] [PATCH igt v2 1/4] igt/perf_pmu: Tighten busy measurement

On 15/12/2017 16:10, Chris Wilson wrote: Sleep for a known duration. In particular, CI once saw a measurement for busyness greater than the intended batch_duration! v2: Go back to starting pmu sampling outside of spinner; the GPU should be idle. Bugzilla:

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/userptr: Probe vma range before gup (rev5)

== Series Details == Series: drm/i915/userptr: Probe vma range before gup (rev5) URL : https://patchwork.freedesktop.org/series/35394/ State : success == Summary == Test kms_frontbuffer_tracking: Subgroup fbc-suspend: pass -> INCOMPLETE (shard-hsw) fdo#103540 +2

[Intel-gfx] [PATCH v2] drm/i915/trace: add hw_id to gem requests trace points

When monitoring the GPU with i915 perf, reports are tagged with a hw id. When also tracking the requests using the kernel tracepoints, if we include the hw_id from i915_gem_context, this allows us to correlate a process with hw id fields in the OA reports. v2: Place hw_id at the end of the

[Intel-gfx] [PATCH i-g-t] trace.pl: handle request tracepoint fields regardless of their order

It doesn't look like tracepoint have any guarantee to have always the same ordering of their parameter. Instead of relying on a predefined regexp, let's split the parameters on commas and access the values through a map. Signed-off-by: Lionel Landwerlin ---

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v2,1/4] igt/perf_pmu: Tighten busy measurement

== Series Details == Series: series starting with [v2,1/4] igt/perf_pmu: Tighten busy measurement URL : https://patchwork.freedesktop.org/series/35421/ State : success == Summary == IGT patchset tested on top of latest successful build c0be3310715e2f744b892c51f09e62273bcc8e57

[Intel-gfx] ✗ Fi.CI.BAT: failure for igt/perf_pmu: Measure the reference batch for all-busy-check-all

== Series Details == Series: igt/perf_pmu: Measure the reference batch for all-busy-check-all URL : https://patchwork.freedesktop.org/series/35417/ State : failure == Summary == IGT patchset tested on top of latest successful build c0be3310715e2f744b892c51f09e62273bcc8e57

[Intel-gfx] ✗ Fi.CI.BAT: failure for igt/perf_pmu: Measure the reference batch for busy-check-all

== Series Details == Series: igt/perf_pmu: Measure the reference batch for busy-check-all URL : https://patchwork.freedesktop.org/series/35416/ State : failure == Summary == IGT patchset tested on top of latest successful build c0be3310715e2f744b892c51f09e62273bcc8e57

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Unifying debugfs return codes for unsupported features (rev2)

== Series Details == Series: drm/i915: Unifying debugfs return codes for unsupported features (rev2) URL : https://patchwork.freedesktop.org/series/34552/ State : failure == Summary == Test gem_exec_suspend: Subgroup basic-s3: incomplete -> PASS (shard-hsw)

Re: [Intel-gfx] [PATCH] drm/i915/trace: add hw_id to gem requests trace points

On 15/12/2017 16:18, Lionel Landwerlin wrote: On 15/12/17 16:08, Chris Wilson wrote: Quoting Lionel Landwerlin (2017-12-15 15:51:36) When monitoring the GPU with i915 perf, reports are tagged with a hw id. When also tracking the requests using the kernel tracepoints, if we include the hw_id

[Intel-gfx] ✓ Fi.CI.BAT: success for igt/perf_pmu: Tighten measurements for most-busy

== Series Details == Series: igt/perf_pmu: Tighten measurements for most-busy URL : https://patchwork.freedesktop.org/series/35414/ State : success == Summary == IGT patchset tested on top of latest successful build c0be3310715e2f744b892c51f09e62273bcc8e57 tests/kms_frontbuffer_tracking:

[Intel-gfx] [PATCH igt] igt/perf_pmu: Speed up frequency measurement

Use the normal batch_duration_ns and display the sampled frequency: Frequency: min=100, max=750, boost=750 MHz Min frequency: requested 100.0, actual 100.0 Max frequency: requested 755.6, actual 755.6 Signed-off-by: Chris Wilson Cc: Tvrtko

[Intel-gfx] ✓ Fi.CI.BAT: success for igt/perf_pmu: Tighten busy measurement

== Series Details == Series: igt/perf_pmu: Tighten busy measurement URL : https://patchwork.freedesktop.org/series/35412/ State : success == Summary == IGT patchset tested on top of latest successful build c0be3310715e2f744b892c51f09e62273bcc8e57 tests/kms_frontbuffer_tracking: Correctly

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Check for fused or unused pipes (rev2)

== Series Details == Series: drm/i915: Check for fused or unused pipes (rev2) URL : https://patchwork.freedesktop.org/series/35389/ State : success == Summary == Test kms_frontbuffer_tracking: Subgroup fbc-1p-offscren-pri-shrfb-draw-render: fail -> PASS

Re: [Intel-gfx] [PATCH v2] x86/gpu: add CFL to early quirks

* Lucas De Marchi wrote: > CFL was missing from intel_early_ids[]. The PCI ID needs to be there to > allow the memory region to be stolen, otherwise we could have RAM being > arbitrarily overwritten if for example we keep using the UEFI framebuffer, > depending on how

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/trace: add hw_id to gem requests trace points

== Series Details == Series: drm/i915/trace: add hw_id to gem requests trace points URL : https://patchwork.freedesktop.org/series/35420/ State : success == Summary == Series 35420v1 drm/i915/trace: add hw_id to gem requests trace points

Re: [Intel-gfx] [PATCH] drm/i915/trace: add hw_id to gem requests trace points

On 15/12/17 16:08, Chris Wilson wrote: Quoting Lionel Landwerlin (2017-12-15 15:51:36) When monitoring the GPU with i915 perf, reports are tagged with a hw id. When also tracking the requests using the kernel tracepoints, if we include the hw_id from i915_gem_context, this allows us to

[Intel-gfx] [PATCH igt v2 2/4] igt/perf_pmu: Tighten measurements for most-busy

Create all the spinners before starting the sampler and then measure how long we sleep. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104160 Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin --- tests/perf_pmu.c | 45

[Intel-gfx] [PATCH igt v2 4/4] igt/perf_pmu: Measure the reference batch for all-busy-check-all

Don't rely on the timer being precise when we can sleep for a known duration. Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin --- tests/perf_pmu.c | 38 ++ 1 file changed, 26 insertions(+), 12 deletions(-)

[Intel-gfx] [PATCH igt v2 1/4] igt/perf_pmu: Tighten busy measurement

Sleep for a known duration. In particular, CI once saw a measurement for busyness greater than the intended batch_duration! v2: Go back to starting pmu sampling outside of spinner; the GPU should be idle. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104241 Signed-off-by: Chris Wilson

[Intel-gfx] [PATCH igt v2 3/4] igt/perf_pmu: Measure the reference batch for busy-check-all

Don't rely on the timer being precise when we can sleep for a known duration. Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin --- tests/perf_pmu.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/tests/perf_pmu.c

Re: [Intel-gfx] [PATCH] drm/i915/trace: add hw_id to gem requests trace points

Quoting Lionel Landwerlin (2017-12-15 15:51:36) > When monitoring the GPU with i915 perf, reports are tagged with a hw > id. When also tracking the requests using the kernel tracepoints, if > we include the hw_id from i915_gem_context, this allows us to > correlate a process with hw id fields in

[Intel-gfx] ✓ Fi.CI.BAT: success for igt: Exercise creating context with shared GTT

== Series Details == Series: igt: Exercise creating context with shared GTT URL : https://patchwork.freedesktop.org/series/35406/ State : success == Summary == IGT patchset tested on top of latest successful build c0be3310715e2f744b892c51f09e62273bcc8e57 tests/kms_frontbuffer_tracking:

[Intel-gfx] [PATCH] drm/i915/trace: add hw_id to gem requests trace points

When monitoring the GPU with i915 perf, reports are tagged with a hw id. When also tracking the requests using the kernel tracepoints, if we include the hw_id from i915_gem_context, this allows us to correlate a process with hw id fields in the OA reports. Signed-off-by: Lionel Landwerlin

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/userptr: Probe vma range before gup (rev5)

== Series Details == Series: drm/i915/userptr: Probe vma range before gup (rev5) URL : https://patchwork.freedesktop.org/series/35394/ State : success == Summary == Series 35394v5 drm/i915/userptr: Probe vma range before gup

[Intel-gfx] [PATCH igt] igt/perf_pmu: Measure the reference batch for all-busy-check-all

Don't rely on the timer being precise when we can sleep for a known duration. Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin --- tests/perf_pmu.c | 36 1 file changed, 24 insertions(+), 12 deletions(-)

Re: [Intel-gfx] [PATCH v2] drm/i915: Check for fused or unused pipes

On Fri, 15 Dec 2017, Mika Kahola wrote: > We may have fused or unused pipes in our system. Let's check that the pipe > in question is within limits of accessible pipes. In case, that we are not > able to access the pipe, we return early with a warning. > > v2: Rephrasing of

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Extend CREATE_CONTEXT to allow inheritance ala clone()

== Series Details == Series: drm/i915: Extend CREATE_CONTEXT to allow inheritance ala clone() URL : https://patchwork.freedesktop.org/series/35405/ State : success == Summary == Test gem_tiled_swapping: Subgroup non-threaded: dmesg-warn -> PASS (shard-hsw)

[Intel-gfx] [PATCH igt] igt/perf_pmu: Measure the reference batch for busy-check-all

Don't rely on the timer being precise when we can sleep for a known duration. Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin --- tests/perf_pmu.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/tests/perf_pmu.c

[Intel-gfx] ✓ Fi.CI.IGT: success for kms_sysfs_edid timing and hack to run for BAT

== Series Details == Series: kms_sysfs_edid timing and hack to run for BAT URL : https://patchwork.freedesktop.org/series/35404/ State : success == Summary == Test gem_tiled_swapping: Subgroup non-threaded: dmesg-warn -> PASS (shard-hsw) fdo#104218 +1 Test

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Unifying debugfs return codes for unsupported features (rev2)

== Series Details == Series: drm/i915: Unifying debugfs return codes for unsupported features (rev2) URL : https://patchwork.freedesktop.org/series/34552/ State : success == Summary == Series 34552v2 drm/i915: Unifying debugfs return codes for unsupported features

[Intel-gfx] [PATCH igt] igt/perf_pmu: Tighten measurements for most-busy

Create all the spinners before starting the sampler and then measure how long we sleep. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104160 Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin --- tests/perf_pmu.c | 43

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Check for fused or unused pipes (rev2)

== Series Details == Series: drm/i915: Check for fused or unused pipes (rev2) URL : https://patchwork.freedesktop.org/series/35389/ State : success == Summary == Series 35389v2 drm/i915: Check for fused or unused pipes https://patchwork.freedesktop.org/api/1.0/series/35389/revisions/2/mbox/

[Intel-gfx] [PATCH igt] igt/perf_pmu: Tighten busy measurement

Start the spinner first; before starting the measurement, and sleep for a known duration. In particular, CI once saw a measurement for busyness greater than the intended batch_duration! Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104241 Signed-off-by: Chris Wilson

[Intel-gfx] [PATCH v5] drm/i915/userptr: Probe vma range before gup

We want to exclude any GGTT objects from being present on our internal lists to avoid the deadlock we may run into with our requirement for struct_mutex during invalidate. However, if the gup_fast fails, we put the userptr onto the workqueue and mark it as active, so that we remember to serialise

[Intel-gfx] [PATCH v2] drm/i915: Unifying debugfs return codes for unsupported features

Instead of trying different seq_puts messages, lets use common -ENODEV error code to indicate missing/unsupported feature. v2: don't forget about guc_log_control fops (Sagar) Suggested-by: Chris Wilson Signed-off-by: Michal Wajdeczko Cc:

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/userptr: Probe vma range before gup (rev4)

== Series Details == Series: drm/i915/userptr: Probe vma range before gup (rev4) URL : https://patchwork.freedesktop.org/series/35394/ State : failure == Summary == Test gem_userptr_blits: Subgroup map-fixed-invalidate-overlap-busy-gup: pass -> FAIL

Re: [Intel-gfx] Warning in i915/intel_audio.c

On Fri, 2017-12-15 at 19:20 +0530, Jaswinder Singh Rajput wrote: > On Fri, 2017-12-15 at 14:44 +0200, Mika Kahola wrote: > > > > Hi, > > > > This is a known issue. Could you try out this patch to see if that > > would fix this issue for you? > > > >

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Extend CREATE_CONTEXT to allow inheritance ala clone()

== Series Details == Series: drm/i915: Extend CREATE_CONTEXT to allow inheritance ala clone() URL : https://patchwork.freedesktop.org/series/35405/ State : success == Summary == Series 35405v1 drm/i915: Extend CREATE_CONTEXT to allow inheritance ala clone()

Re: [Intel-gfx] [PATCH] drm/i915/lpe: Remove double-encapsulation of info string

Quoting Pandiyan, Dhinakaran (2017-12-14 22:03:49) > On Wed, 2017-12-13 at 18:28 +, Chris Wilson wrote: > > Just printk the string, or at least do not double up on the newlines! > > > > Reviewed-by: Dhinakaran Pandiyan And pushed, thanks for the review.

[Intel-gfx] [PATCH v2] drm/i915: Check for fused or unused pipes

We may have fused or unused pipes in our system. Let's check that the pipe in question is within limits of accessible pipes. In case, that we are not able to access the pipe, we return early with a warning. v2: Rephrasing of the commit message (Jani) Bugzilla:

[Intel-gfx] ✓ Fi.CI.BAT: success for kms_sysfs_edid timing and hack to run for BAT

== Series Details == Series: kms_sysfs_edid timing and hack to run for BAT URL : https://patchwork.freedesktop.org/series/35404/ State : success == Summary == IGT patchset tested on top of latest successful build c0be3310715e2f744b892c51f09e62273bcc8e57 tests/kms_frontbuffer_tracking:

[Intel-gfx] [PATCH igt] igt: Exercise creating context with shared GTT

Signed-off-by: Chris Wilson Cc: Joonas Lahtinen Cc: Tvrtko Ursulin Cc: Mika Kuoppala --- tests/Makefile.sources | 1 + tests/gem_ctx_shared.c | 294

[Intel-gfx] [RFC] drm/i915: Extend CREATE_CONTEXT to allow inheritance ala clone()

A context encompasses the driver's view of process related state, and encapsulates the logical GPU state where available. Each context is currently equivalent to a process in CPU terms. Like with processes, sometimes the user wants a lighter encapsulation that shares some state with the parent

[Intel-gfx] [PATCH i-g-t v2 2/2] HACK to get kms_sysfs_edid_timing run on more machines

Signed-off-by: Marta Lofstedt --- tests/intel-ci/fast-feedback.testlist | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist index f71a16bc..a6c3f614 100644 ---

[Intel-gfx] [PATCH i-g-t v2 0/2] kms_sysfs_edid timing and hack to run for BAT

It is possoble to get very mysterious results from kms_sysfs_edid timing Since there is no try-bot for IGT I am using IGT PW to get more data. Marta Lofstedt (2): test/kms_sysfs_edid_timing : Increase THRESHOLD_PER_CONNECTOR and THRESHOLD_TOTAL HACK to get kms_sysfs_edid_timing run on

[Intel-gfx] [PATCH i-g-t v2 1/2] test/kms_sysfs_edid_timing : Increase THRESHOLD_PER_CONNECTOR and THRESHOLD_TOTAL

The discussion on how to fix the issues has been stagnant for a long time, see the Bugzilla below and: https://patchwork.freedesktop.org/patch/170429/ After only changing display cable the result of my machine went from always failing to hit a WARN. This is also illustrated on CI-shards, where

Re: [Intel-gfx] [PATCH i-g-t] tests/kms_frontbuffer_tracking: Correctly handle debugfs errors

Quoting Joonas Lahtinen (2017-12-04 10:45:13) > On Tue, 2017-11-28 at 17:29 +, Chris Wilson wrote: > > Quoting Michal Wajdeczko (2017-11-28 17:01:15) > > > In commit 3f6ae7b19 ("igt/kms_frontbuffer_tracking: Keep the debugfs > > > dir around") we introduced custom variant of __igt_debugfs_read

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Ignore TMDS clock limit for DP++ when EDID override is set (rev2)

== Series Details == Series: drm/i915: Ignore TMDS clock limit for DP++ when EDID override is set (rev2) URL : https://patchwork.freedesktop.org/series/35338/ State : success == Summary == Test kms_frontbuffer_tracking: Subgroup fbc-1p-primscrn-cur-indfb-move: pass

  1   2   >