Received: by 10.223.185.111 with SMTP id b44csp54322wrg; Fri, 9 Mar 2018 00:44:10 -0800 (PST) X-Google-Smtp-Source: AG47ELu7ZBSRpgPwIZKVjAdhH8OkL3LQukZxSvfUor++ohRfLj8P8h7IY048UL4rSLWQcL3ImZ5/ X-Received: by 2002:a17:902:6a17:: with SMTP id m23-v6mr26990571plk.342.1520585049932; Fri, 09 Mar 2018 00:44:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520585049; cv=none; d=google.com; s=arc-20160816; b=I5T9AytUAPauGS4JwtcsQlclj37niFQqWyTDPSEIMTCk6TCgMF/ZqJJXByt8u5TQfl 2jDKyilvbow033VLjixlyxG6ZA7rk71HnhyuJs6HAmFjxE+RipewniKhClsYRpEbtm0Z PHsmXKGkI41XSFswCM+gtBAhqorUmi2euR0DMidSCNkIUiWNNI7XE9lUpqCGJxxsW84I F0rcGSD6hrOVVVFTph8xEc8DeOTRvZLl0d+tsXEYAH9mBQSiJm9Gyu4+ay5haaWwVXvH mtaCsHWoyfUIiz6RmzoVWd4Jr7VyQZDjO6ChF2OXviuneNQIGLgz1rr/jFoX8Q1YFYfT wfnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-disposition :content-transfer-encoding:mime-version:robot-unsubscribe:robot-id :git-commit-id:subject:to:references:in-reply-to:reply-to:cc :message-id:from:date:arc-authentication-results; bh=ccPy3++tNONJ6zHrbAha8gko8WQY1SnGnHrhXUoIoR4=; b=VOttVoxRD6tmKPRG6bG9ZLyQ0KXxwIJDDet+gUY8raG0uJQUyK3NNVhVa9qdMkeUX8 X1EXBXEMSlJv8DgbYIiyvCNXNOviXroG3/MLTtm7oeWZYkvDqD+kV3dDdr0mwgjYE2QU onJULG4upan4bKwtdZKgjYVDtjAIM+2diVPZFZYSnakS01nUOWgq3LmYQ1QgY+DUkb7n tEXMIWivaSMYVGJQaoz5AD/7xsZFM5nPwK+DpClmNT/cgPeyoGNAi8VOWH+wdeCWjioR ipwpLt0wWl68K+7fhyim5YVtI3V6nPkKA5mhz9tfCOkFNx+ABt9bXywQF+EE7AloZxVQ gYJw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j8-v6si490339plk.464.2018.03.09.00.43.55; Fri, 09 Mar 2018 00:44:09 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751878AbeCIIml (ORCPT + 99 others); Fri, 9 Mar 2018 03:42:41 -0500 Received: from terminus.zytor.com ([198.137.202.136]:50135 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750913AbeCIImk (ORCPT ); Fri, 9 Mar 2018 03:42:40 -0500 Received: from terminus.zytor.com (localhost [127.0.0.1]) by terminus.zytor.com (8.15.2/8.15.2) with ESMTP id w298gI2b024062; Fri, 9 Mar 2018 00:42:18 -0800 Received: (from tipbot@localhost) by terminus.zytor.com (8.15.2/8.15.2/Submit) id w298gIpA024059; Fri, 9 Mar 2018 00:42:18 -0800 Date: Fri, 9 Mar 2018 00:42:18 -0800 X-Authentication-Warning: terminus.zytor.com: tipbot set sender to tipbot@zytor.com using -f From: tip-bot for Agustin Vega-Frias Message-ID: Cc: alexander.shishkin@linux.intel.com, hpa@zytor.com, mingo@kernel.org, jolsa@kernel.org, namhyung@kernel.org, peterz@infradead.org, linux-kernel@vger.kernel.org, timur@codeaurora.org, acme@redhat.com, ak@linux.intel.com, tglx@linutronix.de, agustinv@codeaurora.org Reply-To: peterz@infradead.org, namhyung@kernel.org, alexander.shishkin@linux.intel.com, hpa@zytor.com, jolsa@kernel.org, mingo@kernel.org, ak@linux.intel.com, acme@redhat.com, agustinv@codeaurora.org, tglx@linutronix.de, linux-kernel@vger.kernel.org, timur@codeaurora.org In-Reply-To: <1520454947-16977-1-git-send-email-agustinv@codeaurora.org> References: <1520454947-16977-1-git-send-email-agustinv@codeaurora.org> To: linux-tip-commits@vger.kernel.org Subject: [tip:perf/core] perf pmu: Support wildcards on pmu name in dynamic pmu events Git-Commit-ID: b2b9d3a3f0211c5d08c7befdf9d4adad48cda315 X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on terminus.zytor.com Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: b2b9d3a3f0211c5d08c7befdf9d4adad48cda315 Gitweb: https://git.kernel.org/tip/b2b9d3a3f0211c5d08c7befdf9d4adad48cda315 Author: Agustin Vega-Frias AuthorDate: Tue, 6 Mar 2018 09:04:42 -0500 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 8 Mar 2018 10:05:25 -0300 perf pmu: Support wildcards on pmu name in dynamic pmu events Starting on v4.12 event parsing code for dynamic pmu events already supports prefix-based matching of multiple pmus when creating dynamic events. E.g., in a system with the following dynamic pmus: mypmu_0 mypmu_1 mypmu_2 mypmu_4 passing mypmu// as an event spec will result in the creation of the event in all of the pmus. This change expands this matching through the use of fnmatch so glob-like expressions can be used to create events in multiple pmus. E.g., in the system described above if a user only wants to create the event in mypmu_0 and mypmu_1, mypmu_[01]// can be passed. Signed-off-by: Agustin Vega-Frias Acked-by: Andi Kleen Acked-by: Jiri Olsa Cc: Alexander Shishkin Cc: linux-arm-kernel@lists.infradead.org Cc: Namhyung Kim Cc: Peter Zijlstra Cc: Timur Tabi Change-Id: Icb25653fc5d5239c20f3bffdfdf4ab4c9c9bb20b Link: http://lkml.kernel.org/r/1520454947-16977-1-git-send-email-agustinv@codeaurora.org Signed-off-by: Arnaldo Carvalho de Melo --- tools/perf/Documentation/perf-list.txt | 8 +++++++- tools/perf/Documentation/perf-stat.txt | 13 +++++++++++++ tools/perf/util/parse-events.l | 2 +- tools/perf/util/parse-events.y | 14 ++++++++++++-- 4 files changed, 33 insertions(+), 4 deletions(-) diff --git a/tools/perf/Documentation/perf-list.txt b/tools/perf/Documentation/perf-list.txt index e2a897ae3596..2549c34a7895 100644 --- a/tools/perf/Documentation/perf-list.txt +++ b/tools/perf/Documentation/perf-list.txt @@ -141,7 +141,13 @@ on the first memory controller on socket 0 of a Intel Xeon system Each memory controller has its own PMU. Measuring the complete system bandwidth would require specifying all imc PMUs (see perf list output), -and adding the values together. +and adding the values together. To simplify creation of multiple events, +prefix and glob matching is supported in the PMU name, and the prefix +'uncore_' is also ignored when performing the match. So the command above +can be expanded to all memory controllers by using the syntaxes: + + perf stat -C 0 -a imc/cas_count_read/,imc/cas_count_write/ -I 1000 ... + perf stat -C 0 -a *imc*/cas_count_read/,*imc*/cas_count_write/ -I 1000 ... This example measures the combined core power every second diff --git a/tools/perf/Documentation/perf-stat.txt b/tools/perf/Documentation/perf-stat.txt index 2b38e222016a..628026dbedc5 100644 --- a/tools/perf/Documentation/perf-stat.txt +++ b/tools/perf/Documentation/perf-stat.txt @@ -49,6 +49,13 @@ report:: parameters are defined by corresponding entries in /sys/bus/event_source/devices//format/* + Note that the last two syntaxes support prefix and glob matching in + the PMU name to simplify creation of events accross multiple instances + of the same type of PMU in large systems (e.g. memory controller PMUs). + Multiple PMU instances are typical for uncore PMUs, so the prefix + 'uncore_' is also ignored when performing this match. + + -i:: --no-inherit:: child tasks do not inherit counters @@ -260,6 +267,12 @@ taskset. --no-merge:: Do not merge results from same PMUs. +When multiple events are created from a single event alias, stat will, +by default, aggregate the event counts and show the result in a single +row. This option disables that behavior and shows the individual events +and counts. Aliases are listed immediately after the Kernel PMU events +by perf list. + --smi-cost:: Measure SMI cost if msr/aperf/ and msr/smi/ events are supported. diff --git a/tools/perf/util/parse-events.l b/tools/perf/util/parse-events.l index 655ecff636a8..a1a01b1ac8b8 100644 --- a/tools/perf/util/parse-events.l +++ b/tools/perf/util/parse-events.l @@ -175,7 +175,7 @@ bpf_source [^,{}]+\.c[a-zA-Z0-9._]* num_dec [0-9]+ num_hex 0x[a-fA-F0-9]+ num_raw_hex [a-fA-F0-9]+ -name [a-zA-Z_*?][a-zA-Z0-9_*?.]* +name [a-zA-Z_*?\[\]][a-zA-Z0-9_*?.\[\]]* name_minus [a-zA-Z_*?][a-zA-Z0-9\-_*?.:]* drv_cfg_term [a-zA-Z0-9_\.]+(=[a-zA-Z0-9_*?\.:]+)? /* If you add a modifier you need to update check_modifier() */ diff --git a/tools/perf/util/parse-events.y b/tools/perf/util/parse-events.y index e81a20ea8d7d..dedf184b5bed 100644 --- a/tools/perf/util/parse-events.y +++ b/tools/perf/util/parse-events.y @@ -8,6 +8,7 @@ #define YYDEBUG 1 +#include #include #include #include @@ -234,6 +235,10 @@ PE_NAME opt_event_config if (parse_events_add_pmu(_parse_state, list, $1, $2)) { struct perf_pmu *pmu = NULL; int ok = 0; + char *pattern; + + if (asprintf(&pattern, "%s*", $1) < 0) + YYABORT; while ((pmu = perf_pmu__scan(pmu)) != NULL) { char *name = pmu->name; @@ -241,14 +246,19 @@ PE_NAME opt_event_config if (!strncmp(name, "uncore_", 7) && strncmp($1, "uncore_", 7)) name += 7; - if (!strncmp($1, name, strlen($1))) { - if (parse_events_copy_term_list(orig_terms, &terms)) + if (!fnmatch(pattern, name, 0)) { + if (parse_events_copy_term_list(orig_terms, &terms)) { + free(pattern); YYABORT; + } if (!parse_events_add_pmu(_parse_state, list, pmu->name, terms)) ok++; parse_events_terms__delete(terms); } } + + free(pattern); + if (!ok) YYABORT; }