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>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
Kaige Ye <ye@kaige.org>, James Clark <james.clark@arm.com>,
Changbin Du <changbin.du@huawei.com>,
Nick Desaulniers <ndesaulniers@google.com>,
John Garry <john.g.garry@oracle.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf stat: Combine the -A/--no-aggr and --no-merge options
Date: Thu, 14 Dec 2023 18:43:35 -0300 [thread overview]
Message-ID: <ZXt3B_BoGj2LThiI@kernel.org> (raw)
In-Reply-To: <cd3c9e63-1ae8-4106-b4ed-e1332b29a4ce@linux.intel.com>
Em Thu, Dec 14, 2023 at 10:10:57AM -0500, Liang, Kan escreveu:
> On 2023-12-14 1:02 a.m., Ian Rogers wrote:
> > The -A or --no-aggr option disables aggregation of core events:
<SNIP>
> > The --no-merge option disables the aggregation of uncore events:
<SNIP>
> > Having two options confuses users who generally don't appreciate the
> > difference in PMUs. Keep all the options but make it so they all
> > disable aggregation both of core and uncore events:
> > Update the relevant perf-stat man page information.
> Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
Thanks, applied to perf-tools-next.
- Arnaldo
prev parent reply other threads:[~2023-12-14 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 6:02 [PATCH v1] perf stat: Combine the -A/--no-aggr and --no-merge options Ian Rogers
2023-12-14 15:10 ` Liang, Kan
2023-12-14 21:43 ` Arnaldo Carvalho de Melo [this message]
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=ZXt3B_BoGj2LThiI@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=changbin.du@huawei.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kprateek.nayak@amd.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=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=ye@kaige.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).