From: David Ahern <dsahern@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Michael Rubin <mrubin@google.com>, Ingo Molnar <mingo@elte.hu>,
David Sharp <dhsharp@google.com>,
Vaibhav Nagarnaik <vnagarnaik@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@infradead.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: Fix powerTOP regression with 2.6.39-rc5
Date: Tue, 17 May 2011 07:24:46 -0600 [thread overview]
Message-ID: <4DD2771E.70106@gmail.com> (raw)
In-Reply-To: <1305631152.5456.665.camel@gandalf.stny.rr.com>
On 05/17/11 05:19, Steven Rostedt wrote:
> On Tue, 2011-05-17 at 00:15 -0700, Michael Rubin wrote:
>
>> What is the plan for customers going forward? Is it going to involve
>> removing ftrace in favor for perf? Removing perf in favor for ftrace?
>> We love perf and don't want to see it go away either. We tend to use
>> the two systems differently. Do customers basically have to wait a few
>> years to see not only which system wins but which ones stays on top?
>
> My plan is:
>
> 1) get libperf.so out for user tools to use.
libparsevent or libperf? If you really meant libperf will it be a
superset of the event parsing -- like the inclusion of the plugins infra?
David
>
> 2) Start hacking on code again :)
>
> But I'll make sure that this will not be a burden on Google. There's no
> reason that Google should be punished for using something that is
> mainline, and using the proper ABIs. The code in ftrace is very flexible
> and tools that use ftrace should still work even if we make internal
> changes.
>
> I'll work closely with you to make sure that Google's tools will always
> work with future kernels.
>
>>
>> I apologize if this is obvious to others but I am confused.
>
> No need to apologize, it's a very confusing situation.
>
> -- Steve
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2011-05-17 13:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 20:08 Arjan van de Ven
2011-05-06 20:20 ` Steven Rostedt
2011-05-06 20:51 ` Linus Torvalds
2011-05-06 21:10 ` Steven Rostedt
2011-05-06 21:24 ` Linus Torvalds
2011-05-06 21:14 ` Steven Rostedt
2011-05-06 21:28 ` Linus Torvalds
2011-05-06 21:29 ` Arjan van de Ven
2011-05-06 21:57 ` Steven Rostedt
2011-05-07 6:58 ` Ingo Molnar
2011-05-07 10:45 ` Steven Rostedt
2011-05-07 14:44 ` Ingo Molnar
2011-05-07 17:20 ` Steven Rostedt
2011-05-07 17:59 ` Arjan van de Ven
2011-05-08 21:08 ` Frederic Weisbecker
2011-05-08 21:56 ` Arjan van de Ven
2011-05-07 19:00 ` Ingo Molnar
2011-05-10 3:07 ` Steven Rostedt
2011-05-10 4:44 ` Dave Chinner
2011-05-10 5:39 ` Steven Rostedt
2011-05-10 7:36 ` Dave Chinner
2011-05-10 7:54 ` Ingo Molnar
2011-05-10 8:09 ` Ingo Molnar
2011-05-10 8:32 ` Arjan van de Ven
2011-05-10 8:44 ` Ingo Molnar
2011-05-10 9:14 ` Pekka Enberg
2011-05-10 8:41 ` Ingo Molnar
2011-05-10 13:06 ` Steven Rostedt
2011-05-11 21:51 ` Ingo Molnar
2011-05-11 22:36 ` Steven Rostedt
2011-05-17 7:15 ` Michael Rubin
2011-05-17 11:19 ` Steven Rostedt
2011-05-17 13:24 ` David Ahern [this message]
2011-05-17 13:27 ` Steven Rostedt
2011-05-17 13:30 ` Ingo Molnar
2011-05-10 8:47 ` Ingo Molnar
2011-05-10 10:33 ` Steven Rostedt
2011-05-10 19:13 ` David Sharp
2011-05-09 23:37 ` David Sharp
2011-05-10 7:39 ` 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=4DD2771E.70106@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=dhsharp@google.com \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mrubin@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vnagarnaik@google.com \
/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
Powered by JetHome