From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
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>,
John Garry <john.g.garry@oracle.com>,
Kajol Jain <kjain@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 15/15] perf vendor events intel: Add metricgroup descriptions for all models
Date: Wed, 17 May 2023 11:49:24 -0400 [thread overview]
Message-ID: <fdac0774-30d6-c81b-5eb9-54edaa6f6ff1@linux.intel.com> (raw)
In-Reply-To: <20230517152626.563559-16-irogers@google.com>
On 2023-05-17 11:26 a.m., Ian Rogers wrote:
> + "Memory_BW": "Grouping from metrics spreadsheet",
> + "Memory_Lat": "Grouping from metrics spreadsheet",
Seems there is another place we need to update in the convertor script?
Thanks,
Kan
prev parent reply other threads:[~2023-05-17 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 15:26 [PATCH v2 00/15] Event, metric and metric group improvements Ian Rogers
2023-05-17 15:26 ` [PATCH v2 04/15] perf vendor events intel: Update elkhartlake events Ian Rogers
2023-05-17 15:26 ` [PATCH v2 08/15] perf vendor events intel: Update jaketown metrics Ian Rogers
2023-05-17 15:26 ` [PATCH v2 09/15] perf vendor events intel: Update sandybridge metrics Ian Rogers
2023-05-17 15:26 ` [PATCH v2 12/15] perf vendor events intel: Update snowridgex events Ian Rogers
2023-05-17 15:26 ` [PATCH v2 14/15] perf jevents: Add support for metricgroup descriptions Ian Rogers
[not found] ` <20230517152626.563559-16-irogers@google.com>
2023-05-17 15:49 ` Liang, Kan [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=fdac0774-30d6-c81b-5eb9-54edaa6f6ff1@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=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=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=tmricht@linux.ibm.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).