From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Andi Kleen <ak@linux.intel.com>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
perry.taylor@intel.com, caleb.biggers@intel.com,
kshipra.bopardikar@intel.com, samantha.alt@intel.com,
ahmad.yasin@intel.com, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v3 00/23] Improvements to Intel perf metrics
Date: Tue, 4 Oct 2022 15:09:42 -0300 [thread overview]
Message-ID: <Yzx25psp6o4XDaVs@kernel.org> (raw)
In-Reply-To: <CAP-5=fUFuw-WYj7xVm3WrnggN2NW7pJkznUQ-j3U4fwMB5PdnA@mail.gmail.com>
Em Tue, Oct 04, 2022 at 10:55:56AM -0700, Ian Rogers escreveu:
> On Tue, Oct 4, 2022 at 10:29 AM Andi Kleen <ak@linux.intel.com> wrote:
> > Then if I follow the wiki example here I would expect I need to do
> > $ ./perf stat -M tma_backend_bound_group ~/pmu/pmu-tools/workloads/BC1s
> > Cannot find metric or group `tma_backend_bound_group'
> > but tma_retiring_group doesn't exist. So it seems the methodology isn't
> > fully consistent everywhere? Perhaps the wiki needs to document the
> > supported CPUs and also what part of the hierarchy is supported.
> So I think you've not got Arnaldo's branch with the changes applied.
> Unfortunately the instructions around '_group' are only going to apply
> to Linux 6.1.
I just pushed perf/core with Ian's v3 series, please check with that
one.
- Arnaldo
next prev parent reply other threads:[~2022-10-04 18:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 2:15 [PATCH v3 00/23] Improvements to Intel perf metrics Ian Rogers
2022-10-04 2:15 ` [PATCH v3 01/23] perf expr: Allow a double if expression Ian Rogers
2022-10-04 2:15 ` [PATCH v3 02/23] perf test: Adjust case of test metrics Ian Rogers
2022-10-04 2:15 ` [PATCH v3 03/23] perf expr: Remove jevents case workaround Ian Rogers
2022-10-04 2:15 ` [PATCH v3 04/23] perf metrics: Don't scale counts going into metrics Ian Rogers
2022-10-04 2:15 ` [PATCH v3 07/23] perf vendor events: Update Intel broadwell Ian Rogers
2022-10-04 2:15 ` [PATCH v3 10/23] perf vendor events: Update elkhartlake cpuids Ian Rogers
2022-10-04 2:16 ` [PATCH v3 11/23] perf vendor events: Update Intel haswell Ian Rogers
2022-10-04 2:16 ` [PATCH v3 13/23] perf vendor events: Update Intel icelake Ian Rogers
2022-10-04 2:16 ` [PATCH v3 15/23] perf vendor events: Update Intel ivybridge Ian Rogers
2022-10-04 2:16 ` [PATCH v3 17/23] perf vendor events: Update Intel jaketown Ian Rogers
2022-10-04 2:16 ` [PATCH v3 18/23] perf vendor events: Update Intel sandybridge Ian Rogers
2022-10-04 2:16 ` [PATCH v3 20/23] perf vendor events: Update silvermont cpuids Ian Rogers
2022-10-04 2:16 ` [PATCH v3 22/23] perf vendor events: Update Intel tigerlake Ian Rogers
2022-10-04 2:16 ` [PATCH v3 23/23] perf vendor events: Update Intel broadwellde Ian Rogers
2022-10-04 3:43 ` [PATCH v3 00/23] Improvements to Intel perf metrics Ian Rogers
2022-10-04 17:28 ` Andi Kleen
2022-10-04 17:55 ` Ian Rogers
2022-10-04 18:09 ` Arnaldo Carvalho de Melo [this message]
2022-10-04 18:15 ` Andi Kleen
2022-10-04 18:26 ` Arnaldo Carvalho de Melo
2022-10-04 12:09 ` Arnaldo Carvalho de Melo
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=Yzx25psp6o4XDaVs@kernel.org \
--to=acme@kernel.org \
--cc=ahmad.yasin@intel.com \
--cc=ak@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kshipra.bopardikar@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=samantha.alt@intel.com \
--cc=zhengjun.xing@linux.intel.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).