From: Jiri Olsa <jolsa@redhat.com>
To: Kajol Jain <kjain@linux.ibm.com>
Cc: acme@kernel.org, peterz@infradead.org, mingo@redhat.com,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
pc@us.ibm.com, namhyung@kernel.org, ak@linux.intel.com,
yao.jin@linux.intel.com, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, irogers@google.com,
maddy@linux.ibm.com, ravi.bangoria@linux.ibm.com,
john.garry@huawei.com
Subject: Re: [PATCH v6 3/5] perf jevents: Add support for parsing perchip/percore events
Date: Mon, 31 Aug 2020 10:44:04 +0200 [thread overview]
Message-ID: <20200831084404.GD287892@krava> (raw)
In-Reply-To: <20200827130958.189146-4-kjain@linux.ibm.com>
On Thu, Aug 27, 2020 at 06:39:56PM +0530, Kajol Jain wrote:
> Initially, every time we want to add new terms like chip, core thread etc,
> we need to create corrsponding fields in pmu_events and event struct.
> This patch adds an enum called 'aggr_mode_class' which store all these
> aggregation like perchip/percore. It also adds new field 'aggr_mode'
> to capture these terms.
> Now, if user wants to add any new term, they just need to add it in
> the enum defined.
>
> Signed-off-by: Kajol Jain <kjain@linux.ibm.com>
> ---
> tools/perf/pmu-events/jevents.c | 16 ++++++++++++++++
> tools/perf/pmu-events/pmu-events.h | 6 ++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
> index b205cd904a4f..f4ad2d403533 100644
> --- a/tools/perf/pmu-events/jevents.c
> +++ b/tools/perf/pmu-events/jevents.c
> @@ -48,6 +48,7 @@
> #include <linux/list.h>
> #include "jsmn.h"
> #include "json.h"
> +#include "pmu-events.h"
>
> int verbose;
> char *prog;
> @@ -60,6 +61,7 @@ struct json_event {
> char *pmu;
> char *unit;
> char *perpkg;
> + char *aggr_mode;
> char *metric_expr;
> char *metric_name;
> char *metric_group;
> @@ -74,6 +76,14 @@ struct json_event {
> (void)(&_min1 == &_min2); \
> _min1 < _min2 ? _min1 : _min2; })
> #endif
please add new line in here
> +enum aggr_mode_class convert(const char *aggr_mode)
> +{
> + if (!strcmp(aggr_mode, "PerCore"))
> + return PerCore;
> + else if (!strcmp(aggr_mode, "PerChip"))
> + return PerChip;
> + return -1;
should we display some warning in here?
thanks,
jirka
next prev parent reply other threads:[~2020-08-31 8:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 13:09 [PATCH v6 0/5] powerpc/perf: Add json file support for hv_24x7 core level events Kajol Jain
2020-08-27 13:09 ` [PATCH v6 1/5] perf/jevents: Remove jevents.h file Kajol Jain
2020-08-31 8:43 ` Jiri Olsa
2020-08-31 9:01 ` John Garry
2020-08-31 9:01 ` John Garry
2020-09-01 5:56 ` kajoljain
2020-09-02 7:25 ` John Garry
2020-09-02 7:25 ` John Garry
2020-09-01 5:50 ` kajoljain
2020-08-27 13:09 ` [PATCH v6 2/5] perf/jevents: Add new structure to pass json fields Kajol Jain
2020-08-31 8:43 ` Jiri Olsa
2020-09-01 6:02 ` kajoljain
2020-09-01 20:37 ` Jiri Olsa
2020-08-27 13:09 ` [PATCH v6 3/5] perf jevents: Add support for parsing perchip/percore events Kajol Jain
2020-08-31 8:44 ` Jiri Olsa [this message]
2020-09-01 6:03 ` kajoljain
2020-08-27 13:09 ` [PATCH v6 4/5] perf/tools: Pass pmu_event structure as a parameter for arch_get_runtimeparam Kajol Jain
2020-08-27 13:09 ` [PATCH v6 5/5] 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=20200831084404.GD287892@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=kjain@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.