On 22/05/2025 15:06, Philipp Stanner wrote:
On Wed, 2025-05-21 at 11:24 +0100, Tvrtko Ursulin wrote:
On 21/05/2025 11:04, Philipp Stanner wrote:
When the unit tests were implemented, each scheduler job got its
own,
distinct lock. This is not how dma_fence context locking rules are
to be
impl
On Wed, 2025-05-21 at 11:24 +0100, Tvrtko Ursulin wrote:
>
> On 21/05/2025 11:04, Philipp Stanner wrote:
> > When the unit tests were implemented, each scheduler job got its
> > own,
> > distinct lock. This is not how dma_fence context locking rules are
> > to be
> > implemented. All jobs belongin
On 21/05/2025 11:04, Philipp Stanner wrote:
When the unit tests were implemented, each scheduler job got its own,
distinct lock. This is not how dma_fence context locking rules are to be
implemented. All jobs belonging to the same fence context (in this case:
scheduler) should share a lock for
