From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Thomas Gleixner <tglx@linutronix.de>,
Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Subject: Re: [RFC PATCH 0/4] perf: Custom contexts
Date: Wed, 16 Mar 2011 14:53:15 +0100 [thread overview]
Message-ID: <20110316135308.GA1774@nowhere> (raw)
In-Reply-To: <1300228374.2250.42.camel@laptop>
On Tue, Mar 15, 2011 at 11:32:54PM +0100, Peter Zijlstra wrote:
> Right, so I don't much like the interface, two new ioctl()s and a flag
> of dubious use.
Do you think we need a new syscall for this new feature.
> How important is this recursive nature of the thing to you:
>
> > It's supposed to support infinite combinations with starter having starters
> > themselves, plus filters, etc...
>
> We've so far avoided recursion like that, we only have single level
> groups etc.
There is actually no recursivity of any sort that the kernel has to handle.
The starter/stopper links are never handled recursively. ie: there is no
loop walking through the entire chain of starter to starter to starter, etc...
It's always only handled between direct related event: starter and target, but
never further.
Only the final effect has recursion properties in the resulting count
or trace.
next prev parent reply other threads:[~2011-03-16 13:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 19:17 [RFC PATCH 0/4] perf: Custom contexts Frederic Weisbecker
2011-03-14 19:18 ` [RFC PATCH 1/4] perf: Starter and stopper events Frederic Weisbecker
2011-03-15 14:36 ` Lin Ming
2011-03-15 17:54 ` Frederic Weisbecker
2011-03-16 14:21 ` Frederic Weisbecker
2011-03-14 19:18 ` [RFC PATCH 3/4] perf: Support for starter and stopper in tools Frederic Weisbecker
2011-03-14 19:18 ` [RFC PATCH 4/4] perf: New --enable-on-starter option Frederic Weisbecker
2011-03-14 20:43 ` [RFC PATCH 0/4] perf: Custom contexts Arnaldo Carvalho de Melo
2011-03-14 20:51 ` Frederic Weisbecker
2011-03-14 21:03 ` Arnaldo Carvalho de Melo
2011-03-14 21:20 ` Frederic Weisbecker
2011-03-14 21:56 ` Arnaldo Carvalho de Melo
2011-03-14 22:19 ` Arnaldo Carvalho de Melo
2011-03-14 22:43 ` Frederic Weisbecker
2011-03-14 23:02 ` Arnaldo Carvalho de Melo
2011-03-15 18:58 ` Frederic Weisbecker
2011-03-15 19:24 ` Arnaldo Carvalho de Melo
2011-03-16 1:03 ` Frederic Weisbecker
2011-03-16 15:47 ` Masami Hiramatsu
2011-03-16 17:53 ` Arnaldo Carvalho de Melo
2011-03-16 18:02 ` Peter Zijlstra
2011-03-15 22:32 ` Peter Zijlstra
2011-03-16 13:53 ` Frederic Weisbecker [this message]
2011-03-16 13:56 ` Peter Zijlstra
2011-03-16 14:02 ` Frederic Weisbecker
2011-03-16 14:31 ` Peter Zijlstra
2011-03-25 14:47 ` Frederic Weisbecker
2011-03-25 15:03 ` Peter Zijlstra
2011-04-13 14:27 ` Frederic Weisbecker
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=20110316135308.GA1774@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=paulus@samba.org \
--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