✓ CI.checkpatch: success for drm/xe: Use xe_pm_runtime_get in xe_bo_move() if reclaim-safe.

[Patchwork]

== Series Details ==

Series: drm/xe: Use xe_pm_runtime_get in xe_bo_move() if reclaim-safe.
URL   : https://patchwork.freedesktop.org/series/138131/
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
9fe5037901cabbcdf27a6fe0dfb047ca1474d363
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit dcbcce26ff1a48d407a3aac4ce70771a6c8348f6
Author: Thomas Hellström <thomas.hellstrom at linux.intel.com>
Date:   Tue Sep 3 11:42:32 2024 +0200

    drm/xe: Use xe_pm_runtime_get in xe_bo_move() if reclaim-safe.
    
    xe_bo_move() might be called in the TTM swapout path from validation
    by another TTM device. If so, we are not likely to have a RPM
    reference. So iff xe_pm_runtime_get() is safe to call from reclaim,
    use it instead of xe_pm_runtime_get_noresume().
    
    Strictly this is currently needed only if handle_system_ccs is true,
    but use xe_pm_runtime_get() if possible anyway to increase test
    coverage.
    
    At the same time warn if handle_system_ccs is true and we can't
    call xe_pm_runtime_get() from reclaim context. This will likely trip
    if someone tries to enable SRIOV on LNL, without fixing Xe SRIOV
    runtime resume / suspend.
    
    Cc: Rodrigo Vivi <rodrigo.vivi at intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
    Cc: Matthew Auld <matthew.auld at intel.com>
    Signed-off-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Reviewed-by: Matthew Auld <matthew.auld at intel.com>
+ /mt/dim checkpatch dd987a9431a336ddbfc6bfe9720f4783a6bc94b0 drm-intel
dcbcce26ff1a drm/xe: Use xe_pm_runtime_get in xe_bo_move() if reclaim-safe.