From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Darren Hart <dvhart@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"jason.wessel" <jason.wessel@windriver.com>,
"Ted Ts'o" <tytso@mit.edu>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [RFC][PATCH 0/2] tracing: Have trace_printk()s in the events/ directory
Date: Thu, 18 Nov 2010 14:36:25 +0100 [thread overview]
Message-ID: <20101118133622.GC5344@nowhere> (raw)
In-Reply-To: <1290086486.2109.1512.camel@laptop>
On Thu, Nov 18, 2010 at 02:21:26PM +0100, Peter Zijlstra wrote:
> On Thu, 2010-11-18 at 13:53 +0100, Frederic Weisbecker wrote:
> >
> >
> > An other solution, which have been talking with Thomas yesterday, would be
> > to allow having a single fd for several perf_events at once. That would
> > solve some problems when you have hundreds of events opened (think about
> > wide tracing, or use of all individual syscalls).
>
> I'm working on that, but that doesn't make me like this crap any more.
No problem, we have more important things to focus on for now anyway.
We may unearth it one day if the context makes it more useful.
Thanks.
next prev parent reply other threads:[~2010-11-18 13:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 3:58 [RFC][PATCH 0/2] tracing: Have trace_printk()s in the events/ directory Steven Rostedt
2010-11-18 3:58 ` [RFC][PATCH 1/2] [PATCH 1/2] tracing: Rename trace_printk to ftrace_printk Steven Rostedt
2010-11-18 3:58 ` [RFC][PATCH 2/2] [PATCH 2/2] tracing: Make event based trace_printk() Steven Rostedt
2010-11-18 4:19 ` Steven Rostedt
2010-11-18 5:50 ` Lai Jiangshan
2010-11-18 12:22 ` Steven Rostedt
2010-11-18 11:58 ` Mathieu Desnoyers
2010-11-18 12:14 ` Steven Rostedt
2010-11-18 10:41 ` [RFC][PATCH 0/2] tracing: Have trace_printk()s in the events/ directory Peter Zijlstra
2010-11-18 11:53 ` Steven Rostedt
2010-11-18 12:06 ` Mathieu Desnoyers
2010-11-18 12:14 ` Steven Rostedt
2010-11-18 13:03 ` Mathieu Desnoyers
2010-11-18 12:53 ` Frederic Weisbecker
2010-11-18 13:06 ` Steven Rostedt
2010-11-18 14:02 ` Frederic Weisbecker
2010-11-18 13:21 ` Peter Zijlstra
2010-11-18 13:36 ` Frederic Weisbecker [this message]
2010-11-18 12:39 ` 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=20101118133622.GC5344@nowhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvhart@linux.intel.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.