✓ CI.checkpatch: success for Allow CTB G2H processing without G2H IRQ (rev2)

[Patchwork]

== Series Details ==

Series: Allow CTB G2H processing without G2H IRQ (rev2)
URL   : https://patchwork.freedesktop.org/series/134523/
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
51ce9f6cd981d42d7467409d7dbc559a450abc1e
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 2ffa198f883869d0289fb818ee27dc718b43a391
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Thu Jun 6 15:06:39 2024 +0200

    drm/xe/guc: Allow CTB G2H processing without G2H IRQ
    
    During early initialization, in the xe_guc_min_load_for_hwconfig()
    function, we are successfully enabling CTB communication, but it
    will only allow us to send non-blocking H2G messages, as due to
    not yet enabled IRQs, including G2H IRQs, we will not notice any
    new G2H message sent by the GuC, including replies to our blocking
    H2G request messages. And those successful replies are mandatory
    for the VF drivers to continue normal operations.
    
    As attempt to workaround this driver initialization ordering issue,
    introduce special safe-mode CTB worker, that will periodically
    trigger G2H processing, like original IRQ handler, in case no
    MSI/MSIX IRQs were enabled on the driver yet. Once we detect that
    IRQ were enabled, we will stop this worker.
    
    Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch 2163887f734af2f0a812a322e1a53ef6d62bf3d5 drm-intel
8dcfe4221b3c drm/xe/guc: Split g2h worker function
2ffa198f8838 drm/xe/guc: Allow CTB G2H processing without G2H IRQ