mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Peter Zijlstra <peterz@infradead.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org,
	"Frank Ch. Eigler" <fche@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] tracing/markers: make markers select tracepoints
Date: Mon, 23 Feb 2009 09:52:43 +0100	[thread overview]
Message-ID: <20090223085243.GF9582@elte.hu> (raw)
In-Reply-To: <20090223024716.GC5430@Krystal>


* Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:

> * Ingo Molnar (mingo@elte.hu) wrote:
> > 
> > * Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> > 
> > > > > so I wonder why don't we create linux-tracing new mailing 
> > > > > list.
> > 
> > Discussions related to upstream Linux tracing are generally 
> > conducted on lkml.
> > 
> > > > Yes, lets hide it from general view, sounds like a brilliant 
> > > > plan.
> > > 
> > > I guess Kosaki's point is that there may be a disconnect 
> > > between the work that is done on the LTTng side and the ftrace 
> > > side. [...]
> > 
> > Could you please list the items we need to extend the tracing 
> > framework in kernel/tracing/* with so that we can support the 
> > aspects of LTTng you consider important and upstream-worthy?
> > 
> > As i've mentioned it in the past, i'm definitely interested in 
> > helping such an effort to further improve Linux tracing.
> > 
> > 	Ingo
> 
> Hi Ingo,
> 
> I have not merged the "binary trace buffer to ascii" code done 
> by Fujitsu yet because I still have to review it, but when 
> it's ready, I will be ready to post everything that has been 
> identified as wish list for a tracer v2. It includes a very 
> generic buffering infrastructure which have been evolving for 
> the past 4 years (and reviewed on LKML a couple of times in 
> the past).
> 
> So, either I start to merge this last feature, or I can start 
> posting right away without the "binary buffer to ascii" 
> module. The standard mechanism used in LTTng is binary-only, 
> very high speed, and uses a userspace application to transform 
> binary data into text.
> 
> That will let us figure out what overlaps between ftrace and 
> LTTng and find out how those two can fit together.
> 
> Note that for the moment, LTTng sits in the /ltt directory of 
> the kernel tree, so even if we have both tracers at some 
> point, we should not step on each other's foot. That could let 
> us room to figure out how to incrementally combine those 
> tracers if that makes sense.

I think you got me wrong Mathieu. The way to combine those two 
tracers is to do it _before_ it gets merged upstream. We 
obviously dont want to parallel tracing frameworks in the 
upstream kernel.

So ... please lets work on that, okay?

	Ingo

  reply	other threads:[~2009-02-23  8:53 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 16:34 Frederic Weisbecker
2009-02-20 16:59 ` Randy Dunlap
2009-02-20 17:20   ` Frederic Weisbecker
2009-02-20 17:22   ` Ingo Molnar
2009-02-20 17:29     ` Randy Dunlap
2009-02-20 17:31     ` Frederic Weisbecker
2009-02-20 17:48       ` Ingo Molnar
2009-02-20 18:56         ` Jason Baron
2009-02-21  3:15         ` Frederic Weisbecker
2009-02-21 22:04         ` Frank Ch. Eigler
2009-02-22 17:13           ` Ingo Molnar
2009-02-22 17:38             ` Frank Ch. Eigler
2009-02-23 10:13         ` Avi Kivity
2009-02-22  3:23     ` KOSAKI Motohiro
2009-02-22 11:37       ` Peter Zijlstra
2009-02-22 16:04         ` Mathieu Desnoyers
2009-02-22 19:17           ` Ingo Molnar
2009-02-23  2:47             ` Mathieu Desnoyers
2009-02-23  8:52               ` Ingo Molnar [this message]
2009-02-22 11:43     ` Peter Zijlstra
2009-02-22 12:08       ` Frank Ch. Eigler
2009-02-22 12:14         ` Peter Zijlstra
2009-02-22 12:24           ` Frank Ch. Eigler
2009-02-23 11:11             ` Peter Zijlstra
2009-02-23 15:44               ` Frank Ch. Eigler
2009-02-23 16:22                 ` Peter Zijlstra
2009-02-23 17:10                   ` Frank Ch. Eigler
2009-02-23 17:23                     ` Ingo Molnar
2009-02-24 13:01                       ` Frank Ch. Eigler
2009-02-23 17:31                     ` Steven Rostedt
2009-02-23 18:32                       ` Theodore Tso
2009-02-23 22:16                         ` Peter Zijlstra
2009-02-23 22:41                           ` Theodore Tso
2009-02-24  8:55                             ` Peter Zijlstra
2009-02-23  0:23       ` Steven Rostedt
2009-02-21  5:24   ` [PATCH][RFC] check for select dependency errors on config load Steven Rostedt
2009-02-21  5:58     ` Andrew Morton
2009-02-21  6:08     ` Andrew Morton
2009-02-21  6:20       ` Randy Dunlap
2009-02-21 20:07         ` Steven Rostedt
2009-02-21 20:46           ` [PATCH v2] kconfig: " Steven Rostedt
2009-02-21 20:48             ` Steven Rostedt
2009-02-21 21:51             ` Sam Ravnborg
2009-02-21 21:53               ` Steven Rostedt
2009-02-22 16:23     ` [PATCH][RFC] " 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=20090223085243.GF9582@elte.hu \
    --to=mingo@elte.hu \
    --cc=fche@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=peterz@infradead.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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®