✓ CI.checkpatch: success for drm/xe/migrate: Fix CCS copy for small VRAM copy chunks (rev2)

[Patchwork]

== Series Details ==

Series: drm/xe/migrate: Fix CCS copy for small VRAM copy chunks (rev2)
URL   : https://patchwork.freedesktop.org/series/127874/
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
6030b24c1386b00de8187b5fb987e283a57b372a
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit f6e9b88655d57481a896da8dfbfb02d9eb6f5fb7
Author: Thomas Hellström <thomas.hellstrom at linux.intel.com>
Date:   Fri Dec 15 16:07:13 2023 +0100

    drm/xe/migrate: Fix CCS copy for small VRAM copy chunks
    
    Since the migrate code is using the identity map for addressing VRAM,
    copy chunks may become as small as 64K if the VRAM resource is fragmented.
    
    However, a chunk size smaller that 1MiB may lead to the *next* chunk's
    offset into the CCS metadata backup memory may not be page-aligned, and
    the XY_CTRL_SURF_COPY_BLT command can't handle that, and even if it could,
    the current code doesn't handle the offset calculaton correctly.
    
    To fix this, make sure we align the size of VRAM copy chunks to 1MiB. If
    the remaining data to copy is smaller than that, that's not a problem,
    so use the remaining size. If the VRAM copy cunk becomes fragmented due
    to the size alignment restriction, don't use the identity map, but instead
    emit PTEs into the page-table like we do for system memory.
    
    v2:
    - Rebase
    
    Signed-off-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
+ /mt/dim checkpatch d25c0edf65307f50c5fb98e6790b548962ae75ed drm-intel
f6e9b8865 drm/xe/migrate: Fix CCS copy for small VRAM copy chunks