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

[Patchwork]

== Series Details ==

Series: Allow CTB G2H processing without G2H IRQ
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 2798aef83f9c6f3974fdb83b42a7f5a5bc7d06cb
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Wed Jun 5 22:19:47 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 a494545483635d3d93d19e8f483f61e7d4198383 drm-intel
d1935203ae06 drm/xe/guc: Prepare fast-path to be called outside of IRQ handler
2798aef83f9c drm/xe/guc: Allow CTB G2H processing without G2H IRQ