Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932608Ab2HIM47 (ORCPT ); Thu, 9 Aug 2012 08:56:59 -0400 Received: from mail-ey0-f174.google.com ([209.85.215.174]:38540 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932262Ab2HIM45 (ORCPT ); Thu, 9 Aug 2012 08:56:57 -0400 MIME-Version: 1.0 In-Reply-To: <87zk64yk63.fsf@sejong.aot.lge.com> References: <1344344165-369636-1-git-send-email-avagin@openvz.org> <87mx26z0it.fsf@sejong.aot.lge.com> <878vdqympe.fsf@sejong.aot.lge.com> <87zk64yk63.fsf@sejong.aot.lge.com> Date: Thu, 9 Aug 2012 16:56:56 +0400 Message-ID: Subject: Re: [PATCH 0/4] perf: Teach perf tool to profile sleep times (v2) From: Andrey Wagin To: Namhyung Kim Cc: linux-kernel@vger.kernel.org, Peter Zijlstra , Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1104 Lines: 26 2012/8/9 Namhyung Kim : >>>>> The usage like this is too specific and hard to use IMHO. How about >>>>> putting it somehow into perf sched or new command? >>>>> >>>>> /me don't have an idea though. :-) >>>>> >>>> >>>> I'm going to add a script, so the usage will look like this: >>>> $ perf script record sched-stat -e sched:sched_stat_sleep >>>> This command will collect sched_stat_* and proper sched_switch events >>> >>> ??? That means '-e sched:sched_stat_sleep' part can be removed from >>> command line, no? >> >> No. My method works for all kind of sched_stat_* events, so you need >> to specify an event type which should be traced. > > Ok, so can it be like 'perf script record sched-stat -t sleep '? Yes, it can. Thanks for your feedback. I'm going to write the script, when this series will be committed. -- 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/