On Wed, Feb 13, 2013 at 12:51:33PM +0200, Ville Syrj?l? wrote: > On Wed, Feb 13, 2013 at 10:23:28AM +0000, Damien Lespiau wrote: > > On Tue, Jan 29, 2013 at 06:13:34PM +0200, ville.syrjala at linux.intel.com wrote: > > > From: Ville Syrj?l? <ville.syrjala at linux.intel.com> > > > > > > If a GPU reset occurs while a page flip has been submitted to the ring, > > > the flip will never complete once the ring has been reset. > > > > > > The GPU reset can be detected by sampling the reset_counter before the > > > flip is submitted, and then while waiting for the flip, the sampled > > > counter is compared with the current reset_counter value. > > > > > > Signed-off-by: Ville Syrj?l? <ville.syrjala at linux.intel.com> > > > > Reviewed-by: Damien Lespiau <damien.lespiau at intel.com> > > > > You might want to rename reset_counter to flip_reset_counter to indicate > > this field is specific to the flipping code. Other parts of the code > > might need something similar as well? > > IIRC I used flip_reset_counter initially but then I decided it's too > long and dropped the flip_ part. I can change it back if that's what > people prefer. Imo the generic reset_counter name is ok. At least as long as we don't need to keep track of more than one of these per crtc for different things (or if we ever start to add more fine-grained reset domains). -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
