[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/5] drm/i915/gt: Ignore stale context state upon resume

== Series Details == Series: series starting with [1/5] drm/i915/gt: Ignore stale context state upon resume URL : https://patchwork.freedesktop.org/series/71386/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7635 -> Patchwork_15925

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915/gt: Ignore stale context state upon resume

== Series Details == Series: series starting with [1/5] drm/i915/gt: Ignore stale context state upon resume URL : https://patchwork.freedesktop.org/series/71386/ State : warning == Summary == $ dim checkpatch origin/drm-tip f9ba897e2ceb drm/i915/gt: Ignore stale context state upon resume -:7:

[Intel-gfx] [PATCH 4/5] drm/i915/gt: Restore coarse power gating for gen9

Believe in the power of the sacrificial kernel context and restore coarse power gating in the belief that the issue affects only the context idling on another engine -- i.e. only affects our scratch kernel_context. Closes: https://gitlab.freedesktop.org/drm/intel/issues/846 Signed-off-by: Chris Wi

[Intel-gfx] [PATCH 2/5] drm/i915/gt: Discard stale context state from across idling

Before we idle, on parking, we switch to the kernel context such that we have a scratch context loaded while the GPU idle, protecting any precious user state. Be paranoid and assume that the idle state may have been trashed, and reset the kernel_context image after idling. Signed-off-by: Chris Wil

[Intel-gfx] [PATCH 5/5] drm/i915/gt: Apply sanitiization just before resume

Bring sanitization completely underneath the umbrella of intel_gt, and perform it exclusively after suspend and before the next resume. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/gt/intel_gt.c| 2 -- drivers/gpu/drm/i915/gt/intel_gt_pm.c | 15 +++ drivers/gpu/d

[Intel-gfx] [PATCH 1/5] drm/i915/gt: Ignore stale context state upon resume

Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/gt/intel_lrc.c | 10 ++ drivers/gpu/drm/i915/gt/intel_ring_submission.c | 2 +- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c index

[Intel-gfx] [PATCH 3/5] drm/i915/gt: Always poison the kernel_context image before unparking

Keep scrubbing the kernel_context image with poison before we reset it in order to demonstrate that we will be resilient in the case where it is accidentally overwritten on idle. Suggested-by: Imre Deak Signed-off-by: Chris Wilson Cc: Imre Deak --- drivers/gpu/drm/i915/gt/intel_engine_pm.c | 1

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gt: Stop poking at engine->serial at a high level

== Series Details == Series: drm/i915/gt: Stop poking at engine->serial at a high level URL : https://patchwork.freedesktop.org/series/71384/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7634 -> Patchwork_15924 Summary ---

[Intel-gfx] [PATCH] drm/i915/gt: Stop poking at engine->serial at a high level

In record defaults, if we emit a request we expect a context switck on parking. We need take no further action, so don't even mess with the low level engine->serial where it is not warranted. Signed-off-by: Chris Wilson Cc: Andi Shyti --- drivers/gpu/drm/i915/gt/intel_gt.c | 7 +++ 1 file c

Re: [Intel-gfx] [PATCH 0/3] Workaround updates

On 24/12/2019 03:20, Matt Roper wrote: A quick drive-by update for some workarounds I noticed that were added/extended to additional platforms. Cc: Lucas De Marchi Cc: Matt Atwood Cc: Radhakrishna Sripada Matt Roper (3): drm/i915: Extend WaDisableDARBFClkGating to icl,ehl,tgl drm/i915:

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dsb: Increase log level if DSB engine gets busy

== Series Details == Series: drm/i915/dsb: Increase log level if DSB engine gets busy URL : https://patchwork.freedesktop.org/series/71379/ State : success == Summary == CI Bug Log - changes from CI_DRM_7634 -> Patchwork_15923 Summary -

[Intel-gfx] [PATCH] drm/i915/dsb: Increase log level if DSB engine gets busy

Increase the log level if DSB engine gets busy. If dsb engine is busy, it should be an error condition to indicate there might be some difficulty with the hardware. If DSB engine gets busy, load luts will fail and as per current driver design if one instance of DSB engine gets busy, we are not all

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/3] drm/i915/gt: Ignore stale context state upon resume

== Series Details == Series: series starting with [1/3] drm/i915/gt: Ignore stale context state upon resume URL : https://patchwork.freedesktop.org/series/71378/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7634 -> Patchwork_15922

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915/gt: Ignore stale context state upon resume

== Series Details == Series: series starting with [1/3] drm/i915/gt: Ignore stale context state upon resume URL : https://patchwork.freedesktop.org/series/71378/ State : warning == Summary == $ dim checkpatch origin/drm-tip f5a68faf90c3 drm/i915/gt: Ignore stale context state upon resume -:7:

[Intel-gfx] [PATCH 3/3] drm/i915/gt: Restore coarse power gating for gen9

Believe in the power of the sacrificial kernel context and restore coarse power gating in the belief that the issue affects only the context idling on another engine -- i.e. only affects our scratch kernel_context. Closes: https://gitlab.freedesktop.org/drm/intel/issues/846 Signed-off-by: Chris Wi

[Intel-gfx] [PATCH 2/3] drm/i915/gt: Discard stale context state from across idling

Before we idle, on parking, we switch to the kernel context such that we have a scratch context loaded while the GPU idle, protecting any precious user state. Be paranoid and assume that the idle state may have been trashed, and reset the kernel_context image after idling. Signed-off-by: Chris Wil

[Intel-gfx] [PATCH 1/3] drm/i915/gt: Ignore stale context state upon resume

Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/gt/intel_lrc.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c index 4fb70a7716e3..12f5241bf0fa 100644 --- a/drivers/gpu/drm/i915/gt/intel_lrc.c +++ b/drivers/

[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Fix enable OA report logic

== Series Details == Series: drm/i915: Fix enable OA report logic URL : https://patchwork.freedesktop.org/series/71373/ State : failure == Summary == Applying: drm/i915: Fix enable OA report logic Using index info to reconstruct a base tree... M drivers/gpu/drm/i915/i915_perf.c Falling b

[Intel-gfx] [PATCH] drm/i915: Fix enable OA report logic

Clang raises drivers/gpu/drm/i915/i915_perf.c:2474:50: warning: operator '?:' has lower precedence than '|'; '|' will be evaluated first [-Wbitwise-conditional-parentheses] !(stream->sample_flags & SAMPLE_OA_REPORT) ?