✓ CI.checkpatch: success for drm/xe/vf: Post-migration recovery of GGTT nodes and CTB

Patchwork patchwork at emeril.freedesktop.org
Fri Apr 18 00:23:14 UTC 2025


== Series Details ==

Series: drm/xe/vf: Post-migration recovery of GGTT nodes and CTB
URL   : https://patchwork.freedesktop.org/series/147947/
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
13a92ce9fd458ebd6064f23cec8c39c53d02ed26
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit e398391b1acd730cccacaf154ff2e9cdc2da55a6
Author: Tomasz Lis <tomasz.lis at intel.com>
Date:   Fri Apr 18 01:42:39 2025 +0200

    drm/xe/vf: Fixup CTB send buffer messages after migration
    
    During post-migration recovery of a VF, it is necessary to update
    GGTT references included in messages which are going to be sent
    to GuC. GuC will start consuming messages after VF KMD will inform
    it about fixups being done; before that, the VF KMD is expected
    to update any H2G messages which are already in send buffer but
    were not consumed by GuC.
    
    Only a small subset of messages allowed for VFs have GGTT references
    in them. This patch adds the functionality to parse the CTB send
    ring buffer and shift addresses contained within.
    
    While fixing the CTB content, ct->lock is not taken. This means
    the only barrier taken remains GGTT address lock - which is ok,
    because only requests with GGTT addresses matter, but it also means
    tail changes can happen during the CTB fixups execution (which may
    be ignored as any new messages will not have anything to fix).
    
    The GGTT address locking will be introduced in a future series.
    
    v2: removed storing shift as that's now done in VMA nodes patch;
      macros to inlines; warns to asserts; log messages fixes (Michal)
    v3: removed inline keywords, enums for offsets in CTB messages,
      less error messages, if return unused then made functs void (Michal)
    v4: update the cached head before starting fixups
    v5: removed/updated comments, wrapped lines, converted assert into
      error, enums for offsets to separate patch, reused xe_map_rd
    v6: define xe_map_*_array() macros, support CTB wrap which divides
      a message, updated comments, moved one function to an earlier patch
    v7: renamed few functions, wider use on previously introduced helper,
      separate cases in parsing messges, documented a static funct
    v8: Introduced more helpers, fixed coding style mistakes
    v9: Move xe_map*() functs to macros, add asserts, add debug print
    v10: Errors in place of some asserts, style fixes
    
    Signed-off-by: Tomasz Lis <tomasz.lis at intel.com>
    Cc: Michal Wajdeczko <michal.wajdeczko at intel.com>
+ /mt/dim checkpatch 1e5b5f168ee053192ea7ec05bfe826f848be7d68 drm-intel
6e0ba03e38a6 drm/xe/vf: Divide GGTT ballooning into allocation and insertion
97c159065749 drm/xe/vf: Shifting GGTT area post migration
0ebd9dcbf034 drm/xe/guc: Introduce enum with offsets for context register H2Gs
e398391b1acd drm/xe/vf: Fixup CTB send buffer messages after migration




More information about the Intel-xe mailing list