On 7/5/22 01:38, Dmitry Osipenko wrote: ...
Also i915 will run into trouble with attach. In particular since i915 starts a full ww transaction in its attach callback to be able to lock other objects if migration is needed. I think i915 CI would catch this in a selftest.
Seems it indeed it should deadlock. But i915 selftests apparently should've caught it and they didn't, I'll re-check what happened.
The i915 selftests use a separate mock_dmabuf_ops. That's why it works for the selftests, i.e. there is no deadlock.
Thomas, would i915 CI run a different set of tests or will it be the default i915 selftests ran by IGT?
Nevermind, I had a local kernel change that was forgotten about.. it prevented the i915 live tests from running.