From: kajoljain <kjain@linux.ibm.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Paul Clarke <pc@us.ibm.com>, Namhyung Kim <namhyung@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Jin Yao <yao.jin@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
maddy@linux.ibm.com, Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
Anju T Sudhakar <anju@linux.vnet.ibm.com>,
"Liang, Kan" <kan.liang@linux.intel.com>
Subject: Re: [RFC 1/3] perf jevents: Add support for parsing perchip/percore events
Date: Tue, 7 Jul 2020 17:01:54 +0530 [thread overview]
Message-ID: <d9252cb6-7cb3-9783-a0f2-d879dcc894a7@linux.ibm.com> (raw)
In-Reply-To: <20200706125757.GA3424581@krava>
On 7/6/20 6:27 PM, Jiri Olsa wrote:
> On Fri, Jul 03, 2020 at 11:50:28AM +0530, kajoljain wrote:
>
> SNIP
>
>> ]
>> diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
>> index fa86c5f997cc..dd2b14cc147c 100644
>> --- a/tools/perf/pmu-events/jevents.c
>> +++ b/tools/perf/pmu-events/jevents.c
>> @@ -53,6 +53,23 @@
>> int verbose;
>> char *prog;
>>
>> +enum event_class {
>> + PerChip = 0,
>> + PerPkg = 1,
>> + PerCore = 2
>> +};
>
> could you please split this into patch that changes perpkg
> into the class type string and another that adds new PerChip/PerCore?
>
Hi Jiri,
Thanks for reviewing the prototype changes. Sure I will split it and
and send next version out.
>> +
>> +enum event_class convert(const char* event_class_type) {
>> +
>> + if (!strcmp(event_class_type, "PerCore"))
>> + return PerCore;
>> + else if (!strcmp(event_class_type, "PerChip"))
>> + return PerChip;
>> + else if (!strcmp(event_class_type, "PerPkg"))
>> + return PerPkg;
>> + return -1;
>> +}
>> +
>> int eprintf(int level, int var, const char *fmt, ...)
>> {
>>
>> @@ -320,7 +337,7 @@ static void print_events_table_prefix(FILE *fp, const char *tblname)
>>
>> static int print_events_table_entry(void *data, char *name, char *event,
>> char *desc, char *long_desc,
>> - char *pmu, char *unit, char *perpkg,
>> + char *pmu, char *unit, char *event_class_type,
>
> maybe 'aggregation' or 'aggr_mode' would be better name than event_class_type?
>
Sure, will update.
Thanks,
Kajol Jain
> thanks,
> jirka
>
next prev parent reply other threads:[~2020-07-07 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 11:47 [RFC 0/3] powerpc/perf: Add json file support for hv_24x7 core level events Kajol Jain
2020-06-25 11:47 ` [RFC 1/3] perf jevents: Add support for parsing perchip/percore events Kajol Jain
2020-06-25 14:08 ` Ian Rogers
2020-07-03 6:20 ` kajoljain
2020-07-06 1:43 ` Ian Rogers
2020-07-06 12:57 ` Jiri Olsa
2020-07-07 11:31 ` kajoljain [this message]
2020-06-25 11:47 ` [RFC 2/3] perf/tools: Pass pmu_event structure as a parameter for arch_get_runtimeparam Kajol Jain
2020-06-25 11:47 ` [RFC 3/3] perf/tools/pmu_events/powerpc: Add hv_24x7 core level metric events Kajol Jain
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=d9252cb6-7cb3-9783-a0f2-d879dcc894a7@linux.ibm.com \
--to=kjain@linux.ibm.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anju@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pc@us.ibm.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=yao.jin@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).