Quoting Daniele Ceraolo Spurio (2020-01-15 01:31:36) > We currently wait until we attempt to load the GuC to confirm if we're > in GuC mode or not, at which point a lot of the engine setup has already > happened and needs to be updated for GuC submission. To allow us to get > the setup done directly into GuC mode, we need to commit to using GuC > as soon as possible. I think this is the wrong direction; as I thought the goal was to allow delayed loading of firmware, even going as far as allowing the system to run a browser for the user to get the firmware first. I may be completely wrong about that, but imho I never want to have to build firmware images into the kernel. The transition from execlists to guc could be just set-wedged; delete old engines, build guc engines. [This should also work for guc -> guc.] Throwing away context state is ugly, but simple enough. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
