From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751792AbcEMGBP (ORCPT ); Fri, 13 May 2016 02:01:15 -0400 Received: from LGEAMRELO13.lge.com ([156.147.23.53]:45665 "EHLO lgeamrelo13.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751342AbcEMGBM (ORCPT ); Fri, 13 May 2016 02:01:12 -0400 X-Original-SENDERIP: 156.147.1.127 X-Original-MAILFROM: namhyung@kernel.org X-Original-SENDERIP: 10.177.227.17 X-Original-MAILFROM: namhyung@kernel.org From: Namhyung Kim To: Arnaldo Carvalho de Melo Cc: Ingo Molnar , Peter Zijlstra , Jiri Olsa , LKML , Andi Kleen Subject: [PATCH 3/3] perf stat: Use cpu-clock event for cpu targets Date: Fri, 13 May 2016 15:01:03 +0900 Message-Id: <1463119263-5569-3-git-send-email-namhyung@kernel.org> X-Mailer: git-send-email 2.8.2 In-Reply-To: <1463119263-5569-1-git-send-email-namhyung@kernel.org> References: <1463119263-5569-1-git-send-email-namhyung@kernel.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Currently perf stat always counts task-clock event by default. But it's somewhat confusing for system-wide targets (especially with 'sleep N' as the 'sleep' task just sleeps and doesn't use cputime). Changing to cpu-clock event instead for that case makes more sense IMHO. Signed-off-by: Namhyung Kim --- tools/perf/builtin-stat.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c index 5645a8361de6..d602e9e93dc1 100644 --- a/tools/perf/builtin-stat.c +++ b/tools/perf/builtin-stat.c @@ -1904,6 +1904,9 @@ static int add_default_attributes(void) } if (!evsel_list->nr_entries) { + if (target__has_cpu(&target)) + default_attrs0[0].config = PERF_COUNT_SW_CPU_CLOCK; + if (perf_evlist__add_default_attrs(evsel_list, default_attrs0) < 0) return -1; if (pmu_have_event("cpu", "stalled-cycles-frontend")) { -- 2.8.2