✓ CI.checkpatch: success for drm/xe: GSM size should be constant on most platforms

[Patchwork]

== Series Details ==

Series: drm/xe: GSM size should be constant on most platforms
URL   : https://patchwork.freedesktop.org/series/149907/
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
202708c00696422fd217223bb679a353a5936e23
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 66d4f3ca3c6de02833c1b23b92d8f633e6a9db48
Author: Matt Roper <matthew.d.roper at intel.com>
Date:   Thu Jun 5 15:53:53 2025 -0700

    drm/xe: GSM size should be constant on most platforms
    
    On old Intel platforms, the size of the GSM (i.e., the stolen memory
    that holds the GGTT page table entries) could vary, so the driver needed
    to read the actual size from the PCI config space.  However from Xe_HP
    onward, the GSM is now always guaranteed to be exactly 8MB (which
    translates to a 4GB GGTT address space); this is always true regardless
    of what the platform's much larger PPGTT address space is.
    
    The bspec doesn't document the PCI config space as being a valid way to
    query the size of the GSM after Xe_LP platforms, although so far it
    still seems to be giving us proper values for Xe_HP, Xe2, and Xe3.
    However we suspect that the config space will stop providing correct
    values on some upcoming platforms, so we should stop relying on it.
    Instead just use the hardcoded 8MB value as documented elsewhere in the
    bspec.
    
    Bspec: 49636, 67090, 50589
    Signed-off-by: Matt Roper <matthew.d.roper at intel.com>
+ /mt/dim checkpatch 308a53b9affc92eca9eaa6117dd62c79d5419ce7 drm-intel
66d4f3ca3c6d drm/xe: GSM size should be constant on most platforms