From: Ingo Molnar <mingo@elte.hu>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH 1/2] kmemleak: Inform kmemleak about kernel stack allocation
Date: Sat, 29 Aug 2009 15:29:54 +0200 [thread overview]
Message-ID: <20090829132954.GB24123@elte.hu> (raw)
In-Reply-To: <20090827170253.27901.33997.stgit@pc1117.cambridge.arm.com>
* Catalin Marinas <catalin.marinas@arm.com> wrote:
> Traversing all the tasks in the system for scanning the kernel
> stacks requires locking which increases the kernel latency
> considerably. This patch informs kmemleak about newly allocated or
> freed stacks so that they are treated as any other allocated
> object. Subsequent patch will remove the explicit stack scanning
> from mm/kmemleak.c.
>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> ---
> arch/x86/include/asm/thread_info.h | 7 ++++++-
> arch/x86/kernel/process.c | 2 ++
> kernel/fork.c | 7 ++++++-
> 3 files changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/include/asm/thread_info.h b/arch/x86/include/asm/thread_info.h
> index fad7d40..f26432a 100644
> --- a/arch/x86/include/asm/thread_info.h
> +++ b/arch/x86/include/asm/thread_info.h
> @@ -162,7 +162,12 @@ struct thread_info {
> #define __HAVE_ARCH_THREAD_INFO_ALLOCATOR
>
> #define alloc_thread_info(tsk) \
> - ((struct thread_info *)__get_free_pages(THREAD_FLAGS, THREAD_ORDER))
> +({ \
> + struct thread_info *ti = (struct thread_info *) \
> + __get_free_pages(THREAD_FLAGS, THREAD_ORDER); \
> + kmemleak_alloc(ti, THREAD_SIZE, 1, THREAD_FLAGS); \
> + ti; \
> +})
Sidenote:this used to be a trivial wrapper to gfp so it was
borderline OK as a CPP macro - now it's a non-trivial CPP wrapper
macro which is not OK. Mind converting it to an inline function?
Ingo
next prev parent reply other threads:[~2009-08-29 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 17:02 [PATCH 0/2] kmemleak: x86-related patches Catalin Marinas
2009-08-27 17:02 ` [PATCH 1/2] kmemleak: Inform kmemleak about kernel stack allocation Catalin Marinas
2009-08-29 13:29 ` Ingo Molnar [this message]
2009-08-29 14:28 ` Catalin Marinas
2009-08-29 15:08 ` Catalin Marinas
2009-08-31 8:45 ` Ingo Molnar
2009-09-01 9:25 ` Catalin Marinas
2009-09-04 6:57 ` Ingo Molnar
2009-09-04 14:45 ` Catalin Marinas
2009-08-31 9:04 ` Paul Mundt
2009-08-27 17:02 ` [PATCH 2/2] kmemleak: Ignore the aperture memory hole on x86_64 Catalin Marinas
2009-08-29 13:31 ` Ingo Molnar
2009-08-29 14:30 ` Catalin Marinas
2009-08-31 8:38 ` Ingo Molnar
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=20090829132954.GB24123@elte.hu \
--to=mingo@elte.hu \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®