On Wed, 2026-02-11 at 10:57 +0100, Danilo Krummrich wrote: > (Cc: Xe maintainers) > > On Tue Feb 10, 2026 at 12:40 PM CET, Alice Ryhl wrote: > > On Tue, Feb 10, 2026 at 11:46:44AM +0100, Christian König wrote: > > > On 2/10/26 11:36, Danilo Krummrich wrote: > > > > On Tue Feb 10, 2026 at 11:15 AM CET, Alice Ryhl wrote: > > > > >
[…] > > > > > > > > Or in other words, there must be no more than wq->max_active - 1 works > > > > that > > > > execute code violating the DMA fence signalling rules. > > > > Ouch, is that really the best way to do that? Why not two workqueues? > > Most drivers making use of this re-use the same workqueue for multiple GPU > scheduler instances in firmware scheduling mode (i.e. 1:1 relationship between > scheduler and entity). This is equivalent to the JobQ use-case. > > Note that we will have one JobQ instance per userspace queue, so sharing the > workqueue between JobQ instances can make sense. Why, what for? P.
