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

Hi, Here's this week drm-misc-next PR Maxime drm-misc-next-2022-04-21: drm-misc-next for $kernel-version: UAPI Changes: Cross-subsystem Changes: - of: Create a platform_device for offb Core Changes: - edid: block read refactoring - ttm: Add common debugfs code for resource managers Dri

Re: [Intel-gfx] [PATCH 1/2] drm/i915/selftests: fixup min_alignment usage

Reviewed-by: Nirmoy Das On 4/6/2022 9:30 PM, Matthew Auld wrote: Trying to cast the region id into the region type doesn't work too well, since the i915_vm_min_alignment() won't give us the correct value for the stolen-lmem case. Signed-off-by: Matthew Auld Cc: Thomas Hellström Cc: Nirmoy Da

Re: [Intel-gfx] [PATCH 2/2] drm/i915/selftests: tweak the misaligned_case

LGTM Reviewed-by: Nirmoy Das On 4/6/2022 9:30 PM, Matthew Auld wrote: The compact-pt layout restrictions should only apply to the ppGTT. Also make this play nice on platforms that only have the 64K GTT restriction, and not the compact-pt thing. Signed-off-by: Matthew Auld Cc: Thomas Hellström

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [CI,1/4] drm/i915: consider min_page_size when migrating

On 21/04/2022 02:30, Patchwork wrote: *Patch Details* *Series:* series starting with [CI,1/4] drm/i915: consider min_page_size when migrating *URL:* https://patchwork.freedesktop.org/series/102879/ *State:*failure *Details:* https://i

Re: [Intel-gfx] [CI 3/4] drm/i915/selftests: fixup min_alignment usage

On 2022-04-20 at 19:16:12 +0100, Matthew Auld wrote: > Trying to cast the region id into the region type doesn't work too well, > since the i915_vm_min_alignment() won't give us the correct value for > the stolen-lmem case. > > Signed-off-by: Matthew Auld Looks good to me. Reviewed-by: Ramalinga

Re: [Intel-gfx] [CI 4/4] drm/i915/selftests: tweak the misaligned_case

On 2022-04-20 at 19:16:13 +0100, Matthew Auld wrote: > The compact-pt layout restrictions should only apply to the ppGTT. Also > make this play nice on platforms that only have the 64K GTT restriction, > and not the compact-pt thing. > > Signed-off-by: Matthew Auld > Cc: Thomas Hellström > Cc: N

[Intel-gfx] ✗ Fi.CI.BUILD: failure for RFCv2: nested AVIC

== Series Details == Series: RFCv2: nested AVIC URL : https://patchwork.freedesktop.org/series/102905/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/102905/revisions/1/mbox/ not applied Applying: KVM: x86: mmu: allow to enable write tracking exte

Re: [Intel-gfx] PR for new GuC v70.1.1

Pulled and pushed out. josh On Tue, Apr 19, 2022 at 7:46 PM wrote: > > The following changes since commit 681281e49fb6778831370e5d94e6e1d97f0752d6: > > amdgpu: update PSP 13.0.8 firmware (2022-03-18 07:35:54 -0400) > > are available in the Git repository at: > > git://anongit.freedesktop.org

[Intel-gfx] [PATCH 0/4] Flat-CCS eviction enhancements

Flat-CCS eviction enhancements. Ramalingam C (4): drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking drm/i915/gt: optimize the ccs_sz calculation per chunk drm/i915/gt: Extend doc on Flat-CCS obj eviction uapi/drm/i915: Update the placement list impact on obj residency driver

[Intel-gfx] [PATCH 1/4] drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking

While locating the start of ccs scatterlist in smem scatterlist, that has to be the size of lmem obj size + corresponding ccs data size. Report bug if scatterlist terminate before that length. Signed-off-by: Ramalingam C --- drivers/gpu/drm/i915/gt/intel_migrate.c | 6 ++ 1 file changed, 6 i

[Intel-gfx] [PATCH 0/4] Flat-CCS eviction enhancements

Flat-CCS eviction enhancements. Ramalingam C (4): drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking drm/i915/gt: optimize the ccs_sz calculation per chunk drm/i915/gt: Extend doc on Flat-CCS obj eviction uapi/drm/i915: Update the placement list impact on obj residency driver

[Intel-gfx] [PATCH 3/4] drm/i915/gt: Extend doc on Flat-CCS obj eviction

Capture the eviction details for Flat-CCS capable lmem only objects and lmem objects with smem residency. This also captures the impact of eviction on object's memory residency and Flat-CCS compression state. Signed-off-by: Ramalingam C --- drivers/gpu/drm/i915/gt/intel_migrate.c | 36 +

[Intel-gfx] [PATCH 2/4] drm/i915/gt: optimize the ccs_sz calculation per chunk

Calculate the ccs_sz that needs to be emitted based on the src and dst pages emitted per chunk. And handle the return value of emit_pte for the ccs pages. Signed-off-by: Ramalingam C --- drivers/gpu/drm/i915/gt/intel_migrate.c | 36 + 1 file changed, 12 insertions(+), 24

[Intel-gfx] [PATCH 4/4] uapi/drm/i915: Update the placement list impact on obj residency

Object created with list of memory classes as placement preferences, can be backed with any memory class of the list as per kernel's migration policy for the memory contrain situation. Userspace won't be notified of the memory residency change at this scenario. And also Flat-CCS compression is sup

Re: [Intel-gfx] [PATCH 1/2] drm/i915/display/drrs: Split the DRRS status per connector

On Mon, Apr 18, 2022 at 01:52:20PM -0700, José Roberto de Souza wrote: > Instead of keep the DRRS status of all connectors/pipe into a single > i915_drrs_status what makes user-space parsing terrible moving > each eDP connector status to its own folder. > > As legacy support still returning the DR

[Intel-gfx] [PATCH xf86-video-intel 1/3] sna: Don't emit sse2 code where not wanted

From: Ville Syrjälä Fix the s/push_options/pop_options/ pragma so that we don't emit sse2 in the codepaths that run on non-sse2 machines as well. Seems gcc has become much more aggressive in its sse2 usage recently and I'm now hitting sse2 instructions in choose_memcpy_tiled_x() on my non-sse2 P3

[Intel-gfx] [PATCH xf86-video-intel 2/3] sna: Dump fences also on -ENOBUFS

From: Ville Syrjälä Since kernel commit 78d2ad7eb4e1 ("drm/i915/gt: Fix -EDEADLK handling regression") running out of fences will result in -ENOBUFS instead of -EDEADLK (the latter having been stolen by ww mutextes for their internal use). Adjust the fence dumping to expect either errno value. S

[Intel-gfx] [PATCH xf86-video-intel 3/3] sna: Eliminate sna_mode_wants_tear_free()

From: Ville Syrjälä The modparam checks performed by sna_mode_wants_tear_free() don't generally work when the server is running as a regular user. Hence we can't rely on them to indicate whether FBC/PSR/etc is enabled. Also the "Panel Self-Refresh" connector property doesn't actually exist so we

Re: [Intel-gfx] [PATCH 1/2] drm/i915/display/drrs: Split the DRRS status per connector

On Thu, 2022-04-21 at 15:17 +0300, Ville Syrjälä wrote: > On Mon, Apr 18, 2022 at 01:52:20PM -0700, José Roberto de Souza wrote: > > Instead of keep the DRRS status of all connectors/pipe into a single > > i915_drrs_status what makes user-space parsing terrible moving > > each eDP connector status

Re: [Intel-gfx] [PATCH 1/4] drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking

On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > While locating the start of ccs scatterlist in smem scatterlist, that > has > to be the size of lmem obj size + corresponding ccs data size. Report > bug > if scatterlist terminate before that length. > > Signed-off-by: Ramalingam C > --- >

Re: [Intel-gfx] [PATCH 3/4] drm/i915/gt: Extend doc on Flat-CCS obj eviction

On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > Capture the eviction details for Flat-CCS capable lmem only objects > and > lmem objects with smem residency. This also captures the impact of > eviction on  object's memory residency and Flat-CCS compression > state. > > Signed-off-by: Rama

Re: [Intel-gfx] [PATCH 4/4] uapi/drm/i915: Update the placement list impact on obj residency

On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > Object created with list of memory classes as placement preferences, > can > be backed with any memory class of the list as per kernel's migration > policy for the memory contrain situation. Userspace won't be notified > of > the memory resid

Re: [Intel-gfx] [PATCH 1/2] drm/i915/display/drrs: Split the DRRS status per connector

On Thu, Apr 21, 2022 at 01:18:17PM +, Souza, Jose wrote: > On Thu, 2022-04-21 at 15:17 +0300, Ville Syrjälä wrote: > > On Mon, Apr 18, 2022 at 01:52:20PM -0700, José Roberto de Souza wrote: > > > Instead of keep the DRRS status of all connectors/pipe into a single > > > i915_drrs_status what ma

Re: [Intel-gfx] [PATCH 1/4] drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking

On 2022-04-21 at 18:57:59 +0530, Hellstrom, Thomas wrote: > On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > > While locating the start of ccs scatterlist in smem scatterlist, that > > has > > to be the size of lmem obj size + corresponding ccs data size. Report > > bug > > if scatterlist t

Re: [Intel-gfx] [PATCH v2] drm/i915: Check EDID for HDR static metadata when choosing blc

On Thu, Apr 14, 2022 at 04:44:13PM -0400, Lyude Paul wrote: > Reviewed-by: Lyude Paul Thanks for the patch and review. Pushed to drm-intel-next. > > On Wed, 2022-04-13 at 11:28 +0300, Jouni Högander wrote: > > We have now seen panel (XMG Core 15 e21 laptop) advertizing support > > for Intel pro

Re: [Intel-gfx] [PULL v2] gvt-next

On 4/21/22 1:14 PM, Jason Gunthorpe wrote: > On Thu, Apr 21, 2022 at 09:41:30AM +0300, Joonas Lahtinen wrote: >> + Tvrtko >> >> Quoting Christoph Hellwig (2022-04-21 08:47:38) >>> On Thu, Apr 21, 2022 at 04:57:34AM +, Wang, Zhi A wrote: Is it possible that I can send two different pull bas

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Flat-CCS eviction enhancements (rev2)

== Series Details == Series: Flat-CCS eviction enhancements (rev2) URL : https://patchwork.freedesktop.org/series/102916/ 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 Flat-CCS eviction enhancements (rev2)

== Series Details == Series: Flat-CCS eviction enhancements (rev2) URL : https://patchwork.freedesktop.org/series/102916/ State : success == Summary == CI Bug Log - changes from CI_DRM_11535 -> Patchwork_102916v2 Summary --- **SUCCES

[Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [xf86-video-intel,1/3] sna: Don't emit sse2 code where not wanted

== Series Details == Series: series starting with [xf86-video-intel,1/3] sna: Don't emit sse2 code where not wanted URL : https://patchwork.freedesktop.org/series/102925/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/102925/revisions/1/mbox/ not

[Intel-gfx] [PATCH] drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses

Fix typo in the _SEL_FETCH_PLANE_BASE_1_B register base address. Fixes: a5523e2ff074a5 ("drm/i915: Add PSR2 selective fetch registers") References: https://gitlab.freedesktop.org/drm/intel/-/issues/5400 Cc: José Roberto de Souza Cc: # v5.9+ Signed-off-by: Imre Deak --- drivers/gpu/drm/i915/i91

Re: [Intel-gfx] [PATCH] drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses

On Thu, 2022-04-21 at 19:22 +0300, Imre Deak wrote: > Fix typo in the _SEL_FETCH_PLANE_BASE_1_B register base address. > Reviewed-by: José Roberto de Souza > Fixes: a5523e2ff074a5 ("drm/i915: Add PSR2 selective fetch registers") > References: https://gitlab.freedesktop.org/drm/intel/-/issues/54

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/fbc: Consult hw.crtc instead of uapi.crtc (rev2)

== Series Details == Series: series starting with [1/2] drm/i915/fbc: Consult hw.crtc instead of uapi.crtc (rev2) URL : https://patchwork.freedesktop.org/series/102657/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11536 -> Patchwork_102657v2 =

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Start reordering modeset clock calculations (rev5)

== Series Details == Series: drm/i915: Start reordering modeset clock calculations (rev5) URL : https://patchwork.freedesktop.org/series/101789/ State : warning == Summary == Error: dim checkpatch failed 32e8671c097f drm/i915: Make .get_dplls() return int d501feb0cac1 drm/i915: Pass dev_priv t

[Intel-gfx] [PATCH 0/1] Refactor CT access to use iosys_map

From: Siva Mullati ver2: remove newly added iosys map api from ver1 ver3: address review comments ver4: remove accessing vaddr This is continuation to the below patch series to use iosys map APIs, to use CT commands and descriptors. https://patchwork.freedesktop.org/series/99711/ Siva Mullati (

[Intel-gfx] [PATCH 1/1] drm/i915/guc: Convert ct buffer to iosys_map

From: Siva Mullati Convert CT commands and descriptors to use iosys_map rather than plain pointer and save it in the intel_guc_ct_buffer struct. This will help with ct_write and ct_read for cmd send and receive after the initialization by abstracting the IO vs system memory. Signed-off-by: Siva

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Start reordering modeset clock calculations (rev5)

== Series Details == Series: drm/i915: Start reordering modeset clock calculations (rev5) URL : https://patchwork.freedesktop.org/series/101789/ State : success == Summary == CI Bug Log - changes from CI_DRM_11536 -> Patchwork_101789v5 Summ

[Intel-gfx] [PULL v3] gvt-next

Hi folks: Here is the PR of gvt-next. Thanks so much for the patience. Mostly it includes the patch bundle of GVT-g re-factor patches for adapting the GVT-g with the new MDEV interfaces: - Separating the MMIO table from GVT-g. (Zhi) - GVT-g re-factor. (Christoph) - GVT-g mdev API cleanup. (Jaso

[Intel-gfx] [PATCH v4 0/6] drm/i915: ttm for stolen region

This series refactors i915's stolen memory region to use ttm. v2: handle disabled stolen similar to legacy version. relying on ttm to fail allocs works fine, but is dmesg noisy and causes testing dmesg warning regressions. v3: rebase to latest drm-tip. fix v2 code

[Intel-gfx] [PATCH v4 2/6] drm/i915: sanitize mem_flags for stolen buffers

Stolen regions are not page backed or considered iomem. Prevent flags indicating such. This correctly prevents stolen buffers from attempting to directly map them. See i915_gem_object_has_struct_page() and i915_gem_object_has_iomem() usage for where it would break otherwise. Signed-off-by: Robert

[Intel-gfx] [PATCH v4 1/6] drm/i915: instantiate ttm ranger manager for stolen memory

prepare for ttm based stolen region by using ttm range manager as the resource manager for stolen region. Signed-off-by: Robert Beckett --- drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c | 6 ++-- drivers/gpu/drm/i915/intel_region_ttm.c | 31 +++- 2 files changed, 27 insertio

[Intel-gfx] [PATCH v4 3/6] drm/i915: ttm move/clear logic fix

ttm managed buffers start off with system resource definitions and ttm_tt tracking structures allocated (though unpopulated). currently this prevents clearing of buffers on first move to desired placements. The desired behaviour is to clear user allocated buffers and any kernel buffers that specif

[Intel-gfx] [PATCH v4 4/6] drm/i915: ttm backend dont provide mmap_offset for kernel buffers

stolen/kernel buffers should not be mmapable by userland. do not provide callbacks to facilitate this for these buffers. Signed-off-by: Robert Beckett --- drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 32 + 1 file changed, 27 insertions(+), 5 deletions(-) diff --git a/driver

[Intel-gfx] [PATCH v4 5/6] drm/i915: allow memory region creators to alloc and free the region

add callbacks for alloc and free. this allows region creators to allocate any extra storage they may require. Signed-off-by: Robert Beckett --- drivers/gpu/drm/i915/intel_memory_region.c | 16 +--- drivers/gpu/drm/i915/intel_memory_region.h | 2 ++ 2 files changed, 15 insertions(+),

[Intel-gfx] [PATCH v4 6/6] drm/i915: stolen memory use ttm backend

refactor stolen memory region to use ttm. this necessitates using ttm resources to track reserved stolen regions instead of drm_mm_nodes. Signed-off-by: Robert Beckett --- drivers/gpu/drm/i915/display/intel_fbc.c | 78 +-- .../gpu/drm/i915/gem/i915_gem_object_types.h | 2 - drivers/gpu/

[Intel-gfx] ✗ Fi.CI.IGT: failure for Flat-CCS eviction enhancements (rev2)

== Series Details == Series: Flat-CCS eviction enhancements (rev2) URL : https://patchwork.freedesktop.org/series/102916/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11535_full -> Patchwork_102916v2_full Summary ---

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for GSC support (rev7)

On 4/19/2022 6:17 PM, Patchwork wrote: Project List - Patchwork *Patch Details* *Series:* GSC support (rev7) *URL:* https://patchwork.freedesktop.org/series/102160/ *State:*failure *Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102160v7/index.html CI Bug Log

[Intel-gfx] [PATCH 1/3] drm: Add infrastructure to allow seamless mode switches

Intel hardware supports change between modes with different refresh rates without any glitches or visual artifacts, that feature is called seamless DRRS. So far i915 driver was automatically changing between preferred panel mode and lower refresh rate mode based on idleness but ChromeOS compositor

[Intel-gfx] [PATCH 2/3] drm/i915/display: Replace crtc_state's has_drrs by drrs_downclock_mode

Will be adding some additional control options to DRRS that will require to have the DRRS downclock mode stored in the crtc_state. So to optimize memory usage a bit here using it to replace has_drrs as we can check if the drrs_downclock_mode pointer is different than null to have the same behavior

[Intel-gfx] [PATCH 3/3] drm/i915/display: Implement seamless mode switch

As described in previous commit "drm: Add infrastructure to allow seamless mode switches" here doing the i915 implementation. The main steps are: - drm_atomic_helper_check_modeset() will call atomic_seamless_mode_switch_check()/intel_drrs_seamless_mode_switch_check() if conditions match - intel_dr

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses

== Series Details == Series: drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses URL : https://patchwork.freedesktop.org/series/102941/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

Re: [Intel-gfx] [PATCH 2/9] drm/i915/gt: Add media freq factor to per-gt sysfs

On Tue, Apr 19, 2022 at 10:21:26PM -0700, Ashutosh Dixit wrote: > Expose new sysfs to program and retrieve media freq factor. Factor values > of 0 (dynamic), 0.5 and 1.0 are supported via a u8.8 fixed point > representation (corresponding to integer values of 0, 128 and 256 > respectively). > > Me

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses

== Series Details == Series: drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses URL : https://patchwork.freedesktop.org/series/102941/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11537 -> Patchwork_102941v1 Summa

Re: [Intel-gfx] [PATCH 03/15] dma-buf & drm/amdgpu: remove dma_resv workaround

On Thu, 2022-04-21 at 12:17 +0200, Christian König wrote: > ⚠ External Email > > Am 20.04.22 um 21:28 schrieb Zack Rusin: > > [SNIP] > > > To figure out what it is could you try the following code > > > fragment: > > > > > > diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_validation.c > > > b/drivers/

[Intel-gfx] ✗ Fi.CI.BUILD: failure for Make the rest of the VFIO driver interface use vfio_device (rev3)

== Series Details == Series: Make the rest of the VFIO driver interface use vfio_device (rev3) URL : https://patchwork.freedesktop.org/series/102606/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/102606/revisions/3/mbox/ not applied Applying: vfi

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Refactor CT access to use iosys_map

== Series Details == Series: Refactor CT access to use iosys_map URL : https://patchwork.freedesktop.org/series/102949/ 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: failure for drm/i915: Start reordering modeset clock calculations (rev5)

== Series Details == Series: drm/i915: Start reordering modeset clock calculations (rev5) URL : https://patchwork.freedesktop.org/series/101789/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11536_full -> Patchwork_101789v5_full

[Intel-gfx] ✓ Fi.CI.BAT: success for Refactor CT access to use iosys_map

== Series Details == Series: Refactor CT access to use iosys_map URL : https://patchwork.freedesktop.org/series/102949/ State : success == Summary == CI Bug Log - changes from CI_DRM_11537 -> Patchwork_102949v1 Summary --- **SUCCESS*

[Intel-gfx] ✗ Fi.CI.BUILD: failure for gvt-next

== Series Details == Series: gvt-next URL : https://patchwork.freedesktop.org/series/102952/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/102952/revisions/1/mbox/ not applied Applying: gvt-next error: sha1 information is lacking or useless (dri

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/fbc: Consult hw.crtc instead of uapi.crtc (rev3)

== Series Details == Series: series starting with [1/2] drm/i915/fbc: Consult hw.crtc instead of uapi.crtc (rev3) URL : https://patchwork.freedesktop.org/series/102657/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11537 -> Patchwork_102657v3 =

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: ttm for stolen region (rev4)

== Series Details == Series: drm/i915: ttm for stolen region (rev4) URL : https://patchwork.freedesktop.org/series/102540/ State : warning == Summary == Error: dim checkpatch failed c1e10dd4ab94 drm/i915: instantiate ttm ranger manager for stolen memory 0f75dfba1932 drm/i915: sanitize mem_flag

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: ttm for stolen region (rev4)

== Series Details == Series: drm/i915: ttm for stolen region (rev4) URL : https://patchwork.freedesktop.org/series/102540/ 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: failure for drm/i915: ttm for stolen region (rev4)

== Series Details == Series: drm/i915: ttm for stolen region (rev4) URL : https://patchwork.freedesktop.org/series/102540/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11537 -> Patchwork_102540v4 Summary --- **FAILU

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/3] drm: Add infrastructure to allow seamless mode switches

== Series Details == Series: series starting with [1/3] drm: Add infrastructure to allow seamless mode switches URL : https://patchwork.freedesktop.org/series/102958/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked sep

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/3] drm: Add infrastructure to allow seamless mode switches

== Series Details == Series: series starting with [1/3] drm: Add infrastructure to allow seamless mode switches URL : https://patchwork.freedesktop.org/series/102958/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11538 -> Patchwork_102958v1 ===

Re: [Intel-gfx] [PATCH v2 1/7] vfio: Make vfio_(un)register_notifier accept a vfio_device

> From: Jason Gunthorpe > Sent: Friday, April 22, 2022 12:29 AM > > All callers have a struct vfio_device trivially available, pass it in > directly and avoid calling the expensive vfio_group_get_from_dev(). > > To support the unconverted kvmgt mdev driver add > mdev_legacy_get_vfio_device() whic

Re: [Intel-gfx] [PATCH v2 3/7] vfio/mdev: Pass in a struct vfio_device * to vfio_pin/unpin_pages()

> From: Jason Gunthorpe > Sent: Friday, April 22, 2022 12:29 AM > > Every caller has a readily available vfio_device pointer, use that instead > of passing in a generic struct device. The struct vfio_device already > contains the group we need so this avoids complexity, extra refcountings, > and

Re: [Intel-gfx] [PATCH v2 4/7] vfio/mdev: Pass in a struct vfio_device * to vfio_dma_rw()

> From: Jason Gunthorpe > Sent: Friday, April 22, 2022 12:29 AM > > Every caller has a readily available vfio_device pointer, use that instead > of passing in a generic struct device. The struct vfio_device already > contains the group we need so this avoids complexity, extra refcountings, > and

Re: [Intel-gfx] [PATCH v2 5/7] drm/i915/gvt: Change from vfio_group_(un)pin_pages to vfio_(un)pin_pages

> From: Jason Gunthorpe > Sent: Friday, April 22, 2022 12:29 AM > > Use the existing vfio_device versions of vfio_(un)pin_pages(). There is no > reason to use a group interface here, kvmgt has easy access to a > vfio_device. > > Delete kvmgt_vdev::vfio_group since these calls were the last users

Re: [Intel-gfx] [PATCH v2 6/7] vfio: Remove dead code

> From: Jason Gunthorpe > Sent: Friday, April 22, 2022 12:29 AM > > Now that callers have been updated to use the vfio_device APIs the driver > facing group interface is no longer used, delete it: > > - vfio_group_get_external_user_from_dev() > - vfio_group_pin_pages() > - vfio_group_unpin_pages

Re: [Intel-gfx] [PATCH v2 7/7] vfio: Remove calls to vfio_group_add_container_user()

> From: Jason Gunthorpe > Sent: Friday, April 22, 2022 12:29 AM > > When the open_device() op is called the container_users is incremented and > held incremented until close_device(). Thus, so long as drivers call > functions within their open_device()/close_device() region they do not > need to

[Intel-gfx] ✗ Fi.CI.IGT: failure for Refactor CT access to use iosys_map

== Series Details == Series: Refactor CT access to use iosys_map URL : https://patchwork.freedesktop.org/series/102949/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11537_full -> Patchwork_102949v1_full Summary ---

Re: [Intel-gfx] [PATCH v2 1/7] vfio: Make vfio_(un)register_notifier accept a vfio_device

Looks good (for now): Reviewed-by: Christoph Hellwig

Re: [Intel-gfx] [PATCH v2 3/7] vfio/mdev: Pass in a struct vfio_device * to vfio_pin/unpin_pages()

Nit: why do some of these patches that don't touch the mdev code mdev in the subject?

Re: [Intel-gfx] [PATCH v2 5/7] drm/i915/gvt: Change from vfio_group_(un)pin_pages to vfio_(un)pin_pages

Looks good: Reviewed-by: Christoph Hellwig