From mboxrd@z Thu Jan 1 00:00:00 1970 From: Li Zefan Subject: Re: [PATCH 3/3] perf events: Change perf parameter --pid to process-wide collection instead of thread-wide Date: Thu, 25 Mar 2010 16:02:09 +0800 Message-ID: <4BAB1881.8020500@cn.fujitsu.com> References: <1268904666.2813.172.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Ingo Molnar , Arnaldo Carvalho de Melo , Avi Kivity , Peter Zijlstra , linux-kernel@vger.kernel.org, Sheng Yang , oerg Roedel , Jes Sorensen , Marcelo Tosatti , Gleb Natapov , kvm@vger.kernel.org, zhiteng.huang@intel.com, Zachary Amsden To: "Zhang, Yanmin" Return-path: In-Reply-To: <1268904666.2813.172.camel@localhost> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org Zhang, Yanmin wrote: > From: Zhang, Yanmin > > Parameter --pid (or -p) of perf currently means a thread-wide collection. > For exmaple, if a process whose id is 8888 has 10 threads, 'perf top -p 8888' > just collects the main thread statistics. That's misleading. Users are > used to attach a whole process when debugging a process by gdb. To follow > normal usage style, the patch change --pid to process-wide collection and > add --tid (-t) to mean a thread-wide collection. > > Usage example is: > #perf top -p 8888 > #perf record -p 8888 -f sleep 10 > #perf stat -p 8888 -f sleep 10 > Above commands collect the statistics of all threads of process 8888. > > Signed-off-by: Zhang Yanmin > Seems this patch causes seg faults: # ./perf sched record Segmentation fault # ./perf kmem record Segmentation fault # ./perf timechart record Segmentation fault