[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display: Audio keep alive timestamp cdclk divisors

== Series Details == Series: drm/i915/display: Audio keep alive timestamp cdclk divisors URL : https://patchwork.freedesktop.org/series/106630/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_106630v1_full =

Re: [Intel-gfx] [PATCH v3 00/10] Update vfio_pin/unpin_pages API

On Fri, 22 Jul 2022 17:38:25 -0700 Nicolin Chen wrote: > On Fri, Jul 22, 2022 at 06:18:00PM -0600, Alex Williamson wrote: > > External email: Use caution opening links or attachments > > > > > > On Fri, 22 Jul 2022 16:12:19 -0700 > > Nicolin Chen wrote: > > > > > On Fri, Jul 22, 2022 at 04:

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Audio keep alive timestamp cdclk divisors

== Series Details == Series: drm/i915/display: Audio keep alive timestamp cdclk divisors URL : https://patchwork.freedesktop.org/series/106630/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935 -> Patchwork_106630v1 Summa

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display: Audio keep alive timestamp cdclk divisors

== Series Details == Series: drm/i915/display: Audio keep alive timestamp cdclk divisors URL : https://patchwork.freedesktop.org/series/106630/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: Audio keep alive timestamp cdclk divisors

== Series Details == Series: drm/i915/display: Audio keep alive timestamp cdclk divisors URL : https://patchwork.freedesktop.org/series/106630/ State : warning == Summary == Error: dim checkpatch failed d163202db0cc drm/i915/display: Audio keep alive timestamp cdclk divisors -:103: WARNING:LON

[Intel-gfx] [PATCH] drm/i915/display: Audio keep alive timestamp cdclk divisors

Use BSPEC values for the Audio Keep alive M and N values as included in the cdclk BSPEC pages for display > 13 BSPEC: 54034, 55409 Cc: Kai Vehmanen Cc: Uma Shankar Cc: Ville Syrjälä Signed-off-by: Taylor, Clinton A --- drivers/gpu/drm/i915/display/intel_audio.c | 23 +-- drivers/gpu/drm/i

Re: [Intel-gfx] [PATCH v3 00/10] Update vfio_pin/unpin_pages API

On Fri, 22 Jul 2022 16:12:19 -0700 Nicolin Chen wrote: > On Fri, Jul 22, 2022 at 04:11:29PM -0600, Alex Williamson wrote: > > > GVT-g explodes for me with this series on my Broadwell test system, > > continuously spewing the following: > > Thank you for running additional tests. > > > [ 47

Re: [Intel-gfx] [PATCH v4 12/41] dyndbg: add DECLARE_DYNDBG_CLASSMAP

On Fri, Jul 22, 2022 at 2:23 PM Jason Baron wrote: > > > > On 7/20/22 11:32, Jim Cromie wrote: > > DECLARE_DYNDBG_CLASSMAP lets modules declare a set of classnames, this > > opt-in authorizes dyndbg to allow enabling of prdbgs by their class: > > > >:#> echo class DRM_UT_KMS +p > /proc/dynamic

Re: [Intel-gfx] [PATCH v4 0/2] Remove the VFIO_IOMMU_NOTIFY_DMA_UNMAP notifier

On Tue, 19 Jul 2022 21:02:47 -0300 Jason Gunthorpe wrote: > This is the last notifier toward the drivers, replace it with a simple op > callback in the vfio_device_ops. > > v4: > - Rebase over the CCW series > v3: > https://lore.kernel.org/r/0-v3-7593f297c43f+56ce-vfio_unmap_notif_...@nvidia.c

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftests: Increase delay for RPS test (rev2)

== Series Details == Series: drm/i915/selftests: Increase delay for RPS test (rev2) URL : https://patchwork.freedesktop.org/series/106277/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_106277v2_full

Re: [Intel-gfx] [PATCH v3 00/10] Update vfio_pin/unpin_pages API

On Fri, 8 Jul 2022 15:44:18 -0700 Nicolin Chen wrote: > This is a preparatory series for IOMMUFD v2 patches. It prepares for > replacing vfio_iommu_type1 implementations of vfio_pin/unpin_pages() > with IOMMUFD version. > > There's a gap between these two versions: the vfio_iommu_type1 version >

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display: stop HPD workers before display driver unregister (rev13)

== Series Details == Series: drm/i915/display: stop HPD workers before display driver unregister (rev13) URL : https://patchwork.freedesktop.org/series/105557/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_105557v13_full ===

Re: [Intel-gfx] [PATCH 06/12] drm/i915/guc: Use streaming loads to speed up dumping the guc log

On 7/12/2022 16:31, john.c.harri...@intel.com wrote: From: Chris Wilson Use a temporary page and mempy_from_wc to reduce the time it takes to dump the guc log to debugfs. Signed-off-by: Chris Wilson Reviewed-by: John Harrison --- drivers/gpu/drm/i915/gt/uc/intel_guc_log.c | 24 +

Re: [Intel-gfx] [PATCH 10/12] drm/i915/guc: Support larger contexts on newer hardware

On 7/19/2022 02:56, Tvrtko Ursulin wrote: On 19/07/2022 01:13, John Harrison wrote: On 7/18/2022 05:35, Tvrtko Ursulin wrote: On 13/07/2022 00:31, john.c.harri...@intel.com wrote: From: Matthew Brost The GuC needs a copy of a golden context for implementing watchdog resets (aka media resets

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/guc: Check for ct enabled while waiting for response (rev3)

== Series Details == Series: drm/i915/guc: Check for ct enabled while waiting for response (rev3) URL : https://patchwork.freedesktop.org/series/105258/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_105258v3_full

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev3)

On 22/07/2022 19:05, Patchwork wrote: *Patch Details* *Series:* drm/i915: stop using swiotlb (rev3) *URL:* https://patchwork.freedesktop.org/series/106589/ *State:*failure *Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Pa

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Increase delay for RPS test (rev2)

== Series Details == Series: drm/i915/selftests: Increase delay for RPS test (rev2) URL : https://patchwork.freedesktop.org/series/106277/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935 -> Patchwork_106277v2 Summary --

Re: [Intel-gfx] [PATCH 01/12] drm/i915: Remove bogus GEM_BUG_ON in unpark

On 7/21/2022 02:24, Tvrtko Ursulin wrote: On 21/07/2022 01:54, John Harrison wrote: On 7/19/2022 02:42, Tvrtko Ursulin wrote: On 19/07/2022 01:05, John Harrison wrote: On 7/18/2022 05:15, Tvrtko Ursulin wrote: On 13/07/2022 00:31, john.c.harri...@intel.com wrote: From: Matthew Brost Remov

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev3)

== Series Details == Series: drm/i915: stop using swiotlb (rev3) URL : https://patchwork.freedesktop.org/series/106589/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_106589v3_full Summary ---

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: stop HPD workers before display driver unregister (rev13)

== Series Details == Series: drm/i915/display: stop HPD workers before display driver unregister (rev13) URL : https://patchwork.freedesktop.org/series/105557/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935 -> Patchwork_105557v13 =

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display: stop HPD workers before display driver unregister (rev13)

== Series Details == Series: drm/i915/display: stop HPD workers before display driver unregister (rev13) URL : https://patchwork.freedesktop.org/series/105557/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Check for ct enabled while waiting for response (rev3)

== Series Details == Series: drm/i915/guc: Check for ct enabled while waiting for response (rev3) URL : https://patchwork.freedesktop.org/series/105258/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935 -> Patchwork_105258v3 ==

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: stop using swiotlb (rev3)

== Series Details == Series: drm/i915: stop using swiotlb (rev3) URL : https://patchwork.freedesktop.org/series/106589/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935 -> Patchwork_106589v3 Summary --- **SUCCESS*

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: stop using swiotlb (rev3)

== Series Details == Series: drm/i915: stop using swiotlb (rev3) URL : https://patchwork.freedesktop.org/series/106589/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: stop using swiotlb (rev2)

== Series Details == Series: drm/i915: stop using swiotlb (rev2) URL : https://patchwork.freedesktop.org/series/106589/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935 -> Patchwork_106589v2 Summary --- **SUCCESS*

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: stop using swiotlb (rev2)

== Series Details == Series: drm/i915: stop using swiotlb (rev2) URL : https://patchwork.freedesktop.org/series/106589/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/display: stop HPD workers before display driver unregister (rev12)

== Series Details == Series: drm/i915/display: stop HPD workers before display driver unregister (rev12) URL : https://patchwork.freedesktop.org/series/105557/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_105557v12_full ===

[Intel-gfx] [PATCH v3] drm/i915: stop using swiotlb

Calling swiotlb functions directly is nowadays considered harmful. See https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/ Replace swiotlb_max_segment() calls with dma_max_mapping_size(). In i915_gem_object_get_pages_internal() no longer consider max_segment only if CONFIG_SWIOTLB is

Re: [Intel-gfx] [PATCH v2] drm/i915: stop using swiotlb

On 22/07/2022 16:03, Christoph Hellwig wrote: + return max_t(size_t, UINT_MAX, dma_max_mapping_size(dev)); Shouldn't this be a min? eugh! yes. Stand by for v3

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/hdmi: Prune modes that require HDMI2.1 FRL (rev3)

== Series Details == Series: drm/i915/hdmi: Prune modes that require HDMI2.1 FRL (rev3) URL : https://patchwork.freedesktop.org/series/106011/ State : success == Summary == CI Bug Log - changes from CI_DRM_11933_full -> Patchwork_106011v3_full ==

Re: [Intel-gfx] [PATCH v2] drm/i915: stop using swiotlb

> + return max_t(size_t, UINT_MAX, dma_max_mapping_size(dev)); Shouldn't this be a min?

[Intel-gfx] [PATCH v2] drm/i915: stop using swiotlb

Calling swiotlb functions directly is nowadays considered harmful. See https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/ Replace swiotlb_max_segment() calls with dma_max_mapping_size(). In i915_gem_object_get_pages_internal() no longer consider max_segment only if CONFIG_SWIOTLB is

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: stop HPD workers before display driver unregister (rev12)

== Series Details == Series: drm/i915/display: stop HPD workers before display driver unregister (rev12) URL : https://patchwork.freedesktop.org/series/105557/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935 -> Patchwork_105557v12 =

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display: stop HPD workers before display driver unregister (rev12)

== Series Details == Series: drm/i915/display: stop HPD workers before display driver unregister (rev12) URL : https://patchwork.freedesktop.org/series/105557/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately

[Intel-gfx] [PATCH v6 4/4] drm/i915/fbdev: do not create fbdev if HPD is suspended

In case of deferred FB setup core can try to create new framebuffer. Disallow it if hpd_suspended flag is set. Signed-off-by: Andrzej Hajda --- drivers/gpu/drm/i915/display/intel_fbdev.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/gpu/drm/i915/display/intel_fbdev.c b/drive

[Intel-gfx] [PATCH v6 2/4] drm/i915/fbdev: suspend HPD before fbdev unregistration

HPD event after fbdev unregistration can cause registration of deferred fbdev which will not be unregistered later, causing use-after-free. To avoid it HPD handling should be suspended before fbdev unregistration. It should fix following GPF: [272.634530] general protection fault, probably for non

[Intel-gfx] [PATCH v6 1/4] drm/i915/hpd: postpone HPD cancel work after last user suspension

i915->hotplug.dig_port_work can be queued from intel_hpd_irq_handler called by IRQ handler or by intel_hpd_trigger_irq called from dp_mst. Since dp_mst is suspended after irq handler uninstall, a cleaner approach is to cancel hpd work after intel_dp_mst_suspend, otherwise we risk use-after-free. I

[Intel-gfx] [PATCH v6 3/4] drm/i915/display: add hotplug.suspended flag

HPD events during driver removal can be generated by hardware and software frameworks - drm_dp_mst, the former we can avoid by disabling interrupts, the latter can be triggered by any drm_dp_mst transaction, and this is too late. Introducing suspended flag allows to solve this chicken-egg problem.

[Intel-gfx] [PATCH v6 0/4] drm/i915/display: stop HPD workers before display driver unregister

Hi Jani, Ville, Arun, This patchset is replacement of patch "drm/i915/display: disable HPD workers before display driver unregister" [1]. Ive decided to split patch into two parts - fbdev and MST, there are different issues. Ive also dropped shutdown path, as it has slightly different requirements

Re: [Intel-gfx] [PATCH v2 08/21] drm/i915/gt: Move TLB invalidation to its own file

Hi Mauro, On Thu, Jul 14, 2022 at 01:06:13PM +0100, Mauro Carvalho Chehab wrote: > From: Chris Wilson > > Prepare for supporting more TLB invalidation scenarios by moving > the current MMIO invalidation to its own file. > > Signed-off-by: Chris Wilson > Cc: Fei Yang > Signed-off-by: Mauro Car

Re: [Intel-gfx] [PATCH v2 05/21] drm/i915/gt: Skip TLB invalidations once wedged

Hi Mauro, On Thu, Jul 14, 2022 at 01:06:10PM +0100, Mauro Carvalho Chehab wrote: > From: Chris Wilson > > Skip all further TLB invalidations once the device is wedged and > had been reset, as, on such cases, it can no longer process instructions > on the GPU and the user no longer has access to

Re: [Intel-gfx] [PATCH v2 04/21] drm/i915/gt: Only invalidate TLBs exposed to user manipulation

Hi Mauro, On Thu, Jul 14, 2022 at 01:06:09PM +0100, Mauro Carvalho Chehab wrote: > From: Chris Wilson > > Don't flush TLBs when the buffer is only used in the GGTT under full > control of the kernel, as there's no risk of concurrent access > and stale access from prefetch. > > We only need to i

Re: [Intel-gfx] [PATCH v2 03/21] drm/i915/gt: Invalidate TLB of the OA unit at TLB invalidations

Hi Mauro and Chris, On Thu, Jul 14, 2022 at 01:06:08PM +0100, Mauro Carvalho Chehab wrote: > From: Chris Wilson > > Ensure that the TLB of the OA unit is also invalidated > on gen12 HW, as just invalidating the TLB of an engine is not > enough. > > Cc: sta...@vger.kernel.org > Fixes: 7938d61591

Re: [Intel-gfx] [PATCH v2 01/21] drm/i915/gt: Ignore TLB invalidations on idle engines

Hi Mauro, On Thu, Jul 14, 2022 at 01:06:06PM +0100, Mauro Carvalho Chehab wrote: > From: Chris Wilson > > Check if the device is powered down prior to any engine activity, > as, on such cases, all the TLBs were already invalidated, so an > explicit TLB invalidation is not needed, thus reducing t

Re: [Intel-gfx] [PATCH] drm/i915: stop using swiotlb

On 22/07/2022 10:58, Christoph Hellwig wrote: On Fri, Jul 22, 2022 at 10:45:54AM +0100, Tvrtko Ursulin wrote: - unsigned int size = swiotlb_max_segment(); - - if (size == 0) - size = UINT_MAX; On a more detailed look, there was a CI failure which makes me think thi

Re: [Intel-gfx] [PATCH] drm/i915: stop using swiotlb

On Fri, Jul 22, 2022 at 10:13:48AM +0100, Tvrtko Ursulin wrote: > Christoph - ack from you? Also, if we merge it via the normal process it > will hit 5.21 only. Does that work for you? While I'd like to kill off swiotlb_max_segment rather sooner than later I'm fine with following the normal proce

Re: [Intel-gfx] [PATCH] drm/i915: stop using swiotlb

On Fri, Jul 22, 2022 at 10:45:54AM +0100, Tvrtko Ursulin wrote: >> -unsigned int size = swiotlb_max_segment(); >> - >> -if (size == 0) >> -size = UINT_MAX; > > On a more detailed look, there was a CI failure which makes me think this > cap might need to stay. Because max sg seg

Re: [Intel-gfx] [PATCH] drm/i915: stop using swiotlb

On Thu, Jul 21, 2022 at 06:43:07PM +0100, Robert Beckett wrote: > + max_segment = dma_max_mapping_size(i915->drm.dev); > + max_segment = max_t(size_t, max_segment, PAGE_SIZE) >> PAGE_SHIFT; dma_max_mapping_size is always larger than PAGE_SIZE, so I don't think the max is needed. Otherwise

[Intel-gfx] ✓ Fi.CI.IGT: success for Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation (rev9)

== Series Details == Series: Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation (rev9) URL : https://patchwork.freedesktop.org/series/104704/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935_full -> Patchwo

Re: [Intel-gfx] [PATCH] drm/i915: stop using swiotlb

On 21/07/2022 18:43, Robert Beckett wrote: Calling swiotlb functions directly is nowadays considered harmful. See https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/ Replace swiotlb_max_segment() calls with dma_max_mapping_size(). In i915_gem_object_get_pages_internal() no longer

Re: [Intel-gfx] [PATCH] drm/i915: stop using swiotlb

On 21/07/2022 18:43, Robert Beckett wrote: Calling swiotlb functions directly is nowadays considered harmful. See https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/ Replace swiotlb_max_segment() calls with dma_max_mapping_size(). In i915_gem_object_get_pages_internal() no longer

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when turn full plane off (rev2)

== Series Details == Series: drm/i915: clear plane color ctl setting when turn full plane off (rev2) URL : https://patchwork.freedesktop.org/series/106292/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11935 -> Patchwork_106292v2 ===

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/drm_edid: Refactor HFVSDB parsing for DSC1.2

== Series Details == Series: drm/drm_edid: Refactor HFVSDB parsing for DSC1.2 URL : https://patchwork.freedesktop.org/series/106602/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_106602v1_full Summar

[Intel-gfx] ✓ Fi.CI.BAT: success for Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation (rev9)

== Series Details == Series: Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation (rev9) URL : https://patchwork.freedesktop.org/series/104704/ State : success == Summary == CI Bug Log - changes from CI_DRM_11935 -> Patchwork_10

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation (rev9)

== Series Details == Series: Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation (rev9) URL : https://patchwork.freedesktop.org/series/104704/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast m

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation (rev9)

== Series Details == Series: Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation (rev9) URL : https://patchwork.freedesktop.org/series/104704/ State : warning == Summary == Error: dim checkpatch failed 44e2cc835627 drm: Move an

[Intel-gfx] [v2] drm/i915/display: clear plane color ctl setting when turn full plane off

Customer report abnormal display output while switch eDP off sometimes. In current display disable flow, plane will be off at first. Then turn eDP off and disable HW pipe line. We found the abnormal pixel comes after turn plane off. Clear plane color ctl register when driver disable plane can solve