From: "Frank Ch. Eigler" <fche@redhat.com>
To: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: penberg@cs.helsinki.fi, cl@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
rdunlap@xenotime.net, mpm@selenic.com
Subject: Re: [RFC PATCH 1/4] kmemtrace: Core implementation.
Date: Tue, 22 Jul 2008 21:26:11 -0400 [thread overview]
Message-ID: <20080723012611.GB28486@redhat.com> (raw)
In-Reply-To: <20080723005002.GA5206@localhost>
Hi -
On Wed, Jul 23, 2008 at 03:50:02AM +0300, Eduard - Gabriel Munteanu wrote:
> [...] Sounds like a good idea, but I'd like to get rid of markers
> and use Mathieu Desnoyers' tracepoints instead. I'm just waiting for
> tracepoints to get closer to inclusion in mainline/-mm.
OK.
> It would be great if tracepoints completely replaced markers, so
> SystemTap would use those instead.
Raw tracepoints are problematic as they require a per-tracepoint C
function signature to be synthesized by the tool (or hard-coded in the
tool or elsewhere). We haven't worked out how best do to this. OTOH,
markers don't require such hard-coding, so are simpler for a general
tool to interface to.
> However, if tracepoints are not ready when kmemtrace is to be merged,
> I'll take your advice and mention markers and SystemTap.
Thanks either way - I'm glad you found an existing tracing mechanism
usable and didn't choose/need to invent your own.
- FChE
--
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:[~2008-07-23 1:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 18:31 [RFC PATCH 0/4] kmemtrace RFC (resend 2) Eduard - Gabriel Munteanu
2008-07-22 18:31 ` [RFC PATCH 1/4] kmemtrace: Core implementation Eduard - Gabriel Munteanu
2008-07-22 18:31 ` [RFC PATCH 2/4] kmemtrace: SLAB hooks Eduard - Gabriel Munteanu
2008-07-22 18:31 ` [RFC PATCH 3/4] kmemtrace: SLUB hooks Eduard - Gabriel Munteanu
2008-07-22 18:31 ` [RFC PATCH 4/4] kmemtrace: SLOB hooks Eduard - Gabriel Munteanu
2008-07-22 21:28 ` [RFC PATCH 1/4] kmemtrace: Core implementation Frank Ch. Eigler
2008-07-23 0:50 ` Eduard - Gabriel Munteanu
2008-07-23 0:55 ` Eduard - Gabriel Munteanu
2008-07-23 1:26 ` Frank Ch. Eigler [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-22 18:36 [RFC PATCH 0/4] kmemtrace RFC (resend 2, fixed wrong Cc) Eduard - Gabriel Munteanu
2008-07-22 18:36 ` [RFC PATCH 1/4] kmemtrace: Core implementation Eduard - Gabriel Munteanu
2008-07-28 9:24 ` Pekka Enberg
2008-07-28 16:29 ` Mathieu Desnoyers
2008-07-28 17:09 ` Matt Mackall
2008-07-28 17:35 ` Eduard - Gabriel Munteanu
2008-07-29 8:25 ` Pekka Enberg
2008-07-17 0:46 [RFC PATCH 0/4] kmemtrace RFC (resubmit 1) Eduard - Gabriel Munteanu
2008-07-17 0:46 ` [RFC PATCH 1/4] kmemtrace: Core implementation Eduard - Gabriel Munteanu
2008-07-17 8:01 ` Pekka Enberg
2008-07-17 18:32 ` Eduard - Gabriel Munteanu
2008-07-18 8:48 ` Pekka J Enberg
2008-07-18 10:13 ` Eduard - Gabriel Munteanu
2008-07-18 14:38 ` Pekka Enberg
2008-07-18 19:40 ` Eduard - Gabriel Munteanu
2008-07-18 20:07 ` Matt Mackall
2008-07-17 21:34 ` Randy Dunlap
2008-07-17 23:49 ` Eduard - Gabriel Munteanu
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=20080723012611.GB28486@redhat.com \
--to=fche@redhat.com \
--cc=cl@linux-foundation.org \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
--cc=rdunlap@xenotime.net \
/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