On Wed, 2018-01-10 at 08:54 -0800, Kenneth Graunke wrote:
> On Wednesday, January 10, 2018 5:11:21 AM PST Iago Toral wrote:
> > On Mon, 2018-01-08 at 13:30 -0800, Kenneth Graunke wrote:
> > > Growing the batch/state buffer is a lot more dangerous than I
> > > thought.
> > >
> > > A number of
On Wednesday, January 10, 2018 5:11:21 AM PST Iago Toral wrote:
> On Mon, 2018-01-08 at 13:30 -0800, Kenneth Graunke wrote:
> > Growing the batch/state buffer is a lot more dangerous than I
> > thought.
> >
> > A number of places emit multiple state buffer sections, and then
> > write
> > data to
On Mon, 2018-01-08 at 13:30 -0800, Kenneth Graunke wrote:
> Growing the batch/state buffer is a lot more dangerous than I
> thought.
>
> A number of places emit multiple state buffer sections, and then
> write
> data to the returned pointer, or save a pointer to brw-
> >batch.state.bo
> and then
Growing the batch/state buffer is a lot more dangerous than I thought.
A number of places emit multiple state buffer sections, and then write
data to the returned pointer, or save a pointer to brw->batch.state.bo
and then use it in relocations. If each call can grow, this can result
in stale map
