From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Avi Kivity <avi@qumranet.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
systemtap-ml <systemtap@sources.redhat.com>,
linux-btrace@vger.kernel.org
Subject: Re: [RFC] LTTng merge plan
Date: Tue, 29 Jul 2008 16:18:36 +0000 [thread overview]
Message-ID: <20080729161836.GA10751@redhat.com> (raw)
In-Reply-To: <20080728005405.GA7941@Krystal>
Hi, Mathieu -
> [...]
> Currently, [my merge plan] looks like :
>
> In Ingo's trees :
> - Tracepoints, scheduler tracepoints instrumentation, ftrace port to
> tracepoints
> - Should make it into 2.6.27 since ftrace needs those.
> [...]
This is the tracepoints infrastructure, and ...
> Short-term submission plan
>
> In LTTng patchset
> (http://ltt.polymtl.ca/lttng/patch-2.6.26-0.12.tar.bz2)
>
> - Instrumentation
> - LTTng tracepoints
> - Used by LTTng, SystemTAP and usable specialized probes.
> [...]
... this is the "meat", which includes both the tracepoints
and the the tracepoint-to-marker conversion modules, such as those in
"lttng-instrumentation-*-tracepoint-probes.patch", right?
- FChE
next prev parent reply other threads:[~2008-07-29 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080717155724.897537670@polymtl.ca>
[not found] ` <48862A30.7050701@qumranet.com>
[not found] ` <y0mabg991c3.fsf@ton.toronto.redhat.com>
[not found] ` <488635A7.2030609@qumranet.com>
[not found] ` <20080722221204.GA14661@Krystal>
[not found] ` <488C49CC.8040800@qumranet.com>
2008-07-28 0:54 ` [RFC] LTTng merge plan Mathieu Desnoyers
2008-07-29 16:18 ` Frank Ch. Eigler [this message]
2008-07-29 17:01 ` Mathieu Desnoyers
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=20080729161836.GA10751@redhat.com \
--to=fche@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=linux-btrace@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.com \
--cc=torvalds@linux-foundation.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