[PATCH 14/15] drm/radeon: record what is next valid wptr for each ring v2

2012-07-11 Thread Christian König
On 10.07.2012 18:56, Jerome Glisse wrote: > On Tue, Jul 10, 2012 at 8:51 AM, Christian K?nig > wrote: >> Before emitting any indirect buffer, emit the offset of the next >> valid ring content if any. This allow code that want to resume >> ring to resume ring right after ib that caused GPU lockup.

Re: [PATCH 14/15] drm/radeon: record what is next valid wptr for each ring v2

2012-07-11 Thread Christian König
On 10.07.2012 18:56, Jerome Glisse wrote: On Tue, Jul 10, 2012 at 8:51 AM, Christian König wrote: Before emitting any indirect buffer, emit the offset of the next valid ring content if any. This allow code that want to resume ring to resume ring right after ib that caused GPU lockup. v2: use s

[PATCH 14/15] drm/radeon: record what is next valid wptr for each ring v2

2012-07-10 Thread Christian König
Before emitting any indirect buffer, emit the offset of the next valid ring content if any. This allow code that want to resume ring to resume ring right after ib that caused GPU lockup. v2: use scratch registers instead of storing it into memory Signed-off-by: Jerome Glisse Signed-off-by: Chris

[PATCH 14/15] drm/radeon: record what is next valid wptr for each ring v2

2012-07-10 Thread Jerome Glisse
On Tue, Jul 10, 2012 at 8:51 AM, Christian K?nig wrote: > Before emitting any indirect buffer, emit the offset of the next > valid ring content if any. This allow code that want to resume > ring to resume ring right after ib that caused GPU lockup. > > v2: use scratch registers instead of storing

Re: [PATCH 14/15] drm/radeon: record what is next valid wptr for each ring v2

2012-07-10 Thread Jerome Glisse
On Tue, Jul 10, 2012 at 8:51 AM, Christian König wrote: > Before emitting any indirect buffer, emit the offset of the next > valid ring content if any. This allow code that want to resume > ring to resume ring right after ib that caused GPU lockup. > > v2: use scratch registers instead of storing

[PATCH 14/15] drm/radeon: record what is next valid wptr for each ring v2

2012-07-10 Thread Christian König
Before emitting any indirect buffer, emit the offset of the next valid ring content if any. This allow code that want to resume ring to resume ring right after ib that caused GPU lockup. v2: use scratch registers instead of storing it into memory Signed-off-by: Jerome Glisse Signed-off-by: Chris