Re: [Intel-gfx] [PATCH 2/2] drm/i915: Let hardware keep track of ctx buf read pointer

On Mon, Jun 08, 2015 at 01:15:39PM +0300, Ville Syrjälä wrote: > On Mon, Jun 08, 2015 at 12:12:41PM +0300, Mika Kuoppala wrote: > > Chris Wilson writes: > > > > > On Fri, May 22, 2015 at 08:17:22PM +0300, Mika Kuoppala wrote: > > >> We initialize the internal read pointer to zero on init/reset, >

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Let hardware keep track of ctx buf read pointer

On Mon, Jun 08, 2015 at 12:12:41PM +0300, Mika Kuoppala wrote: > Chris Wilson writes: > > > On Fri, May 22, 2015 at 08:17:22PM +0300, Mika Kuoppala wrote: > >> We initialize the internal read pointer to zero on init/reset, > >> but only the reset will actually zero the write pointer. > >> This me

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Let hardware keep track of ctx buf read pointer

On Mon, Jun 08, 2015 at 12:12:41PM +0300, Mika Kuoppala wrote: > Chris Wilson writes: > > > On Fri, May 22, 2015 at 08:17:22PM +0300, Mika Kuoppala wrote: > >> We initialize the internal read pointer to zero on init/reset, > >> but only the reset will actually zero the write pointer. > >> This me

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Let hardware keep track of ctx buf read pointer

Chris Wilson writes: > On Fri, May 22, 2015 at 08:17:22PM +0300, Mika Kuoppala wrote: >> We initialize the internal read pointer to zero on init/reset, >> but only the reset will actually zero the write pointer. >> This means that on module reload we might re-read context >> status buffers that w

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Let hardware keep track of ctx buf read pointer

> -Original Message- > From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of > Chris Wilson > Sent: Saturday, May 23, 2015 5:11 PM > To: Mika Kuoppala > Cc: intel-gfx@lists.freedesktop.org; m...@iki.fi > Subject: Re: [Intel-gfx] [PATCH 2/2] d

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Let hardware keep track of ctx buf read pointer

On Fri, May 22, 2015 at 08:17:22PM +0300, Mika Kuoppala wrote: > We initialize the internal read pointer to zero on init/reset, > but only the reset will actually zero the write pointer. > This means that on module reload we might re-read context > status buffers that were written prior reload. >

[Intel-gfx] [PATCH 2/2] drm/i915: Let hardware keep track of ctx buf read pointer

We initialize the internal read pointer to zero on init/reset, but only the reset will actually zero the write pointer. This means that on module reload we might re-read context status buffers that were written prior reload. It is safest just to let the hardware keep track of the read pointer, so