[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180308130358.GC3701@kernel.org>
Date: Thu, 8 Mar 2018 10:03:58 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Agustin Vega-Frias <agustinv@...eaurora.org>
Cc: linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Andi Kleen <ak@...ux.intel.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>, timur@...eaurora.org
Subject: Re: [RFC V4] perf, tools: Support wildcards on pmu name in dynamic
pmu events
Em Wed, Mar 07, 2018 at 03:35:47PM -0500, Agustin Vega-Frias escreveu:
> +++ b/tools/perf/util/parse-events.y
> @@ -8,6 +8,7 @@
>
> #define YYDEBUG 1
>
> +#include <fnmatch.h>
> #include <linux/compiler.h>
> #include <linux/list.h>
> #include <linux/types.h>
> @@ -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;
+ if (asprintf(&pattern, "?(uncore_)%s*", $1) < 0)
I completely overlook that you were using this and thus needed that
extension, duh, thanks for the patience 8-) and for the new patch.
- Arnaldo
Powered by blists - more mailing lists