[PATCH] drm/radeon: add an exclusive lock for GPU reset v2

2012-07-06 Thread Christian König
On 02.07.2012 18:45, j.glisse at gmail.com wrote: > From: Jerome Glisse > > GPU reset need to be exclusive, one happening at a time. For this > add a rw semaphore so that any path that trigger GPU activities > have to take the semaphore as a reader thus allowing concurency. > > The GPU reset path

Re: [PATCH] drm/radeon: add an exclusive lock for GPU reset v2

2012-07-06 Thread Christian König
On 02.07.2012 18:45, j.gli...@gmail.com wrote: From: Jerome Glisse GPU reset need to be exclusive, one happening at a time. For this add a rw semaphore so that any path that trigger GPU activities have to take the semaphore as a reader thus allowing concurency. The GPU reset path take the sema

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-03 Thread Christian König
On 03.07.2012 16:09, Jerome Glisse wrote: > On Tue, Jul 3, 2012 at 5:26 AM, Christian K?nig > wrote: >> [SNIP] >> Yeah, but I thought that fixing those oops as the second step. I see the >> fact that suspend/resume is unpinning all the ttm memory and then pinning it >> again as a bug that needs t

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-03 Thread Christian König
On 02.07.2012 19:27, Jerome Glisse wrote: > On Mon, Jul 2, 2012 at 1:05 PM, Christian K?nig > wrote: >> On 02.07.2012 18:41, Jerome Glisse wrote: >>> On Mon, Jul 2, 2012 at 12:26 PM, Christian K?nig >>> wrote: On 02.07.2012 17:39, j.glisse at gmail.com wrote: > From: Jerome Glisse

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-03 Thread Jerome Glisse
On Tue, Jul 3, 2012 at 10:52 AM, Christian K?nig wrote: > On 03.07.2012 16:09, Jerome Glisse wrote: >> >> On Tue, Jul 3, 2012 at 5:26 AM, Christian K?nig >> wrote: >>> >>> [SNIP] >>> >>> Yeah, but I thought that fixing those oops as the second step. I see the >>> fact that suspend/resume is unpin

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-03 Thread Jerome Glisse
On Tue, Jul 3, 2012 at 5:26 AM, Christian K?nig wrote: > On 02.07.2012 19:27, Jerome Glisse wrote: >> >> On Mon, Jul 2, 2012 at 1:05 PM, Christian K?nig >> wrote: >>> >>> On 02.07.2012 18:41, Jerome Glisse wrote: On Mon, Jul 2, 2012 at 12:26 PM, Christian K?nig wrote: > >

Re: [PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-03 Thread Jerome Glisse
On Tue, Jul 3, 2012 at 10:52 AM, Christian König wrote: > On 03.07.2012 16:09, Jerome Glisse wrote: >> >> On Tue, Jul 3, 2012 at 5:26 AM, Christian König >> wrote: >>> >>> [SNIP] >>> >>> Yeah, but I thought that fixing those oops as the second step. I see the >>> fact that suspend/resume is unpin

Re: [PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-03 Thread Christian König
On 03.07.2012 16:09, Jerome Glisse wrote: On Tue, Jul 3, 2012 at 5:26 AM, Christian König wrote: [SNIP] Yeah, but I thought that fixing those oops as the second step. I see the fact that suspend/resume is unpinning all the ttm memory and then pinning it again as a bug that needs to be fixed. Or

Re: [PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-03 Thread Jerome Glisse
On Tue, Jul 3, 2012 at 5:26 AM, Christian König wrote: > On 02.07.2012 19:27, Jerome Glisse wrote: >> >> On Mon, Jul 2, 2012 at 1:05 PM, Christian König >> wrote: >>> >>> On 02.07.2012 18:41, Jerome Glisse wrote: On Mon, Jul 2, 2012 at 12:26 PM, Christian König wrote: > >

Re: [PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-03 Thread Christian König
On 02.07.2012 19:27, Jerome Glisse wrote: On Mon, Jul 2, 2012 at 1:05 PM, Christian König wrote: On 02.07.2012 18:41, Jerome Glisse wrote: On Mon, Jul 2, 2012 at 12:26 PM, Christian König wrote: On 02.07.2012 17:39, j.gli...@gmail.com wrote: From: Jerome Glisse GPU reset need to be exclus

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread Christian König
On 02.07.2012 18:41, Jerome Glisse wrote: > On Mon, Jul 2, 2012 at 12:26 PM, Christian K?nig > wrote: >> On 02.07.2012 17:39, j.glisse at gmail.com wrote: >>> From: Jerome Glisse >>> >>> GPU reset need to be exclusive, one happening at a time. For this >>> add a rw semaphore so that any path that

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread Christian König
On 02.07.2012 17:39, j.glisse at gmail.com wrote: > From: Jerome Glisse > > GPU reset need to be exclusive, one happening at a time. For this > add a rw semaphore so that any path that trigger GPU activities > have to take the semaphore as a reader thus allowing concurency. > > The GPU reset path

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread Jerome Glisse
On Mon, Jul 2, 2012 at 1:05 PM, Christian K?nig wrote: > On 02.07.2012 18:41, Jerome Glisse wrote: >> >> On Mon, Jul 2, 2012 at 12:26 PM, Christian K?nig >> wrote: >>> >>> On 02.07.2012 17:39, j.glisse at gmail.com wrote: From: Jerome Glisse GPU reset need to be exclusive, o

[PATCH] drm/radeon: add an exclusive lock for GPU reset v2

2012-07-02 Thread j.gli...@gmail.com
From: Jerome Glisse GPU reset need to be exclusive, one happening at a time. For this add a rw semaphore so that any path that trigger GPU activities have to take the semaphore as a reader thus allowing concurency. The GPU reset path take the semaphore as a writer ensuring that no concurrent res

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread Jerome Glisse
On Mon, Jul 2, 2012 at 12:26 PM, Christian K?nig wrote: > On 02.07.2012 17:39, j.glisse at gmail.com wrote: >> >> From: Jerome Glisse >> >> GPU reset need to be exclusive, one happening at a time. For this >> add a rw semaphore so that any path that trigger GPU activities >> have to take the sema

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread Jerome Glisse
On Mon, Jul 2, 2012 at 11:39 AM, wrote: > From: Jerome Glisse > > GPU reset need to be exclusive, one happening at a time. For this > add a rw semaphore so that any path that trigger GPU activities > have to take the semaphore as a reader thus allowing concurency. > > The GPU reset path take the

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread j.gli...@gmail.com
From: Jerome Glisse GPU reset need to be exclusive, one happening at a time. For this add a rw semaphore so that any path that trigger GPU activities have to take the semaphore as a reader thus allowing concurency. The GPU reset path take the semaphore as a writer ensuring that no concurrent res

Re: [PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread Jerome Glisse
On Mon, Jul 2, 2012 at 1:05 PM, Christian König wrote: > On 02.07.2012 18:41, Jerome Glisse wrote: >> >> On Mon, Jul 2, 2012 at 12:26 PM, Christian König >> wrote: >>> >>> On 02.07.2012 17:39, j.gli...@gmail.com wrote: From: Jerome Glisse GPU reset need to be exclusive, one h

Re: [PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread Christian König
On 02.07.2012 18:41, Jerome Glisse wrote: On Mon, Jul 2, 2012 at 12:26 PM, Christian König wrote: On 02.07.2012 17:39, j.gli...@gmail.com wrote: From: Jerome Glisse GPU reset need to be exclusive, one happening at a time. For this add a rw semaphore so that any path that trigger GPU activiti

[PATCH] drm/radeon: add an exclusive lock for GPU reset v2

2012-07-02 Thread j . glisse
From: Jerome Glisse GPU reset need to be exclusive, one happening at a time. For this add a rw semaphore so that any path that trigger GPU activities have to take the semaphore as a reader thus allowing concurency. The GPU reset path take the semaphore as a writer ensuring that no concurrent res

Re: [PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread Jerome Glisse
On Mon, Jul 2, 2012 at 12:26 PM, Christian König wrote: > On 02.07.2012 17:39, j.gli...@gmail.com wrote: >> >> From: Jerome Glisse >> >> GPU reset need to be exclusive, one happening at a time. For this >> add a rw semaphore so that any path that trigger GPU activities >> have to take the semapho

Re: [PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread Christian König
On 02.07.2012 17:39, j.gli...@gmail.com wrote: From: Jerome Glisse GPU reset need to be exclusive, one happening at a time. For this add a rw semaphore so that any path that trigger GPU activities have to take the semaphore as a reader thus allowing concurency. The GPU reset path take the sema

Re: [PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread Jerome Glisse
On Mon, Jul 2, 2012 at 11:39 AM, wrote: > From: Jerome Glisse > > GPU reset need to be exclusive, one happening at a time. For this > add a rw semaphore so that any path that trigger GPU activities > have to take the semaphore as a reader thus allowing concurency. > > The GPU reset path take the

[PATCH] drm/radeon: add an exclusive lock for GPU reset

2012-07-02 Thread j . glisse
From: Jerome Glisse GPU reset need to be exclusive, one happening at a time. For this add a rw semaphore so that any path that trigger GPU activities have to take the semaphore as a reader thus allowing concurency. The GPU reset path take the semaphore as a writer ensuring that no concurrent res