[Intel-gfx] [RFC 3/5] drm/i915: split out virtual engine code

[Chris Wilson]

Quoting Daniele Ceraolo Spurio (2019-12-11 21:12:42)
> Having the virtual engine handling in its own file will make it easier
> call it from or modify for the GuC implementation without leaking the
> changes in the context management or execlists submission paths.

No. The virtual engine is tightly coupled into the execlists, it is not
the starting point for a general veng.
-Chris