[RFC PATCH] drm/xe/uapi: Remove support for persistent exec_queues

[Dave Airlie]

On Tue, 30 Jan 2024 at 22:52, Thomas Hellström
<thomas.hellstrom at linux.intel.com> wrote:
>
> Persistent exec_queues delays explicit destruction of exec_queues
> until they are done executing, but destruction on process exit
> is still immediate. It turns out no UMD is relying on this
> functionality, so remove it. If there turns out to be a use-case
> in the future, let's re-add.
>
> Persistent exec_queues were never used for LR VMs
>
> Open: Should we renumber the exec_queue properties, or leave a hole
> as in this patch.


So can we have a bit of insight into how this happened? Like we just
merged xe and it already has uapi that had no userspace?

Like seriously? I'm sorry Intel has all these crazy silos with
compute, video, graphics and kernel teams, but that should be Intel's
internal problem, can we stop exposing your org chart outside the
company?

If you can't get someone from the compute team to work in the kernel
driver space when a new uAPI is needed, and instead powerpoint up
uAPIs without commitments, then xe is going to end up being in the
same hole as i915.

Dave.