Quoting Chris Wilson (2018-04-18 12:41:49) > Today we only want to pass along the priority to engine->schedule(), but > in the future we want to have much more control over the various aspects > of the GPU during a context's execution, for example controlling the > frequency allowed. As we need an ever growing number of parameters for > scheduling, move those into a struct for convenience. > > v2: Move the anonymous struct into its own function for legibility and > ye olde gcc. > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx> Regards, Joonas _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
