[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/mtl: Disable SF round to nearest even

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915/mtl: Disable SF round to nearest even URL : https://patchwork.freedesktop.org/series/122198/ State : warning == Summary == Error: dim checkpatch failed /home/kbuild2/linux/maintainer-tools/dim: line 50: /home/kbuild2/.dimrc: No such file or directory

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/mtl: Disable SF round to nearest even

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915/mtl: Disable SF round to nearest even URL : https://patchwork.freedesktop.org/series/122198/ State : warning == Summary == Error: dim sparse failed /home/kbuild2/linux/maintainer-tools/dim: line 50: /home/kbuild2/.dimrc: No such file or directory

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/mtl: Disable SF round to nearest even

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915/mtl: Disable SF round to nearest even URL : https://patchwork.freedesktop.org/series/122198/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13492 -> Patchwork_122198v1 Summary ---

Re: [Intel-gfx] [PATCH 1/2] drm/i915/display: optimize DP 2.0 sdp split update config

2023-08-09 Thread Govindapillai, Vinod
Hi Jani From: Jani Nikula Sent: Tuesday, August 8, 2023 4:23 PM To: Govindapillai, Vinod ; intel-gfx@lists.freedesktop.org Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/display: optimize DP 2.0 sdp split update config On Fri, 04 Aug 2023, Vinod Govindapillai

[Intel-gfx] [PATCH] drm/i915: Fix mistake in intel_modeset_all_pipes condition

2023-08-09 Thread Stanislav Lisovskiy
It is supposed to be "!intel_crtc_needs_modeset" - otherwise, we are active exactly vice versa for active pipes: skipping if modeset is needed and not skipping if not needed. Signed-off-by: Stanislav Lisovskiy --- drivers/gpu/drm/i915/display/intel_display.c | 2 +- 1 file changed, 1 insertion(+

Re: [Intel-gfx] [PATCH] drm/i915: Fix mistake in intel_modeset_all_pipes condition

2023-08-09 Thread Jani Nikula
On Wed, 09 Aug 2023, Stanislav Lisovskiy wrote: > It is supposed to be "!intel_crtc_needs_modeset" - otherwise, > we are active exactly vice versa for active pipes: skipping if modeset > is needed and not skipping if not needed. If the crtc *already* needs a full modeset, there's no need to force

Re: [Intel-gfx] [PATCH] drm/i915: Fix mistake in intel_modeset_all_pipes condition

2023-08-09 Thread Lisovskiy, Stanislav
On Wed, Aug 09, 2023 at 11:38:08AM +0300, Jani Nikula wrote: > On Wed, 09 Aug 2023, Stanislav Lisovskiy > wrote: > > It is supposed to be "!intel_crtc_needs_modeset" - otherwise, > > we are active exactly vice versa for active pipes: skipping if modeset > > is needed and not skipping if not neede

Re: [Intel-gfx] [PATCH] drm/i915: Fix mistake in intel_modeset_all_pipes condition

2023-08-09 Thread Jani Nikula
On Wed, 09 Aug 2023, "Lisovskiy, Stanislav" wrote: > On Wed, Aug 09, 2023 at 11:38:08AM +0300, Jani Nikula wrote: >> On Wed, 09 Aug 2023, Stanislav Lisovskiy >> wrote: >> > It is supposed to be "!intel_crtc_needs_modeset" - otherwise, >> > we are active exactly vice versa for active pipes: skip

Re: [Intel-gfx] [PATCH] drm/i915: Fix mistake in intel_modeset_all_pipes condition

2023-08-09 Thread Lisovskiy, Stanislav
On Wed, Aug 09, 2023 at 12:01:25PM +0300, Jani Nikula wrote: > On Wed, 09 Aug 2023, "Lisovskiy, Stanislav" > wrote: > > On Wed, Aug 09, 2023 at 11:38:08AM +0300, Jani Nikula wrote: > >> On Wed, 09 Aug 2023, Stanislav Lisovskiy > >> wrote: > >> > It is supposed to be "!intel_crtc_needs_modeset"

Re: [Intel-gfx] [PATCH] drm/i915: Fix mistake in intel_modeset_all_pipes condition

2023-08-09 Thread Jani Nikula
On Wed, 09 Aug 2023, "Lisovskiy, Stanislav" wrote: > On Wed, Aug 09, 2023 at 12:01:25PM +0300, Jani Nikula wrote: >> On Wed, 09 Aug 2023, "Lisovskiy, Stanislav" >> wrote: >> > On Wed, Aug 09, 2023 at 11:38:08AM +0300, Jani Nikula wrote: >> >> On Wed, 09 Aug 2023, Stanislav Lisovskiy >> >> wro

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fix mistake in intel_modeset_all_pipes condition

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915: Fix mistake in intel_modeset_all_pipes condition URL : https://patchwork.freedesktop.org/series/122208/ State : warning == Summary == Error: dim checkpatch failed /home/kbuild/linux/maintainer-tools/dim: line 50: /home/kbuild/.dimrc: No such file or dire

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Fix mistake in intel_modeset_all_pipes condition

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915: Fix mistake in intel_modeset_all_pipes condition URL : https://patchwork.freedesktop.org/series/122208/ State : warning == Summary == Error: dim sparse failed /home/kbuild/linux/maintainer-tools/dim: line 50: /home/kbuild/.dimrc: No such file or director

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix mistake in intel_modeset_all_pipes condition

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915: Fix mistake in intel_modeset_all_pipes condition URL : https://patchwork.freedesktop.org/series/122208/ State : success == Summary == CI Bug Log - changes from CI_DRM_13492 -> Patchwork_122208v1 Summar

[Intel-gfx] [CI 2/3] drm/i915: Don't change the status of forced connectors during hotplug detect

2023-08-09 Thread Imre Deak
DRM display connectors forced to a connected/disconnected state via the drm_connector::force member shouldn't change their status. Atm, this can still happen in the connector's detect function when called to handle a hotplug event. This in turn may lead to the GETCONNECTOR ioctl to report the incor

[Intel-gfx] [CI 3/3] drm/i915: Don't change the status of forced connectors during HPD poll detect

2023-08-09 Thread Imre Deak
As described in the previous patch a connector shouldn't change its status while it's forced to a connected/disconnected state. This can still happen while running the connector detect function to account for lost HPD events in a low-power state. Fix this by reusing the connector detect function w

[Intel-gfx] [CI 1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume

2023-08-09 Thread Imre Deak
The issue fixed in commit a8ddac7c9f06 ("drm/i915: Avoid HPD poll detect triggering a new detect cycle") on VLV, CHV is still present on platforms where the display hotplug detection functionality is available whenever the device is in D0 state (hence these platforms switch to HPD polling only w

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/irq: cleanups (rev2)

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915/irq: cleanups (rev2) URL : https://patchwork.freedesktop.org/series/122165/ State : warning == Summary == Error: dim checkpatch failed /home/kbuild/linux/maintainer-tools/dim: line 50: /home/kbuild/.dimrc: No such file or directory

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/irq: cleanups (rev2)

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915/irq: cleanups (rev2) URL : https://patchwork.freedesktop.org/series/122165/ State : warning == Summary == Error: dim sparse failed /home/kbuild2/linux/maintainer-tools/dim: line 50: /home/kbuild2/.dimrc: No such file or directory

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/irq: cleanups (rev2)

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915/irq: cleanups (rev2) URL : https://patchwork.freedesktop.org/series/122165/ State : success == Summary == CI Bug Log - changes from CI_DRM_13492 -> Patchwork_122165v2 Summary --- **SUCCESS** N

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Test conflict fix for "Fix Wa_22016122933 implementation" (rev5)

2023-08-09 Thread Patchwork
== Series Details == Series: Test conflict fix for "Fix Wa_22016122933 implementation" (rev5) URL : https://patchwork.freedesktop.org/series/122099/ State : warning == Summary == Error: dim checkpatch failed /home/kbuild2/linux/maintainer-tools/dim: line 50: /home/kbuild2/.dimrc: No such file

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Test conflict fix for "Fix Wa_22016122933 implementation" (rev5)

2023-08-09 Thread Patchwork
== Series Details == Series: Test conflict fix for "Fix Wa_22016122933 implementation" (rev5) URL : https://patchwork.freedesktop.org/series/122099/ State : warning == Summary == Error: dim sparse failed /home/kbuild2/linux/maintainer-tools/dim: line 50: /home/kbuild2/.dimrc: No such file or

[Intel-gfx] ✓ Fi.CI.BAT: success for Test conflict fix for "Fix Wa_22016122933 implementation" (rev5)

2023-08-09 Thread Patchwork
== Series Details == Series: Test conflict fix for "Fix Wa_22016122933 implementation" (rev5) URL : https://patchwork.freedesktop.org/series/122099/ State : success == Summary == CI Bug Log - changes from CI_DRM_13492 -> Patchwork_122099v5

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume

2023-08-09 Thread Patchwork
== Series Details == Series: series starting with [CI,1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume URL : https://patchwork.freedesktop.org/series/122218/ State : warning == Summary == Error: dim sparse failed /home/kbuild2/linux/maintainer-tools/dim: line 50: /

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume

2023-08-09 Thread Patchwork
== Series Details == Series: series starting with [CI,1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume URL : https://patchwork.freedesktop.org/series/122218/ State : warning == Summary == Error: dim checkpatch failed /home/kbuild/linux/maintainer-tools/dim: line 50

Re: [Intel-gfx] [PATCH 19/27] KVM: x86/mmu: Use page-track notifiers iff there are external users

2023-08-09 Thread Sean Christopherson
On Wed, Aug 09, 2023, Yan Zhao wrote: > On Mon, Aug 07, 2023 at 10:19:07AM -0700, Sean Christopherson wrote: > > On Mon, Aug 07, 2023, Like Xu wrote: > > > On 23/12/2022 8:57 am, Sean Christopherson wrote: > > > > +static inline void kvm_page_track_write(struct kvm_vcpu *vcpu, gpa_t > > > > gpa, >

Re: [Intel-gfx] [PATCH 1/2] drm/i915: fix display probe for IVB Q and IVB D GT2 server

2023-08-09 Thread Luca Coelho
On Fri, 2023-08-04 at 11:45 +0300, Jani Nikula wrote: > The current display probe is unable to differentiate between IVB Q and > IVB D GT2 server, as they both have the same device id, but different > subvendor and subdevice. This leads to the latter being misidentified as > the former, and should

Re: [Intel-gfx] [PATCH 2/2] drm/i915: debug log when GMD ID indicates there's no display

2023-08-09 Thread Luca Coelho
On Fri, 2023-08-04 at 11:46 +0300, Jani Nikula wrote: > Debug log similar to the device id based identification of no display. > > Signed-off-by: Jani Nikula > --- > drivers/gpu/drm/i915/display/intel_display_device.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume (rev2)

2023-08-09 Thread Patchwork
== Series Details == Series: series starting with [CI,1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume (rev2) URL : https://patchwork.freedesktop.org/series/122218/ State : warning == Summary == Error: dim checkpatch failed /home/kbuild2/linux/maintainer-tools/dim:

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume (rev2)

2023-08-09 Thread Patchwork
== Series Details == Series: series starting with [CI,1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume (rev2) URL : https://patchwork.freedesktop.org/series/122218/ State : warning == Summary == Error: dim sparse failed /home/kbuild/linux/maintainer-tools/dim: line

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume (rev2)

2023-08-09 Thread Patchwork
== Series Details == Series: series starting with [CI,1/3] drm/i915: Avoid endless HPD poll detect loop via runtime suspend/resume (rev2) URL : https://patchwork.freedesktop.org/series/122218/ State : success == Summary == CI Bug Log - changes from CI_DRM_13496 -> Patchwork_122218v2 =

Re: [Intel-gfx] [PATCH v1 3/3] drm/i915/gt: Timeout when waiting for idle in suspending

2023-08-09 Thread Teres Alexis, Alan Previn
Thanks Rodrigo for reviewing this. On Mon, 2023-08-07 at 13:56 -0400, Vivi, Rodrigo wrote: > On Wed, Aug 02, 2023 at 04:35:01PM -0700, Alan Previn wrote: > > When suspending, add a timeout when calling > > intel_gt_pm_wait_for_idle else if we have a lost > > G2H event that holds a wakeref (which w

Re: [Intel-gfx] [PATCH v1 1/3] drm/i915/guc: Flush context destruction worker at suspend

2023-08-09 Thread Teres Alexis, Alan Previn
Thanks Rodrigo for reviewing this. On Mon, 2023-08-07 at 13:52 -0400, Vivi, Rodrigo wrote: > On Wed, Aug 02, 2023 at 04:34:59PM -0700, Alan Previn wrote: > > Suspend is not like reset, it can unroll, so we have to properly > > flush pending context-guc-id deregistrations to complete before > > we

Re: [Intel-gfx] [PATCH 1/2] drm/i915: fix display probe for IVB Q and IVB D GT2 server

2023-08-09 Thread Matt Roper
On Fri, Aug 04, 2023 at 11:45:59AM +0300, Jani Nikula wrote: > The current display probe is unable to differentiate between IVB Q and > IVB D GT2 server, as they both have the same device id, but different > subvendor and subdevice. This leads to the latter being misidentified as > the former, and

[Intel-gfx] [PATCH] drm/i915/display: Dual refresh rate fastset fixes with VRR fastset

2023-08-09 Thread Manasi Navare
Dual refresh rate (DRR) fastset seamlessly lets refresh rate throttle without needing a full modeset. However with the recent VRR fastset patches that got merged this logic was broken. This is broken because now with VRR fastset VRR parameters are calculated by default at the nominal refresh rate s

Re: [Intel-gfx] [PATCH 19/27] KVM: x86/mmu: Use page-track notifiers iff there are external users

2023-08-09 Thread Yan Zhao
On Wed, Aug 09, 2023 at 07:33:45AM -0700, Sean Christopherson wrote: > On Wed, Aug 09, 2023, Yan Zhao wrote: > > On Mon, Aug 07, 2023 at 10:19:07AM -0700, Sean Christopherson wrote: > > > On Mon, Aug 07, 2023, Like Xu wrote: > > > > On 23/12/2022 8:57 am, Sean Christopherson wrote: > > > > > +stati

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: Dual refresh rate fastset fixes with VRR fastset

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915/display: Dual refresh rate fastset fixes with VRR fastset URL : https://patchwork.freedesktop.org/series/122252/ State : warning == Summary == Error: dim checkpatch failed /home/kbuild2/linux/maintainer-tools/dim: line 50: /home/kbuild2/.dimrc: No such fi

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display: Dual refresh rate fastset fixes with VRR fastset

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915/display: Dual refresh rate fastset fixes with VRR fastset URL : https://patchwork.freedesktop.org/series/122252/ State : warning == Summary == Error: dim sparse failed /home/kbuild/linux/maintainer-tools/dim: line 50: /home/kbuild/.dimrc: No such file or

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Dual refresh rate fastset fixes with VRR fastset

2023-08-09 Thread Patchwork
== Series Details == Series: drm/i915/display: Dual refresh rate fastset fixes with VRR fastset URL : https://patchwork.freedesktop.org/series/122252/ State : success == Summary == CI Bug Log - changes from CI_DRM_13496 -> Patchwork_122252v1

Re: [Intel-gfx] [PATCH 19/27] KVM: x86/mmu: Use page-track notifiers iff there are external users

2023-08-09 Thread Yan Zhao
On Thu, Aug 10, 2023 at 07:21:03AM +0800, Yan Zhao wrote: > On Wed, Aug 09, 2023 at 07:33:45AM -0700, Sean Christopherson wrote: > > On Wed, Aug 09, 2023, Yan Zhao wrote: > > > On Mon, Aug 07, 2023 at 10:19:07AM -0700, Sean Christopherson wrote: > > > > On Mon, Aug 07, 2023, Like Xu wrote: > > > >

Re: [Intel-gfx] [PATCH v1 2/3] drm/i915/guc: Close deregister-context race against CT-loss

2023-08-09 Thread Teres Alexis, Alan Previn
On Wed, 2023-08-02 at 16:35 -0700, Teres Alexis, Alan Previn wrote: > If we are at the end of suspend or very early in resume > its possible an async fence signal could lead us to the > execution of the context destruction worker (after the > prior worker flush). > alan:snip > > static void __g

[Intel-gfx] [PULL] drm-misc-fixes

2023-08-09 Thread Maxime Ripard
Hi, Here's this week drm-misc-fixes PR Maxime drm-misc-fixes-2023-08-10: Multiple fixes for nouveau around memory safety and DisplayPort, one fix to reduce the log level of rockchip, a power state fix for the it6505 bridge, a timing fix for the lt9611 bridge, a cache maintenance fix for ivpu and