From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ravi Bangoria <ravi.bangoria@amd.com>,
Kajol Jain <kjain@linux.ibm.com>,
John Garry <john.g.garry@oracle.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] perf list: Remove duplicate PMUs
Date: Fri, 25 Aug 2023 11:46:20 -0300 [thread overview]
Message-ID: <ZOi+vNhyUd5oduBQ@kernel.org> (raw)
In-Reply-To: <166e2aad-5e17-3ffa-b140-05f174583ab2@linux.intel.com>
Em Fri, Aug 25, 2023 at 10:05:46AM -0400, Liang, Kan escreveu:
> On 2023-08-25 9:52 a.m., Ian Rogers wrote:
> > When there are multiple PMUs, differing by ordered suffixes, by
> > default only display one. This avoids repeated listing of events, in
> > particular when there are 10s of uncore PMUs. If "-v" is passed to
> > "perf list" then still list all PMUs.
> >
> > Listing fewer PMU/event combinations helps speed the all PMU event
> > tests.
> >
> > Before:
> > ```
> > $ perf list
> > ...
> > uncore_imc_free_running_0/data_read/ [Kernel PMU event]
> > uncore_imc_free_running_0/data_total/ [Kernel PMU event]
> > uncore_imc_free_running_0/data_write/ [Kernel PMU event]
> > uncore_imc_free_running_1/data_read/ [Kernel PMU event]
> > uncore_imc_free_running_1/data_total/ [Kernel PMU event]
> > uncore_imc_free_running_1/data_write/ [Kernel PMU event]
> > ```
> >
> > After:
> > ```
> > $ perf list
> > ...
> > uncore_imc_free_running/data_read/ [Kernel PMU event]
> > uncore_imc_free_running/data_total/ [Kernel PMU event]
> > uncore_imc_free_running/data_write/ [Kernel PMU event]
> > ...
> > $ perf list -v
> > ...
> > uncore_imc_free_running_0/data_read/ [Kernel PMU event]
> > uncore_imc_free_running_0/data_total/ [Kernel PMU event]
> > uncore_imc_free_running_0/data_write/ [Kernel PMU event]
> > uncore_imc_free_running_1/data_read/ [Kernel PMU event]
> > uncore_imc_free_running_1/data_total/ [Kernel PMU event]
> > uncore_imc_free_running_1/data_write/ [Kernel PMU event]
> > ...
> > ```
> >
> > The PMUs are sorted by name then suffix as a part of this change.
> >
> > v5: Improved the 2nd patch's commit message and removed an unused
> > variable as suggested by Kan Liang <kan.liang@linux.intel.com>.
> > v4: Rebase on top of lazy PMU changes. Ignore numeric ordering due to
> > gaps, suggested by Kan Liang <kan.liang@linux.intel.com>. Fold
> > patches 2 & 3 as suggested by John Garry <john.g.garry@oracle.com>
> > (done by accident as part of rebasing).
> > v3: Add detail to patch 1 sorting commit message about the suffix and
> > why sorting is necessary.
> > v2: List all PMUs when "-v" is passed as suggested by John Garry
> > <john.g.garry@oracle.com>.
> >
> > Ian Rogers (2):
> > perf pmus: Sort pmus by name then suffix
> > perf pmus: Skip duplicate PMUs and don't print list suffix by default
>
>
> Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
Thanks, applied.
- Arnaldo
next prev parent reply other threads:[~2023-08-25 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 13:52 [PATCH v5 0/2] perf list: Remove duplicate PMUs Ian Rogers
2023-08-25 13:52 ` [PATCH v5 1/2] perf pmus: Sort pmus by name then suffix Ian Rogers
2023-08-25 14:48 ` Arnaldo Carvalho de Melo
2023-08-25 14:51 ` Arnaldo Carvalho de Melo
2023-08-25 15:56 ` Ian Rogers
2023-08-25 16:49 ` Arnaldo Carvalho de Melo
2023-08-25 20:23 ` Arnaldo Carvalho de Melo
2023-08-25 22:48 ` Ian Rogers
2023-08-25 13:52 ` [PATCH v5 2/2] perf pmus: Skip duplicate PMUs and don't print list suffix by default Ian Rogers
2023-08-25 14:05 ` [PATCH v5 0/2] perf list: Remove duplicate PMUs Liang, Kan
2023-08-25 14:46 ` Arnaldo Carvalho de Melo [this message]
2023-08-29 5:06 ` kajoljain
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=ZOi+vNhyUd5oduBQ@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
/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).