From: Gautam Menghani <gautam@linux.ibm.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Howard Chu <howardchu95@gmail.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/3] perf python: Add PMU argument to parse_metrics
Date: Fri, 17 Oct 2025 19:51:03 +0530 [thread overview]
Message-ID: <aPJQz475v3OmCqEl@Gautams-MacBook-Pro.local> (raw)
In-Reply-To: <20251016222228.2926870-2-irogers@google.com>
On Thu, Oct 16, 2025 at 03:22:27PM -0700, Ian Rogers wrote:
> Add an optional PMU argument to parse_metrics to allow restriction of
> the particular metrics to be opened. If no argument is provided then
> all metrics with the given name/group are opened
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/python.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/util/python.c b/tools/perf/util/python.c
> index 779fe1280a56..fa5e4270d182 100644
> --- a/tools/perf/util/python.c
> +++ b/tools/perf/util/python.c
> @@ -2051,7 +2051,7 @@ static PyObject *pyrf__parse_events(PyObject *self, PyObject *args)
>
> static PyObject *pyrf__parse_metrics(PyObject *self, PyObject *args)
> {
> - const char *input;
> + const char *input, *pmu = NULL;
> struct evlist evlist = {};
> PyObject *result;
> PyObject *pcpus = NULL, *pthreads = NULL;
> @@ -2059,14 +2059,14 @@ static PyObject *pyrf__parse_metrics(PyObject *self, PyObject *args)
> struct perf_thread_map *threads;
> int ret;
>
> - if (!PyArg_ParseTuple(args, "s|OO", &input, &pcpus, &pthreads))
> + if (!PyArg_ParseTuple(args, "s|sOO", &input, &pmu, &pcpus, &pthreads))
> return NULL;
>
> threads = pthreads ? ((struct pyrf_thread_map *)pthreads)->threads : NULL;
> cpus = pcpus ? ((struct pyrf_cpu_map *)pcpus)->cpus : NULL;
>
> evlist__init(&evlist, cpus, threads);
> - ret = metricgroup__parse_groups(&evlist, /*pmu=*/"all", input,
> + ret = metricgroup__parse_groups(&evlist, pmu ?: "all", input,
> /*metric_no_group=*/ false,
> /*metric_no_merge=*/ false,
> /*metric_no_threshold=*/ true,
> --
Acked-by: Gautam Menghani <gautam@linux.ibm.com>
next prev parent reply other threads:[~2025-10-17 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 22:22 [PATCH v1 1/3] perf ilist: Don't display deprecated events Ian Rogers
2025-10-16 22:22 ` [PATCH v1 2/3] perf python: Add PMU argument to parse_metrics Ian Rogers
2025-10-17 14:21 ` Gautam Menghani [this message]
2025-10-16 22:22 ` [PATCH v1 3/3] perf ilist: Add PMU information to metrics Ian Rogers
2025-10-19 2:56 ` [PATCH v1 1/3] perf ilist: Don't display deprecated events Namhyung Kim
2025-10-19 6:50 ` Howard Chu
2025-10-19 23:04 ` Ian Rogers
2025-10-20 1:10 ` Namhyung Kim
2025-10-20 2:12 ` Namhyung Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aPJQz475v3OmCqEl@Gautams-MacBook-Pro.local \
--to=gautam@linux.ibm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).