linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <clameter@sgi.com>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] slub: add hooks for kmemcheck
Date: Sat, 19 Apr 2008 02:21:32 +0300	[thread overview]
Message-ID: <48092CFC.9090708@cs.helsinki.fi> (raw)
In-Reply-To: <Pine.LNX.4.64.0804181604310.4046@schroedinger.engr.sgi.com>

Hi,

Christoph Lameter wrote:
>>>  Should this not go into some kmemcheck.h file?
>> The implementations of these prototypes are in mm/slub_kmemcheck.c.
>> They are only ever called from slub.c since they represent the
>> interface between SLUB and kmemcheck.
>>
>> Would you rather have it in include/linux/slub_kmemcheck.h?
> 
> Well lets see what Pekka says.

Well, I've tried to push for "generic" kmemcheck hooks so that they can 
be used by SLAB/SLOB too but Vegard has always talked me out of it. Of 
course, I have long forgotten the rationale.

But anyway, slub_kmemcheck.h sounds okay and I wonder if we should put 
it in mm/ instead of include/linux/ as it's not supposed to be included 
by anyone except SLUB?

Christoph Lameter wrote:
>> Currently, with SLAB/SLUB debugging enabled, the page flag will be
>> cleared, then accessed in check_object(), thus generating a few
>> accesses to the page. It is safer to delay the clearing of the page
>> flag until no more accesses can be generated for the page.
> 
> Hmmmm.. Okay that is already dealt with by a patch in Pekka's tree.

And merged by Linus now.

			Pekka

  reply	other threads:[~2008-04-18 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 22:03 [PATCH 3/3] slub: add hooks for kmemcheck Vegard Nossum
2008-04-18 22:12 ` Christoph Lameter
2008-04-18 22:27   ` Vegard Nossum
2008-04-18 23:06     ` Christoph Lameter
2008-04-18 23:21       ` Pekka Enberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-04 13:44 [ANNOUNCE] kmemcheck v7 Vegard Nossum
2008-04-04 13:47 ` [PATCH 3/3] slub: add hooks for kmemcheck Vegard Nossum

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=48092CFC.9090708@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vegard.nossum@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).