From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH 0/2] ftrace: updates to tip
Date: Sat, 17 Jan 2009 23:34:51 +0100 [thread overview]
Message-ID: <20090117223451.GA27065@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0901162003000.9232@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> > This would allow the creation of "surgical" one-time traces - of
> > events and functions one is specifically interested in.
>
> This all sounds great, but it would add a lot of conditionals into a
> extremely hot function tracer path. [...]
Why would we need more than exactly one unlikely() condition to handle all
of this?
Ingo
next prev parent reply other threads:[~2009-01-17 22:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 0:40 [PATCH 0/2] ftrace: updates to tip Steven Rostedt
2009-01-16 0:40 ` [PATCH 1/2] ftrace: fix trace_output Steven Rostedt
2009-01-16 1:40 ` Andrew Morton
2009-01-16 1:46 ` Steven Rostedt
2009-01-16 0:40 ` [PATCH 2/2] ftrace: add stack trace to function tracer Steven Rostedt
2009-01-16 0:48 ` Steven Rostedt
2009-01-16 10:08 ` Frédéric Weisbecker
2009-01-16 14:28 ` Steven Rostedt
2009-01-16 11:19 ` Ingo Molnar
2009-01-16 11:23 ` [PATCH 0/2] ftrace: updates to tip Ingo Molnar
2009-01-16 13:08 ` Frédéric Weisbecker
2009-01-16 13:10 ` Ingo Molnar
2009-01-16 14:32 ` Steven Rostedt
2009-01-16 15:21 ` Ingo Molnar
2009-01-16 15:53 ` Steven Rostedt
2009-01-16 16:02 ` Ingo Molnar
2009-01-16 16:03 ` Ingo Molnar
2009-01-16 16:22 ` Steven Rostedt
2009-01-16 16:30 ` Ingo Molnar
2009-01-16 22:59 ` Ingo Molnar
2009-01-17 1:14 ` Steven Rostedt
2009-01-17 13:48 ` Frederic Weisbecker
2009-01-17 22:34 ` Ingo Molnar [this message]
2009-01-18 7:27 ` Ingo Molnar
2009-01-16 21:47 ` Chris Mason
2009-01-16 22:26 ` Ingo Molnar
2009-01-17 1:30 ` Chris Mason
2009-01-17 2:38 ` Arnaldo Carvalho de Melo
2009-01-19 13:31 ` 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=20090117223451.GA27065@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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