r300g is able to sleep until a fence completes rather than busywait because
it creates a special buffer object and relocation that stays busy until the
CS containing the fence is finished.
Copy the idea into r600g, and use it to sleep if the user asked for an
infinite wait, falling back to busywai
On Wednesday 1 February 2012, Michel Dänzer wrote:
> On Mit, 2012-02-01 at 15:01 +, Simon Farnsworth wrote:
> > + if (sleep_bo) {
> > + unsigned reloc_index;
> > + /* Create a dummy BO so that fence_finish without a timeout can
> > sleep waiting for completion */
> > +
[ Dropping dri-devel list ]
On Mit, 2012-02-01 at 15:01 +, Simon Farnsworth wrote:
> r300g is able to sleep until a fence completes rather than busywait because
> it creates a special buffer object and relocation that stays busy until the
> CS containing the fence is finished.
>
> Copy the i
On Wednesday 1 February 2012, Simon Farnsworth
wrote:
> This is a userspace only fix for my problem, as suggested by Mark Olšák. It
My apologies, Marek; my typing appears to have failed me, and renamed you to
Mark. I shall try not to make that mistake again.
--
Simon Farnsworth
Software Enginee
r300g is able to sleep until a fence completes rather than busywait because
it creates a special buffer object and relocation that stays busy until the
CS containing the fence is finished.
Copy the idea into r600g, and use it to sleep if the user asked for an
infinite wait, falling back to busywai
