On Fri, Oct 14, 2011 at 10:14:54AM +0200, Michel D?nzer wrote:
> [ Dropping stable at kernel.org from CC, it'll get picked up for stable
> once it hits mainline ]
>
> On Don, 2011-10-13 at 16:38 -0400, j.glisse at gmail.com wrote:
> > From: Jerome Glisse
> >
> > After GPU lockup VRAM gart table
[ Dropping stable at kernel.org from CC, it'll get picked up for stable
once it hits mainline ]
On Don, 2011-10-13 at 16:38 -0400, j.glisse at gmail.com wrote:
> From: Jerome Glisse
>
> After GPU lockup VRAM gart table is unpinned and thus its pointer
> becomes unvalid. This patch move the unpi
On Fri, Oct 14, 2011 at 10:14:54AM +0200, Michel Dänzer wrote:
> [ Dropping sta...@kernel.org from CC, it'll get picked up for stable
> once it hits mainline ]
>
> On Don, 2011-10-13 at 16:38 -0400, j.gli...@gmail.com wrote:
> > From: Jerome Glisse
> >
> > After GPU lockup VRAM gart table is un
[ Dropping sta...@kernel.org from CC, it'll get picked up for stable
once it hits mainline ]
On Don, 2011-10-13 at 16:38 -0400, j.gli...@gmail.com wrote:
> From: Jerome Glisse
>
> After GPU lockup VRAM gart table is unpinned and thus its pointer
> becomes unvalid. This patch move the unpin code
From: Jerome Glisse
After GPU lockup VRAM gart table is unpinned and thus its pointer
becomes unvalid. This patch move the unpin code to a common helper
function and set pointer to NULL so that page update code can check
if it should update GPU page table or not. That way bo still bound
to GART c
From: Jerome Glisse
After GPU lockup VRAM gart table is unpinned and thus its pointer
becomes unvalid. This patch move the unpin code to a common helper
function and set pointer to NULL so that page update code can check
if it should update GPU page table or not. That way bo still bound
to GART c
