All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 23/24] drm/i915: Use a slab for object allocation
Date: Thu, 30 Aug 2012 11:50:29 -0700	[thread overview]
Message-ID: <20120830115029.4d5d51cc@bwidawsk.net> (raw)
In-Reply-To: <1346340679-7699-24-git-send-email-chris@chris-wilson.co.uk>

On Thu, 30 Aug 2012 16:31:18 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> 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>
Acked-by: Ben Widawsky <ben@bwidawsk.net>

-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2012-08-30 18:50 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30 15:30 Next iteration of stolen support Chris Wilson
2012-08-30 15:30 ` [PATCH 01/24] drm/i915: Introduce drm_i915_gem_object_ops Chris Wilson
2012-08-30 15:30 ` [PATCH 02/24] drm/i915: Pin backing pages whilst exporting through a dmabuf vmap Chris Wilson
2012-08-30 15:30 ` [PATCH 03/24] drm/i915: Pin backing pages for pwrite Chris Wilson
2012-08-30 15:30 ` [PATCH 04/24] drm/i915: Pin backing pages for pread Chris Wilson
2012-08-30 15:31 ` [PATCH 05/24] drm/i915: Replace the array of pages with a scatterlist Chris Wilson
2012-08-30 15:31 ` [PATCH 06/24] drm/i915: Convert the dmabuf object to use the new i915_gem_object_ops Chris Wilson
2012-08-30 15:31 ` [PATCH 07/24] drm: Introduce drm_mm_create_block() Chris Wilson
2012-08-30 15:31 ` [PATCH 08/24] drm/i915: Fix detection of stolen base for gen2 Chris Wilson
2012-08-30 15:31 ` [PATCH 09/24] drm/i915: Fix location of stolen memory register for SandyBridge+ Chris Wilson
2012-08-30 15:31 ` [PATCH 10/24] drm/i915: Avoid clearing preallocated regions from the GTT Chris Wilson
2012-08-30 15:31 ` [PATCH 11/24] drm: Introduce an iterator over holes in the drm_mm range manager Chris Wilson
2012-10-25 19:22   ` Daniel Vetter
2012-10-25 20:54     ` Ben Widawsky
2012-10-26 10:55       ` Chris Wilson
2012-08-30 15:31 ` [PATCH 12/24] drm/i915: Delay allocation of stolen space for FBC Chris Wilson
2012-08-30 15:31 ` [PATCH 13/24] drm/i915: Defer allocation of stolen memory for FBC until first use Chris Wilson
2012-08-30 15:31 ` [PATCH 14/24] drm/i915: Allow objects to be created with no backing pages, but stolen space Chris Wilson
2012-08-30 15:31 ` [PATCH 15/24] drm/i915: Differentiate between prime and stolen objects Chris Wilson
2012-08-30 15:31 ` [PATCH 16/24] drm/i915: Support readback of stolen objects upon error Chris Wilson
2012-08-30 15:31 ` [PATCH 17/24] drm/i915: Handle stolen objects in pwrite Chris Wilson
2012-08-30 15:31 ` [PATCH 18/24] drm/i915: Handle stolen objects for pread Chris Wilson
2012-08-30 15:31 ` [PATCH 19/24] drm/i915: Introduce i915_gem_object_create_stolen() Chris Wilson
2012-08-30 15:31 ` [PATCH 20/24] drm/i915: Allocate fbcon from stolen memory Chris Wilson
2012-08-30 15:31 ` [PATCH 21/24] drm/i915: Allocate ringbuffers " Chris Wilson
2012-08-30 15:31 ` [PATCH 22/24] drm/i915: Allocate overlay registers " Chris Wilson
2012-08-30 15:31 ` [PATCH 23/24] drm/i915: Use a slab for object allocation Chris Wilson
2012-08-30 18:50   ` Ben Widawsky [this message]
2012-08-30 15:31 ` [PATCH 24/24] drm/i915: Introduce mapping of user pages into video memory (userptr) ioctl Chris Wilson
2012-08-30 16:22 ` Next iteration of stolen support Chris Wilson
2012-09-04 20:02 Stolen memory, again Chris Wilson
2012-09-04 20:03 ` [PATCH 23/24] drm/i915: Use a slab for object allocation Chris Wilson
2012-10-11 18:55   ` Jesse Barnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120830115029.4d5d51cc@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.