[Intel-xe] ✓ CI.checkpatch: success for drm/xe: Fix lockdep warning in xe_force_wake calls (rev4)

[Patchwork]

== Series Details ==

Series: drm/xe: Fix lockdep warning in xe_force_wake calls (rev4)
URL   : https://patchwork.freedesktop.org/series/126241/
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
6030b24c1386b00de8187b5fb987e283a57b372a
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 1b03951e41a87a23d60e96b1aafdba01d8a35c41
Author: Aravind Iddamsetty <aravind.iddamsetty at linux.intel.com>
Date:   Wed Dec 6 15:23:18 2023 +0530

    drm/xe: Fix lockdep warning in xe_force_wake calls
    
    Use spin_lock_irqsave, spin_unlock_irqrestore
    
    Fix for below:
    [13994.811263] ========================================================
    [13994.811295] WARNING: possible irq lock inversion dependency detected
    [13994.811326] 6.6.0-rc3-xe #2 Tainted: G     U
    [13994.811358] --------------------------------------------------------
    [13994.811388] swapper/0/0 just changed the state of lock:
    [13994.811416] ffff895c7e044db8 (&cpuctx_lock){-...}-{2:2}, at:
    __perf_event_read+0xb7/0x3a0
    [13994.811494] but this lock took another, HARDIRQ-unsafe lock in the
    past:
    [13994.811528]  (&fw->lock){+.+.}-{2:2}
    [13994.811544]
    
                   and interrupts could create inverse lock ordering between
    them.
    
    [13994.811606]
                   other info that might help us debug this:
    [13994.811636]  Possible interrupt unsafe locking scenario:
    
    [13994.811667]        CPU0                    CPU1
    [13994.811691]        ----                    ----
    [13994.811715]   lock(&fw->lock);
    [13994.811744]                                local_irq_disable();
    [13994.811773]                                lock(&cpuctx_lock);
    [13994.811810]                                lock(&fw->lock);
    [13994.811846]   <Interrupt>
    [13994.811865]     lock(&cpuctx_lock);
    [13994.811895]
                    *** DEADLOCK ***
    
    v2: Use spin_lock in atomic context and spin_lock_irq in a non atomic
    context (Matthew Brost)
    
    v3: just use spin_lock_irqsave/restore
    
    Cc: Matthew Brost <matthew.brost at intel.com>
    Cc: Anshuman Gupta <anshuman.gupta at intel.com>
    Cc: Ville Syrjala <ville.syrjala at linux.intel.com>
    
    Signed-off-by: Aravind Iddamsetty <aravind.iddamsetty at linux.intel.com>
+ /mt/dim checkpatch 9d76164e08c68a3d5d081ff7b07c15a2cadf741a drm-intel
1b03951e4 drm/xe: Fix lockdep warning in xe_force_wake calls