[Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Skip XY_FAST_COLOR instruction on link copy engines (rev5)

[Patchwork]

== Series Details ==

Series: drm/xe: Skip XY_FAST_COLOR instruction on link copy engines (rev5)
URL   : https://patchwork.freedesktop.org/series/114751/
State : success

== Summary ==

=== Applying kernel patches on branch 'drm-xe-next' with base: ===
commit 10989943f6b27400a891c4bfc9e37ee31aef9f26
Author:     Matthew Auld <matthew.auld at intel.com>
AuthorDate: Tue Mar 14 08:58:39 2023 +0000
Commit:     Matthew Auld <matthew.auld at intel.com>
CommitDate: Fri Mar 17 09:58:48 2023 +0000

    drm/xe/vram: start tracking the io_size
    
    First step towards supporting small-bar is to track the io_size for
    vram. We can longer assume that the io_size == vram size. This way we
    know how much is CPU accessible via the BAR, and how much is not.
    Effectively giving us a two tiered vram, where in some later patches we
    can support different allocation strategies depending on if the memory
    needs to be CPU accessible or not.
    
    Note as this stage we still clamp the vram size to the usable vram size.
    Only in the final patch do we turn this on for real, and allow distinct
    io_size and vram_size.
    
    v2: (Lucas):
      - Improve the commit message, plus improve the kernel-doc for the
        io_size to give a better sense of what it actually is.
    
    Signed-off-by: Matthew Auld <matthew.auld at intel.com>
    Cc: Gwan-gyeong Mun <gwan-gyeong.mun at intel.com>
    Cc: Lucas De Marchi <lucas.demarchi at intel.com>
    Reviewed-by: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
    Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun at intel.com>
=== git am output follows ===
Applying: drm/xe: Stop accepting value in xe_migrate_clear
Applying: drm/xe: Skip XY_FAST_COLOR instruction on link copy engines