Re: [RFC 3/5] drm/i915: split out virtual engine code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 12/11/19 1:22 PM, Chris Wilson wrote:
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


What's the issue from your POV? We've been using it with little changes for GuC submission and IMO it flows relatively well, mainly just using a different tasklet and slightly different cops (need to call into GuC for pin/unpin).

Daniele
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx



[Index of Archives]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux