Re: [Intel-gfx] [PATCH] agp/intel: Reinforce the barrier after GTT updates

Hi [This is an automated email] This commit has been processed because it contains a "Fixes:" tag fixing commit: 983d308cb8f6 ("agp/intel: Serialise after GTT updates"). The bot has tested the following trees: v5.6.5, v5.5.18, v5.4.33, v4.19.116, v4.14.176, v4.9.219, v4.4.219. v5.6.5: Build OK

Re: [Intel-gfx] [PATCH] agp/intel: Reinforce the barrier after GTT updates

Hi Chris, > After changing the timing between GTT updates and execution on the GPU, > we started seeing sporadic failures on Ironlake. These were narrowed > down to being an insufficiently strong enough barrier/delay after > updating the GTT and scheduling execution on the GPU. By forcing the > un

[Intel-gfx] [PATCH] agp/intel: Reinforce the barrier after GTT updates

After changing the timing between GTT updates and execution on the GPU, we started seeing sporadic failures on Ironlake. These were narrowed down to being an insufficiently strong enough barrier/delay after updating the GTT and scheduling execution on the GPU. By forcing the uncached read, and addi

[Intel-gfx] [PATCH] agp/intel: Reinforce the barrier after GTT updates

From: Chris Wilson After changing the timing between GTT updates and execution on the GPU, we started seeing sporadic failures on Ironlake. These were narrowed down to being an insufficiently strong enough barrier/delay after updating the GTT and scheduling execution on the GPU. By forcing the un