Quoting Mika Kuoppala (2018-05-22 12:24:59) > Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> writes: > > > Extend the i915 load to (optionally) pass a write hazard between > > engines, causing us to wait on the interrupt between engines. Thus > > adding MI_USER_INTERRUPT irq handling to our list of sins. > > > Is it the eb_move_to_gpu waiting then for the object > due to write? Don't be silly! That was like 3 years ago :-p > ..and this then arming the interrupts later down the > chain? i915_gem_request_await_object adds the callback for the request to be submitted when its dependencies are complete. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
