✓ CI.checkpatch: success for Deny unbinds if user fence pending (rev2)

Patchwork patchwork at emeril.freedesktop.org
Thu Feb 15 18:33:54 UTC 2024


== Series Details ==

Series: Deny unbinds if user fence pending (rev2)
URL   : https://patchwork.freedesktop.org/series/129957/
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
35591fb8b4d5305b37ce31483f85ac0956eaa536
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit a48db5d4e3b8e31e82dacaeabdeebebc4866ed52
Author: Mika Kuoppala <mika.kuoppala at linux.intel.com>
Date:   Thu Feb 15 20:11:52 2024 +0200

    drm/xe: Deny unbinds if uapi ufence pending
    
    If user fence was provided for MAP in vm_bind_ioctl
    and it has still not been signalled, deny UNMAP of said
    vma with EBUSY as long as unsignalled fence exists.
    
    This guarantees that MAP vs UNMAP sequences won't
    escape under the radar if we ever want to track the
    client's state wrt to completed and accessible MAPs.
    By means of intercepting the ufence release signalling.
    
    v2: find ufence with num_fences > 1 (Matt)
    v3: careful on clearing vma ufence (Matt)
    
    Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1159
    Cc: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
    Cc: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>
    Signed-off-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
+ /mt/dim checkpatch 6d3abf8f7f55420cf53e9ed344872c459ecfd0ed drm-intel
de68e6cb9 drm/xe: Expose user fence from xe_sync_entry
a48db5d4e drm/xe: Deny unbinds if uapi ufence pending




More information about the Intel-xe mailing list