public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Pekka Paalanen <pq@iki.fi>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [Patch -tip 3/3] Tracing/ftrace: Don't consume entries unhandled by mmiotrace
Date: Sat, 27 Sep 2008 19:47:56 +0200	[thread overview]
Message-ID: <20080927174756.GF26047@elte.hu> (raw)
In-Reply-To: <c62985530809250913q227a5876k19b1b0ec591ad3cd@mail.gmail.com>


* Frédéric Weisbecker <fweisbec@gmail.com> wrote:

> 2008/9/25 Pekka Paalanen <pq@iki.fi>:
> > We can (must) return to this if/when multiple tracers are allowed
> > to be active simultaneously. But in the current situation, I do not
> > see a way to trace more than one thing, but I haven't really looked
> > into the other tracers.
> 
> You can enable another tracer simultaneously. I never tried it but you 
> can launch one from debugfs and another from kernel code for example. 
> The new boot tracer will have to launch the sched_switch tracer.

hm, right now i can see a lot of problems with that approach - the 
buffers are partly per tracer and partly global.

the new trace-ringbuffer design Steve is working on would abstract away 
this complication - then we could make tracers truly independent 
entities.

	Ingo

  reply	other threads:[~2008-09-27 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25 12:28 [Patch -tip 3/3] Tracing/ftrace: Don't consume entries unhandled by mmiotrace Frédéric Weisbecker
2008-09-25 12:56 ` Ingo Molnar
2008-09-25 14:34 ` Pekka Paalanen
2008-09-25 14:44   ` Frédéric Weisbecker
2008-09-25 15:36     ` Pekka Paalanen
2008-09-25 16:13       ` Frédéric Weisbecker
2008-09-27 17:47         ` Ingo Molnar [this message]
2008-09-27 18:25           ` Steven Rostedt

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=20080927174756.GF26047@elte.hu \
    --to=mingo@elte.hu \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pq@iki.fi \
    --cc=rostedt@goodmis.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