[PATCH] drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer.

2010-09-21 Thread Marcin Slusarz
On Tue, Sep 21, 2010 at 02:15:15AM +0200, Francisco Jerez wrote: > It makes sense for a BO to move after a process has requested > exclusive RW access on it (e.g. because the BO used to be located in > unmappable VRAM and we intercepted the CPU access from the fault > handler). > > If we let the g

Re: [PATCH] drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer.

2010-09-21 Thread Marcin Slusarz
On Tue, Sep 21, 2010 at 02:15:15AM +0200, Francisco Jerez wrote: > It makes sense for a BO to move after a process has requested > exclusive RW access on it (e.g. because the BO used to be located in > unmappable VRAM and we intercepted the CPU access from the fault > handler). > > If we let the g

[PATCH] drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer.

2010-09-21 Thread Jerome Glisse
On Mon, Sep 20, 2010 at 8:15 PM, Francisco Jerez wrote: > It makes sense for a BO to move after a process has requested > exclusive RW access on it (e.g. because the BO used to be located in > unmappable VRAM and we intercepted the CPU access from the fault > handler). > > If we let the ghost obj

Re: [PATCH] drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer.

2010-09-21 Thread Jerome Glisse
On Mon, Sep 20, 2010 at 8:15 PM, Francisco Jerez wrote: > It makes sense for a BO to move after a process has requested > exclusive RW access on it (e.g. because the BO used to be located in > unmappable VRAM and we intercepted the CPU access from the fault > handler). > > If we let the ghost obje

[PATCH] drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer.

2010-09-21 Thread Francisco Jerez
It makes sense for a BO to move after a process has requested exclusive RW access on it (e.g. because the BO used to be located in unmappable VRAM and we intercepted the CPU access from the fault handler). If we let the ghost object inherit cpu_writers from the original object, ttm_bo_release_list

[PATCH] drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer.

2010-09-20 Thread Francisco Jerez
It makes sense for a BO to move after a process has requested exclusive RW access on it (e.g. because the BO used to be located in unmappable VRAM and we intercepted the CPU access from the fault handler). If we let the ghost object inherit cpu_writers from the original object, ttm_bo_release_list