[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOJsxLHBZgUB1dSyF=qx2jfMHGs2sfgO5AEgV9h1KSuxejoEXQ@mail.gmail.com>
Date: Fri, 25 Oct 2013 13:25:05 +0200
From: Pekka Enberg <penberg@...nel.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
jovi.zhangwei@...wei.com,
Frédéric Weisbecker <fweisbec@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Steven Rostedt <rostedt@...dmis.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Tom Zanussi <tom.zanussi@...ux.intel.com>,
Namhyung Kim <namhyung@...nel.org>,
David Ahern <dsahern@...il.com>, Jiri Olsa <jolsa@...hat.com>
Subject: Re: ktap inclusion in drivers/staging/?
On Thu, Oct 24, 2013 at 9:58 AM, Ingo Molnar <mingo@...nel.org> wrote:
> - In a similar fashion, it would be nice to see it integrated with
> 'perf probe' or 'perf ktap', so that users can create probes from
> a single place, with coherent syntax and integrated analysis
> capabilities. I.e. there's no reason to not make this a
> relatively pain-less yet very useful transition.
I really hope we don't end up wit 'perf ktap'. As a user, I really don't want
to know what the underlying mechanism is nor learn the command line
idiosyncrasies, I just want to 'perf trace'.
Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists