✓ CI.checkpatch: success for drm/xe/guc: Enable WA_DUAL_QUEUE for newer platforms

[Patchwork]

== Series Details ==

Series: drm/xe/guc: Enable WA_DUAL_QUEUE for newer platforms
URL   : https://patchwork.freedesktop.org/series/141812/
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
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 6c7b1fdbc1c070252bd34e8eff82a970b55d89de
Author: Daniele Ceraolo Spurio <daniele.ceraolospurio at intel.com>
Date:   Tue Nov 26 17:11:05 2024 -0800

    drm/xe/guc: Enable WA_DUAL_QUEUE for newer platforms
    
    The DUAL_QUEUE_WA tells the GuC to not allow concurrent submissions
    on RCS and CCSes with different address spaces, which on DG2 is
    required as a WA for an HW bug. On newer platforms, this block has
    been moved in HW at the CS level, by stalling the RCS/CCS context
    switch when one of the other RCS/CCSes is busy with a different
    address space. While functionally correct, having a submission
    stalled on the HW limits the GuC ability to shuffle things around and
    can cause complications if the non-stalled submission runs for a long
    time, because the GuC doesn't know that the stalled submission isn't
    actually running and might declare it as hung. Therefore, we enable
    the DUAL_QUEUE_WA on all newer platforms to move management back to
    the GuC.
    
    Note that the GuC specs also recommend enabling this for all platforms
    starting from MTL that have a CCS.
    
    Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio at intel.com>
    Cc: John Harrison <John.C.Harrison at Intel.com>
+ /mt/dim checkpatch 739a2506c44a0be22cc842d2c625a05ed21c1198 drm-intel
6c7b1fdbc1c0 drm/xe/guc: Enable WA_DUAL_QUEUE for newer platforms