public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <andi@firstfloor.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Arjan van de Ven <arjan@linux.intel.com>,
	ltt-dev@lists.casi.polymtl.ca, linux-kernel@vger.kernel.org,
	pierre-marc.fournier@polymtl.ca,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] New tools: lttngtrace and lttngreport
Date: Wed, 17 Nov 2010 21:38:09 -0500	[thread overview]
Message-ID: <20101118023809.GA700@Krystal> (raw)
In-Reply-To: <20101117220152.GA2915@elte.hu>

* Ingo Molnar (mingo@elte.hu) wrote:
> 
> * Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> 
> > Well, I'm afraid the collection approach "trace" is currently taking won't allow 
> > this kind of dependency wakeup chain tracking, because they focus on tracing 
> > operations happening on a thread and its children, but the reality is that the 
> > wakeup chains often spread outside of this scope.
> >
> > This is why lttngtrace gathers a system-wide trace even though we're mostly 
> > intested in the wait/wakeups of a specific PID.
> 
> Mathieu, what you say is factually wrong - of course perf events allows
> system-wide tracing, it always did.

Ah, good to know. Reading through your announcement, I thought that the "trace"
tool was only following processes and their children (I know that perf allows
system-wide tracing). However, there seems to be some incompatibilities between
the will to make the "trace" tool usable from non-root users and the will to
gather a system-wide trace.

I'm actually struggling with the same issue with lttngtrace. So far, I've taken
the approach to only allow root to perform this kind of operation, which is much
more limiting than what strace currently does.

I was wondering if you had thought about this problem.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com

      reply	other threads:[~2010-11-18  2:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 13:42 [ANNOUNCE] New tools: lttngtrace and lttngreport Mathieu Desnoyers
2010-11-15 16:07 ` Mathieu Desnoyers
2010-11-17 11:37   ` Andi Kleen
2010-11-17 11:47     ` [ltt-dev] " Benjamin Poirier
2010-11-17 17:31     ` Mathieu Desnoyers
2010-11-17 21:44       ` Thomas Gleixner
2010-11-17 22:33         ` Steven Rostedt
2010-11-18 12:57         ` Mathieu Desnoyers
2010-11-17 22:01       ` Ingo Molnar
2010-11-18  2:38         ` Mathieu Desnoyers [this message]

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=20101118023809.GA700@Krystal \
    --to=mathieu.desnoyers@efficios.com \
    --cc=andi@firstfloor.org \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=pierre-marc.fournier@polymtl.ca \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --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