[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Try to guess PCH type even without ISA bridge

== Series Details == Series: drm/i915: Try to guess PCH type even without ISA bridge URL : https://patchwork.freedesktop.org/series/84886/ State : success == Summary == CI Bug Log - changes from CI_DRM_9478 -> Patchwork_19131 Summary --

[Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915: Try to guess PCH type even without ISA bridge

== Series Details == Series: drm/i915: Try to guess PCH type even without ISA bridge URL : https://patchwork.freedesktop.org/series/84886/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 Error: Cannot open file ./drivers/gpu/drm/i915/gt/intel_lrc.c WARNING: kernel-do

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Try to guess PCH type even without ISA bridge

== Series Details == Series: drm/i915: Try to guess PCH type even without ISA bridge URL : https://patchwork.freedesktop.org/series/84886/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. +drivers/g

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Try to guess PCH type even without ISA bridge

== Series Details == Series: drm/i915: Try to guess PCH type even without ISA bridge URL : https://patchwork.freedesktop.org/series/84886/ State : warning == Summary == $ dim checkpatch origin/drm-tip 17c226d01ecc drm/i915: Try to guess PCH type even without ISA bridge -:93: CHECK:BRACES: brac

[Intel-gfx] [PATCH] drm/i915: Try to guess PCH type even without ISA bridge

From: Zhenyu Wang Some vmm like hyperv and crosvm doesn't supply any ISA bridge to its guest, when igd passthrough is equipped on these vmm, guest i915 display may couldn't work as i915 detects pch type as PCH_NONE. When i915 runs as guest, this patch guess pch type through gpu type even without

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [v5,1/6] drm/damage_helper: Check if damage clips has valid values

== Series Details == Series: series starting with [v5,1/6] drm/damage_helper: Check if damage clips has valid values URL : https://patchwork.freedesktop.org/series/84874/ State : success == Summary == CI Bug Log - changes from CI_DRM_9478_full -> Patchwork_19130_full =

Re: [Intel-gfx] [PATCH 12/20] drm/i915/gt: Track the overall awake/busy time

Quoting Matthew Brost (2020-12-10 17:51:12) > On Mon, Dec 07, 2020 at 07:38:16PM +, Chris Wilson wrote: > > Since we wake the GT up before executing a request, and go to sleep as > > soon as it is retired, the GT wake time not only represents how long the > > device is powered up, but also prov

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v5,1/6] drm/damage_helper: Check if damage clips has valid values

== Series Details == Series: series starting with [v5,1/6] drm/damage_helper: Check if damage clips has valid values URL : https://patchwork.freedesktop.org/series/84874/ State : success == Summary == CI Bug Log - changes from CI_DRM_9478 -> Patchwork_19130 ===

[Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [v5,1/6] drm/damage_helper: Check if damage clips has valid values

== Series Details == Series: series starting with [v5,1/6] drm/damage_helper: Check if damage clips has valid values URL : https://patchwork.freedesktop.org/series/84874/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 Error: Cannot open file ./drivers/gpu/drm/i915/

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v5,1/6] drm/damage_helper: Check if damage clips has valid values

== Series Details == Series: series starting with [v5,1/6] drm/damage_helper: Check if damage clips has valid values URL : https://patchwork.freedesktop.org/series/84874/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't

[Intel-gfx] [PATCH v5 4/6] drm/i915/display: Split and export main surface calculation from skl_check_main_surface()

The calculation the offsets of the main surface will be needed by PSR2 selective fetch code so here splitting and exporting it. No functional changes were done here. v3: Rebased Cc: Gwan-gyeong Mun Cc: Ville Syrjälä Signed-off-by: José Roberto de Souza Reviewed-by: Gwan-gyeong Mun Tested-by:

[Intel-gfx] [PATCH v5 6/6] HAX/DO_NOT_MERGE_IT: drm/i915/display: Enable PSR2 selective fetch for testing

Enabling it to check if it causes regressions in CI but the feature is still not ready to be enabled by default. Signed-off-by: José Roberto de Souza --- drivers/gpu/drm/i915/i915_params.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/i915_params.h b/d

[Intel-gfx] [PATCH v5 5/6] drm/i915/display/psr: Program plane's calculated offset to plane SF register

It programs Plane's calculated x, y, offset to Plane SF register. It does the calculation of x and y offsets using skl_calc_main_surface_offset(). v3: Update commit message Cc: Gwan-gyeong Mun Cc: Ville Syrjälä Signed-off-by: José Roberto de Souza Reviewed-by: Gwan-gyeong Mun Tested-by: Gwan-

[Intel-gfx] [PATCH v5 3/6] drm/i915/display/psr: Use plane damage clips to calculate damaged area

Now using plane damage clips property to calcualte the damaged area. Selective fetch only supports one region to be fetched so software needs to calculate a bounding box around all damage clips. Now that we are not complete fetching each plane, there is another loop needed as all the plane areas t

[Intel-gfx] [PATCH v5 2/6] drm/i915/display: Check plane damage clips

Call the function that validates every damage clips of each plane. As in commit 093a3a39 ("drm/i915: Add plane damage clips property") this property was only enabled for gen12+ only checking it for gen12 too. v2: - add logs to underspace understand why commit was rejected Cc: Gwan-gyeong Mun

[Intel-gfx] [PATCH v5 1/6] drm/damage_helper: Check if damage clips has valid values

Userspace can set a damage clip with a negative coordinate, negative width or height or larger than the plane. This invalid values could cause issues in some HW or even worst enable security flaws. v2: - add debug messages to let userspace know why atomic commit failed due invalid damage clips Cc

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/damage_helper: Check if damage clips has valid values

== Series Details == Series: drm/damage_helper: Check if damage clips has valid values URL : https://patchwork.freedesktop.org/series/84871/ State : success == Summary == CI Bug Log - changes from CI_DRM_9478 -> Patchwork_19128 Summary

[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/damage_helper: Check if damage clips has valid values (rev2)

== Series Details == Series: drm/damage_helper: Check if damage clips has valid values (rev2) URL : https://patchwork.freedesktop.org/series/84871/ State : failure == Summary == Applying: drm/damage_helper: Check if damage clips has valid values error: patch failed: drivers/gpu/drm/drm_damage_

Re: [Intel-gfx] [PATCH] drm/damage_helper: Check if damage clips has valid values

On Sun, 2020-12-13 at 17:22 +, Simon Ser wrote: > Can you add some drm_dbg_atomic logs when the damage is invalid, to make it > easier for user-space to understand why an atomic commit failed? sure, this is enough? will wait for a couple of more days before send another version. diff --git

Re: [Intel-gfx] [PATCH] drm/damage_helper: Check if damage clips has valid values

Can you add some drm_dbg_atomic logs when the damage is invalid, to make it easier for user-space to understand why an atomic commit failed? ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gf

[Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/damage_helper: Check if damage clips has valid values

== Series Details == Series: drm/damage_helper: Check if damage clips has valid values URL : https://patchwork.freedesktop.org/series/84871/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 Error: Cannot open file ./drivers/gpu/drm/i915/gt/intel_lrc.c WARNING: kernel-

[Intel-gfx] [PATCH] drm/damage_helper: Check if damage clips has valid values

Userspace can set a damage clip with a negative coordinate, negative width or height or larger than the plane. This invalid values could cause issues in some HW or even worst enable security flaws. Cc: Gwan-gyeong Mun Cc: Sean Paul Cc: Fabio Estevam Cc: Deepak Rawat Cc: dri-de...@lists.freedes

[Intel-gfx] [PATCH i-g-t] i915/gem_exec_balancer: Measure timeslicing fairness

Oversaturate the virtual engines on the system and check that each workload receives a fair share of the available GPU time. Signed-off-by: Chris Wilson --- tests/i915/gem_exec_balancer.c | 154 + 1 file changed, 154 insertions(+) diff --git a/tests/i915/gem_exec