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

2012-07-17 Thread Christian König
On 17.07.2012 16:17, Jerome Glisse wrote: > On Tue, Jul 17, 2012 at 8:51 AM, Alex Deucher > wrote: >> On Tue, Jul 17, 2012 at 4:49 AM, Christian K?nig >> wrote: >>> On 17.07.2012 01:13, Alex Deucher wrote: On Fri, Jul 13, 2012 at 9:57 AM, Alex Deucher wrote: > On Fri, Jul 13, 2012

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

2012-07-17 Thread Christian König
On 17.07.2012 01:13, Alex Deucher wrote: > On Fri, Jul 13, 2012 at 9:57 AM, Alex Deucher > wrote: >> On Fri, Jul 13, 2012 at 9:46 AM, Christian K?nig >> wrote: >>> On 13.07.2012 14:27, Alex Deucher wrote: On Fri, Jul 13, 2012 at 5:09 AM, Christian K?nig wrote: > On 12.07.2012 18:3

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

2012-07-17 Thread Jerome Glisse
On Tue, Jul 17, 2012 at 8:51 AM, Alex Deucher wrote: > On Tue, Jul 17, 2012 at 4:49 AM, Christian K?nig > wrote: >> On 17.07.2012 01:13, Alex Deucher wrote: >>> >>> On Fri, Jul 13, 2012 at 9:57 AM, Alex Deucher >>> wrote: On Fri, Jul 13, 2012 at 9:46 AM, Christian K?nig wrote: >>

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

2012-07-17 Thread Alex Deucher
On Tue, Jul 17, 2012 at 4:49 AM, Christian K?nig wrote: > On 17.07.2012 01:13, Alex Deucher wrote: >> >> On Fri, Jul 13, 2012 at 9:57 AM, Alex Deucher >> wrote: >>> >>> On Fri, Jul 13, 2012 at 9:46 AM, Christian K?nig >>> wrote: On 13.07.2012 14:27, Alex Deucher wrote: > > On F

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

2012-07-17 Thread Christian König
On 17.07.2012 16:17, Jerome Glisse wrote: On Tue, Jul 17, 2012 at 8:51 AM, Alex Deucher wrote: On Tue, Jul 17, 2012 at 4:49 AM, Christian König wrote: On 17.07.2012 01:13, Alex Deucher wrote: On Fri, Jul 13, 2012 at 9:57 AM, Alex Deucher wrote: On Fri, Jul 13, 2012 at 9:46 AM, Christian Kö

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

2012-07-17 Thread Jerome Glisse
On Tue, Jul 17, 2012 at 8:51 AM, Alex Deucher wrote: > On Tue, Jul 17, 2012 at 4:49 AM, Christian König > wrote: >> On 17.07.2012 01:13, Alex Deucher wrote: >>> >>> On Fri, Jul 13, 2012 at 9:57 AM, Alex Deucher >>> wrote: On Fri, Jul 13, 2012 at 9:46 AM, Christian König wrote: >>

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

2012-07-17 Thread Alex Deucher
On Tue, Jul 17, 2012 at 4:49 AM, Christian König wrote: > On 17.07.2012 01:13, Alex Deucher wrote: >> >> On Fri, Jul 13, 2012 at 9:57 AM, Alex Deucher >> wrote: >>> >>> On Fri, Jul 13, 2012 at 9:46 AM, Christian König >>> wrote: On 13.07.2012 14:27, Alex Deucher wrote: > > On F

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

2012-07-17 Thread Christian König
On 17.07.2012 01:13, Alex Deucher wrote: On Fri, Jul 13, 2012 at 9:57 AM, Alex Deucher wrote: On Fri, Jul 13, 2012 at 9:46 AM, Christian König wrote: On 13.07.2012 14:27, Alex Deucher wrote: On Fri, Jul 13, 2012 at 5:09 AM, Christian König wrote: On 12.07.2012 18:36, Alex Deucher wrote: O

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

2012-07-16 Thread Alex Deucher
On Fri, Jul 13, 2012 at 9:57 AM, Alex Deucher wrote: > On Fri, Jul 13, 2012 at 9:46 AM, Christian K?nig > wrote: >> On 13.07.2012 14:27, Alex Deucher wrote: >>> >>> On Fri, Jul 13, 2012 at 5:09 AM, Christian K?nig >>> wrote: On 12.07.2012 18:36, Alex Deucher wrote: > > On Thu,

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

2012-07-16 Thread Alex Deucher
On Fri, Jul 13, 2012 at 9:57 AM, Alex Deucher wrote: > On Fri, Jul 13, 2012 at 9:46 AM, Christian König > wrote: >> On 13.07.2012 14:27, Alex Deucher wrote: >>> >>> On Fri, Jul 13, 2012 at 5:09 AM, Christian König >>> wrote: On 12.07.2012 18:36, Alex Deucher wrote: > > On Thu,

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

2012-07-13 Thread Christian König
On 13.07.2012 14:27, Alex Deucher wrote: > On Fri, Jul 13, 2012 at 5:09 AM, Christian K?nig > wrote: >> On 12.07.2012 18:36, Alex Deucher wrote: >>> On Thu, Jul 12, 2012 at 12:12 PM, Christian K?nig >>> wrote: Before emitting any indirect buffer, emit the offset of the next valid ring c

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

2012-07-13 Thread Christian König
On 12.07.2012 18:36, Alex Deucher wrote: > On Thu, Jul 12, 2012 at 12:12 PM, 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.

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

2012-07-13 Thread Alex Deucher
On Fri, Jul 13, 2012 at 9:46 AM, Christian K?nig wrote: > On 13.07.2012 14:27, Alex Deucher wrote: >> >> On Fri, Jul 13, 2012 at 5:09 AM, Christian K?nig >> wrote: >>> >>> On 12.07.2012 18:36, Alex Deucher wrote: On Thu, Jul 12, 2012 at 12:12 PM, Christian K?nig wrote: > >

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

2012-07-13 Thread Alex Deucher
On Fri, Jul 13, 2012 at 5:09 AM, Christian K?nig wrote: > On 12.07.2012 18:36, Alex Deucher wrote: >> >> On Thu, Jul 12, 2012 at 12:12 PM, 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

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

2012-07-13 Thread Alex Deucher
On Fri, Jul 13, 2012 at 9:46 AM, Christian König wrote: > On 13.07.2012 14:27, Alex Deucher wrote: >> >> On Fri, Jul 13, 2012 at 5:09 AM, Christian König >> wrote: >>> >>> On 12.07.2012 18:36, Alex Deucher wrote: On Thu, Jul 12, 2012 at 12:12 PM, Christian König wrote: > >

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

2012-07-13 Thread Christian König
On 13.07.2012 14:27, Alex Deucher wrote: On Fri, Jul 13, 2012 at 5:09 AM, Christian König wrote: On 12.07.2012 18:36, Alex Deucher wrote: On Thu, Jul 12, 2012 at 12:12 PM, Christian König wrote: Before emitting any indirect buffer, emit the offset of the next valid ring content if any. This

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

2012-07-13 Thread Alex Deucher
On Fri, Jul 13, 2012 at 5:09 AM, Christian König wrote: > On 12.07.2012 18:36, Alex Deucher wrote: >> >> On Thu, Jul 12, 2012 at 12:12 PM, 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

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

2012-07-13 Thread Christian König
On 12.07.2012 18:36, Alex Deucher wrote: On Thu, Jul 12, 2012 at 12:12 PM, 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 v3

2012-07-12 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 v3: skip over the surface sync for ni and si as wel

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

2012-07-12 Thread Alex Deucher
On Thu, Jul 12, 2012 at 12:12 PM, 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 v3

2012-07-12 Thread Alex Deucher
On Thu, Jul 12, 2012 at 12:12 PM, 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 v3

2012-07-12 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 v3: skip over the surface sync for ni and si as wel