[Intel-xe] ✗ CI.Patch_applied: failure for Upstreaming prep / all of mbrosts patches (rev2)

[Christopher Snowhill (kode54)]

> On May 1, 2023, at 5:20 PM, Patchwork <patchwork at emeril.freedesktop.org> wrote:
> 
> == Series Details ==
> 
> Series: Upstreaming prep / all of mbrosts patches (rev2)
> URL   : https://patchwork.freedesktop.org/series/117156/
> State : failure
> 
> == Summary ==
> 
> === Applying kernel patches on branch 'drm-xe-next' with base: ===
> Base commit: 9a7a643c2 drm/xe: Fix media detection for pre-GMD_ID platforms
> === git am output follows ===
> error: patch failed: drivers/gpu/drm/xe/xe_pt.c:778
> error: drivers/gpu/drm/xe/xe_pt.c: patch does not apply
> hint: Use 'git am --show-current-patch' to see the failed patch
> Applying: drm/sched: Add run_wq argument to drm_sched_init
> Applying: drm/sched: Move schedule policy to scheduler
> Applying: drm/sched: Add DRM_SCHED_POLICY_SINGLE_ENTITY scheduling policy
> Applying: drm/xe: Use DRM_SCHED_POLICY_SINGLE_ENTITY mode
> Applying: drm/xe: Long running job update
> Applying: drm/xe: Ensure LR engines are not persistent
> Applying: drm/xe: Only try to lock external BOs in VM bind
> Applying: drm/xe: VM LRU bulk move
> Applying: drm/xe/guc: Read HXG fields from DW1 of G2H response
> Applying: drm/xe/guc: Return the lower part of blocking H2G message
> Applying: drm/xe/guc: Use doorbells for submission if possible
> Applying: drm/xe/guc: Print doorbell ID in GuC engine debugfs entry
> Applying: maple_tree: split up MA_STATE() macro
> Applying: maple_tree: Export mas_preallocate
> Applying: drm: manager to keep track of GPUs VA mappings
> Applying: drm/xe: Port Xe to GPUVA
> Patch failed at 0016 drm/xe: Port Xe to GPUVA
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".

damn I hate Apple Mail. I wanted to select which message in the thread I am replying to, and it naturally assumes I want to quote and reply to the most recent.

Anyway, is there a Mesa branch that works with this series yet? Or will the current Xe branch work here? I already needed to use a special flavor of the branch because of shared object issues that hadn't been merged into the main MR, and I'm using @mlankhorst's uAPI header and validation, and my own compat ioctl function one line change to make 32 bit work.

Otherwise, if there's no working userspace for this yet, I'll just give it a pass at testing for now.

I did notice some typoes in the above comments or commit messages, though. Like "doorbels". I'll have to look over it again if it's worth noting any more.