✓ CI.checkpatch: success for drm/xe: Perform dma_map when moving system buffer objects to TT

[Patchwork]

== Series Details ==

Series: drm/xe: Perform dma_map when moving system buffer objects to TT
URL   : https://patchwork.freedesktop.org/series/133068/
State : success

== Summary ==

+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
0daf0be5bb95eb0a0e42275e00a0e42d8d8fd543
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit bd03c251f2dcaf1eb5aa85a57b5f2b42acf5baeb
Author: Thomas Hellström <thomas.hellstrom at linux.intel.com>
Date:   Tue Apr 30 14:02:14 2024 +0200

    drm/xe: Perform dma_map when moving system buffer objects to TT
    
    Currently we dma_map on ttm_tt population and dma_unmap when
    the pages are released in ttm_tt unpopulate.
    
    Strictly, the dma_map is not needed until the bo is moved to the
    XE_PL_TT placement, so perform the dma_mapping on such moves
    instead, and remove the dma_mappig when moving to XE_PL_SYSTEM.
    
    This is desired for the upcoming shrinker series where shrinking
    of a ttm_tt might fail. That would lead to an odd construct where
    we first dma_unmap, then shrink and if shrinking fails dma_map
    again. If dma_mapping instead is performed on move like this,
    shrinking does not need to care at all about dma mapping.
    
    Finally, where a ttm_tt is destroyed while bound to a different
    memory type than XE_PL_SYSTEM, we keep the dma_unmap in
    unpopulate().
    
    Signed-off-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
+ /mt/dim checkpatch 39bf0b9d268e460fe2b7e9f792c9d610655eb9b7 drm-intel
bd03c251f2dc drm/xe: Perform dma_map when moving system buffer objects to TT