[Intel-xe] ✗ CI.checkpatch: warning for PAT and cache coherency support (rev15)

[Patchwork]

== Series Details ==

Series: PAT and cache coherency support (rev15)
URL   : https://patchwork.freedesktop.org/series/123027/
State : warning

== 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
63c2b6b160bca2df6efc7bc4cea6f442097d7854
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 8cf4a07c909e18d1a733941bf00b3b2775cfc868
Author: Matthew Auld <matthew.auld at intel.com>
Date:   Wed Nov 22 10:14:51 2023 +0000

    drm/xe/uapi: support pat_index selection with vm_bind
    
    Allow userspace to directly control the pat_index for a given vm
    binding. This should allow directly controlling the coherency, caching
    behaviour, compression and potentially other stuff in the future for the
    ppGTT binding.
    
    The exact meaning behind the pat_index is very platform specific (see
    BSpec or PRMs) but effectively maps to some predefined memory
    attributes. From the KMD pov we only care about the coherency that is
    provided by the pat_index, which falls into either NONE, 1WAY or 2WAY.
    The vm_bind coherency mode for the given pat_index needs to be at least
    1way coherent when using cpu_caching with DRM_XE_GEM_CPU_CACHING_WB. For
    platforms that lack the explicit coherency mode attribute, we treat
    UC/WT/WC as NONE and WB as AT_LEAST_1WAY.
    
    For userptr mappings we lack a corresponding gem object, so the expected
    coherency mode is instead implicit and must fall into either 1WAY or
    2WAY. Trying to use NONE will be rejected by the kernel. For imported
    dma-buf (from a different device) the coherency mode is also implicit
    and must also be either 1WAY or 2WAY.
    
    v2:
      - Undefined coh_mode(pat_index) can now be treated as programmer
        error. (Matt Roper)
      - We now allow gem_create.coh_mode <= coh_mode(pat_index), rather than
        having to match exactly. This ensures imported dma-buf can always
        just use 1way (or even 2way), now that we also bundle 1way/2way into
        at_least_1way. We still require 1way/2way for external dma-buf, but
        the policy can now be the same for self-import, if desired.
      - Use u16 for pat_index in uapi. u32 is massive overkill. (José)
      - Move as much of the pat_index validation as we can into
        vm_bind_ioctl_check_args. (José)
    v3 (Matt Roper):
      - Split the pte_encode() refactoring into separate patch.
    v4:
      - Rebase
    v5:
      - Check for and reject !coh_mode which would indicate hw reserved
        pat_index on xe2.
    v6:
      - Rebase on removal of coh_mode from uapi. We just need to reject
        cpu_caching=wb + pat_index with coh_none.
    
    Testcase: igt at xe_pat
    Bspec: 45101, 44235 #xe
    Bspec: 70552, 71582, 59400 #xe2
    Signed-off-by: Matthew Auld <matthew.auld at intel.com>
    Cc: Pallavi Mishra <pallavi.mishra at intel.com>
    Cc: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Cc: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>
    Cc: Lucas De Marchi <lucas.demarchi at intel.com>
    Cc: Matt Roper <matthew.d.roper at intel.com>
    Cc: José Roberto de Souza <jose.souza at intel.com>
    Cc: Filip Hazubski <filip.hazubski at intel.com>
    Cc: Carl Zhang <carl.zhang at intel.com>
    Cc: Effie Yu <effie.yu at intel.com>
    Cc: Zhengguo Xu <zhengguo.xu at intel.com>
    Cc: Francois Dugast <francois.dugast at intel.com>
    Tested-by: José Roberto de Souza <jose.souza at intel.com>
    Reviewed-by: José Roberto de Souza <jose.souza at intel.com>
    Acked-by: Zhengguo Xu <zhengguo.xu at intel.com>
    Acked-by: Bartosz Dunajski <bartosz.dunajski at intel.com>
+ /mt/dim checkpatch 89e2bb1e155242dd9aa46bc90e563e71c5f498b0 drm-intel
56603cea8 drm/xe/uapi: Add support for CPU caching mode
e3ca7f886 drm/xe/pat: annotate pat_index with coherency mode
-:147: CHECK:MACRO_ARG_REUSE: Macro argument reuse '__coh_mode' - possible side-effects?
#147: FILE: drivers/gpu/drm/xe/xe_pat.c:99:
+#define XE2_PAT(no_promote, comp_en, l3clos, l3_policy, l4_policy, __coh_mode) \
+	{ \
+		.value = (no_promote ? XE2_NO_PROMOTE : 0) | \
+			(comp_en ? XE2_COMP_EN : 0) | \
+			REG_FIELD_PREP(XE2_L3_CLOS, l3clos) | \
+			REG_FIELD_PREP(XE2_L3_POLICY, l3_policy) | \
+			REG_FIELD_PREP(XE2_L4_POLICY, l4_policy) | \
+			REG_FIELD_PREP(XE2_COH_MODE, __coh_mode), \
+		.coh_mode = __coh_mode ? XE_COH_AT_LEAST_1WAY : XE_COH_NONE \
+	}

-:167: ERROR:SPACING: space prohibited after that open parenthesis '('
#167: FILE: drivers/gpu/drm/xe/xe_pat.c:143:
+static const struct xe_pat_table_entry xe2_pat_ats = XE2_PAT( 0, 0, 0, 0, 3, 3 );

-:167: ERROR:SPACING: space prohibited before that close parenthesis ')'
#167: FILE: drivers/gpu/drm/xe/xe_pat.c:143:
+static const struct xe_pat_table_entry xe2_pat_ats = XE2_PAT( 0, 0, 0, 0, 3, 3 );

total: 2 errors, 0 warnings, 1 checks, 210 lines checked
8cf4a07c9 drm/xe/uapi: support pat_index selection with vm_bind