drm/i915: Use a slab for object allocation

Browse source

The primary purpose of this was to debug some use-after-free memory
corruption that was causing an OOPS inside drm/i915. As it turned out
the corruption was being caused elsewhere and i915.ko as a major user of
many objects was being hit hardest.

Indeed as we do frequent the generic kmalloc caches, dedicating one to
ourselves (or at least naming one for us depending upon the core) aids
debugging our own slab usage.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

...

This commit is contained in:

Chris Wilson 2012-11-15 11:32:30 +00:00 • committed by Daniel Vetter

parent 8040513870

commit 42dcedd4f2

5 changed files with 34 additions and 10 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

3

drivers/gpu/drm/i915/i915_dma.c

View file

4

drivers/gpu/drm/i915/i915_drv.h

View file

28

drivers/gpu/drm/i915/i915_gem.c

View file

5

drivers/gpu/drm/i915/i915_gem_dmabuf.c

View file

4

drivers/gpu/drm/i915/i915_gem_stolen.c

View file