[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <526E9808.4030607@gmail.com>
Date: Mon, 28 Oct 2013 10:59:52 -0600
From: David Ahern <dsahern@...il.com>
To: Pekka Enberg <penberg@....fi>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
CC: Hemant Kumar <hkshaw@...ux.vnet.ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Oleg Nesterov <oleg@...hat.com>,
"hegdevasant@...ux.vnet.ibm.com" <hegdevasant@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...hat.com>,
"anton@...hat.com" <anton@...hat.com>,
"systemtap@...rceware.org" <systemtap@...rceware.org>,
Namhyung Kim <namhyung@...nel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
"aravinda@...ux.vnet.ibm.com" <aravinda@...ux.vnet.ibm.com>
Subject: Re: [PATCH v4 2/3] Support for perf to probe into SDT markers:
On 10/28/13 2:48 AM, Pekka Enberg wrote:
> So I really hope this SDT effort and the ktap effort at least
> make some effort in unifying all the nice functionality that's
> simple to use and easy to discover. I really, really would
> at the end of the day, just 'perf trace' like I 'perf stat' or
> 'perf record'.
Agree. I see user's eyes glaze over with each command line option, and
we have added aliases to embed some of the details as well as having
sensible defaults.
I often use perf-list to lookup an exact event name, and I do not want
to see it taking many seconds to minutes to run (not everyone is running
on an SSD). I also run perf on many different OS versions with an NFS
home directory, and do not want to see a cache explosion (I have buildid
disabled for this reason).
David
--
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