✓ CI.checkpatch: success for drm/xe: Get XE_FORCEWAKE_ALL to read RING_TIMESTAMP

[Patchwork]

== Series Details ==

Series: drm/xe: Get XE_FORCEWAKE_ALL to read RING_TIMESTAMP
URL   : https://patchwork.freedesktop.org/series/135196/
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 be220bc6a2b9bfd02cce9ca37b8a1bcdf443842c
Author: Umesh Nerlige Ramappa <umesh.nerlige.ramappa at intel.com>
Date:   Sat Jun 22 03:23:25 2024 +0800

    drm/xe: Get XE_FORCEWAKE_ALL to read RING_TIMESTAMP
    
    Per client engine utilization uses RING_TIMESTAMP to return
    drm-total-cycles to the user. We read only the rcs RING_TIMESTAMP in
    platforms that have render. While this works for rcs and
    ccs, it is observed that this value is 0 when running work on bcs, vcs
    and vecs. Ideally we should read the engine specific RING_TIMESTAMP, but
    to keep the logic simple, just get XE_FORCEWAKE_ALL instead of XE_GT_FW.
    
    This should work fine on multi-gt platforms as well since the
    gt_timestamp is in sync on all GTs.
    
    Fixes: 188ced1e0ff8 ("drm/xe/client: Print runtime to fdinfo")
    Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa at intel.com>
+ /mt/dim checkpatch 383dc44a79848f13f2430c9ed811b5c9b22b882a drm-intel
be220bc6a2b9 drm/xe: Get XE_FORCEWAKE_ALL to read RING_TIMESTAMP