[PATCH 1/3] drm/vmwgfx: Don't use memory accounting for kernel-side fence objects

On 2 December 2014 at 21:59, Thomas Hellstrom wrote: > Kernel side fence objects are used when unbinding resources and may thus be > created as part of a memory reclaim operation. This might trigger recursive > memory reclaims and result in the kernel running out of stack space. > > So a simple wa

[PATCH 1/3] drm/vmwgfx: Don't use memory accounting for kernel-side fence objects

On 12/03/2014 02:06 AM, Dave Airlie wrote: > On 2 December 2014 at 21:59, Thomas Hellstrom > wrote: >> Kernel side fence objects are used when unbinding resources and may thus be >> created as part of a memory reclaim operation. This might trigger recursive >> memory reclaims and result in the ke

[PATCH 1/3] drm/vmwgfx: Don't use memory accounting for kernel-side fence objects

Kernel side fence objects are used when unbinding resources and may thus be created as part of a memory reclaim operation. This might trigger recursive memory reclaims and result in the kernel running out of stack space. So a simple way out is to avoid accounting of these fence objects. In princip