Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752287Ab2JEG5Z (ORCPT ); Fri, 5 Oct 2012 02:57:25 -0400 Received: from LGEMRELSE6Q.lge.com ([156.147.1.121]:51578 "EHLO LGEMRELSE6Q.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751968Ab2JEG5V (ORCPT ); Fri, 5 Oct 2012 02:57:21 -0400 X-AuditID: 9c930179-b7bf9ae000000e4c-d7-506e6c119c14 From: Namhyung Kim To: Arnaldo Carvalho de Melo Cc: Peter Zijlstra , Paul Mackerras , Ingo Molnar , LKML , Namhyung Kim Subject: [PATCH 4/5] perf trace: Add -a switch for --all-cpus option Date: Fri, 5 Oct 2012 14:02:15 +0900 Message-Id: <1349413336-26936-4-git-send-email-namhyung@kernel.org> X-Mailer: git-send-email 1.7.11.4 In-Reply-To: <1349413336-26936-1-git-send-email-namhyung@kernel.org> References: <1349413336-26936-1-git-send-email-namhyung@kernel.org> X-Brightmail-Tracker: AAAAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1253 Lines: 31 From: Namhyung Kim Other perf subcommands like record, top and stat use '-a' as a shortcut for --all-cpus option. Just follow the convention. :) Signed-off-by: Namhyung Kim --- tools/perf/builtin-trace.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c index 231b60690ce9..8daac2eef5af 100644 --- a/tools/perf/builtin-trace.c +++ b/tools/perf/builtin-trace.c @@ -311,7 +311,7 @@ int cmd_trace(int argc, const char **argv, const char *prefix __maybe_unused) "trace events on existing process id"), OPT_STRING(0, "tid", &trace.opts.target.tid, "tid", "trace events on existing thread id"), - OPT_BOOLEAN(0, "all-cpus", &trace.opts.target.system_wide, + OPT_BOOLEAN('a', "all-cpus", &trace.opts.target.system_wide, "system-wide collection from all CPUs"), OPT_STRING(0, "cpu", &trace.opts.target.cpu_list, "cpu", "list of cpus to monitor"), -- 1.7.11.4 -- 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/