From: Ezequiel Garcia <elezegarcia@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Tim Bird <tim.bird@am.sony.com>,
Pekka Enberg <penberg@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [RFC/PATCH] scripts/tracing: Add trace_analyze.py tool
Date: Thu, 24 Jan 2013 14:16:35 -0300 [thread overview]
Message-ID: <CALF0-+VRF=ZK7YH8AkrFM2T4QQ4xz8-MdceSHr4biALxZfGdzA@mail.gmail.com> (raw)
In-Reply-To: <20130124055042.GE22654@blaptop>
On Thu, Jan 24, 2013 at 2:50 AM, Minchan Kim <minchan@kernel.org> wrote:
> On Wed, Jan 23, 2013 at 06:37:56PM -0300, Ezequiel Garcia wrote:
>
>>
>> > 2. Does it support alloc_pages family?
>> > kmem event trace already supports it. If it supports, maybe we can replace
>> > CONFIG_PAGE_OWNER hack.
>> >
>>
>> Mmm.. no, it doesn't support alloc_pages and friends, for we found
>> no reason to do it.
>> However, it sounds like a nice idea, on a first thought.
>>
>> I'll review CONFIG_PAGE_OWNER patches and see if I can come up with something.
>
> Thanks!
>
I'm searching CONFIG_PAGE_OWNER patches, but I could only find this one
for v2.6.13:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/broken-out/page-owner-tracking-leak-detector.patch
Is there a more recent one?
--
Ezequiel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-01-24 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 9:46 Ezequiel Garcia
2013-01-22 13:41 ` Pekka Enberg
2013-01-22 16:16 ` Ezequiel Garcia
2013-01-23 4:27 ` Minchan Kim
2013-01-23 21:37 ` Ezequiel Garcia
2013-01-24 5:50 ` Minchan Kim
2013-01-24 17:16 ` Ezequiel Garcia [this message]
2013-01-24 23:24 ` Minchan Kim
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='CALF0-+VRF=ZK7YH8AkrFM2T4QQ4xz8-MdceSHr4biALxZfGdzA@mail.gmail.com' \
--to=elezegarcia@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tim.bird@am.sony.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