(2013/10/29 3:45), Pekka Enberg wrote: > On 10/28/13 6:59 PM, David Ahern wrote: > > 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). > > I am talking about reasonable defaults - the 'default' part implies that > people can change the behavior. So we absolutely should also have > something like this for power users such as yourself: > > perf config sdt.scan false
Ah, I like this perf-config to store the default/customized values ;) > That said, the 'reasonable' part suggests that 'perf list' must not take > seconds or minutes (!) for every run. I'd start with implementing a > naive scan and seeing where it takes us. It's not like it's rocket > science to ignore network mounts or revert to a whitelist of paths if > necessary. I think it is reasonable to scan only $PATH and ld.so.cache (the result of ldconfig --print-cache) by default. :) Thank you, -- Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu...@hitachi.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
