From: John Garry <john.garry@huawei.com>
To: Kajol Jain <kjain@linux.ibm.com>, <acme@kernel.org>
Cc: <jolsa@redhat.com>, <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>
Subject: Re: [RFC] perf/jevents: Add new structure to pass json fields.
Date: Tue, 25 Aug 2020 09:14:11 +0100 [thread overview]
Message-ID: <bc078472-e859-b7dc-c451-d737dd573edf@huawei.com> (raw)
In-Reply-To: <20200825074041.378520-1-kjain@linux.ibm.com>
On 25/08/2020 08:40, Kajol Jain wrote:
> This patch adds new structure called 'json_event' inside jevents.h
> file to improve the callback prototype inside jevent files.
> Initially, whenever user want to add new field, they need to update
> in all function callback which make it more and more complex with
> increased number of parmeters.
> With this change, we just need to add it in new structure 'json_event'.
>
>
> Signed-off-by: Kajol Jain <kjain@linux.ibm.com>
> ---
> tools/perf/pmu-events/jevents.c | 188 +++++++++++++-------------------
> tools/perf/pmu-events/jevents.h | 28 +++--
> 2 files changed, 94 insertions(+), 122 deletions(-)
>
> This is the initial prototype to include structure for passing
> json fileds. Please, Let me know if this is the right direction
> to go forward.
> This patch doen't include all the changes, like percore/perchip
> field addition. If this looks fine I can send new patch set with
> those changes.
>
> diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
> index fa86c5f997cc..606805af69fe 100644
> --- a/tools/perf/pmu-events/jevents.c
> +++ b/tools/perf/pmu-events/jevents.c
> @@ -318,12 +318,7 @@ static void print_events_table_prefix(FILE *fp, const char *tblname)
> close_table = 1;
> }
>
> -static int print_events_table_entry(void *data, char *name, char *event,
> - char *desc, char *long_desc,
> - char *pmu, char *unit, char *perpkg,
> - char *metric_expr,
> - char *metric_name, char *metric_group,
> - char *deprecated, char *metric_constraint)
Right, too many paramaetrs of the same type, so looks reasonable to pass
a struct
[...]
> if (arch_std) {
> /*
> * An arch standard event is referenced, so try to
> * fixup any unassigned values.
> */
> - err = try_fixup(fn, arch_std, &event, &desc, &name,
> - &long_desc, &pmu, &filter, &perpkg,
> - &unit, &metric_expr, &metric_name,
> - &metric_group, eventcode,
> - &deprecated, &metric_constraint);
> + err = try_fixup(fn, arch_std, eventcode, je);
> if (err)
> goto free_strings;
> }
> - err = func(data, name, real_event(name, event), desc, long_desc,
> - pmu, unit, perpkg, metric_expr, metric_name,
> - metric_group, deprecated, metric_constraint);
> + je->event = real_event(je->name, je->event);
> + err = func(data, je);
> free_strings:
> - free(event);
> - free(desc);
> - free(name);
> - free(long_desc);
> free(extra_desc);
> - free(pmu);
> free(filter);
> - free(perpkg);
> - free(deprecated);
> - free(unit);
> - free(metric_expr);
> - free(metric_name);
> - free(metric_group);
> - free(metric_constraint);
> free(arch_std);
> + free(je);
>
> if (err)
> break;
> diff --git a/tools/perf/pmu-events/jevents.h b/tools/perf/pmu-events/jevents.h
> index 2afc8304529e..e696edf70e9a 100644
> --- a/tools/perf/pmu-events/jevents.h
> +++ b/tools/perf/pmu-events/jevents.h
Somewhat unrelated - this file only seems to be included in jevents.c,
so I don't see why it exists...
> @@ -2,14 +2,28 @@
> #ifndef JEVENTS_H
> #define JEVENTS_H 1
>
> +#include "pmu-events.h"
> +
> +struct json_event {
> + char *name;
> + char *event;
> + char *desc;
> + char *topic;
> + char *long_desc;
> + char *pmu;
> + char *unit;
> + char *perpkg;
> + char *metric_expr;
> + char *metric_name;
> + char *metric_group;
> + char *deprecated;
> + char *metric_constraint;
This looks very much like struct event_struct, so could look to consolidate:
struct event_struct {
struct list_head list;
char *name;
char *event;
char *desc;
char *long_desc;
char *pmu;
char *unit;
char *perpkg;
char *metric_expr;
char *metric_name;
char *metric_group;
char *deprecated;
char *metric_constraint;
};
> +};
> +
> int json_events(const char *fn,
> - int (*func)(void *data, char *name, char *event, char *desc,
> - char *long_desc,
> - char *pmu,
> - char *unit, char *perpkg, char *metric_expr,
> - char *metric_name, char *metric_group,
> - char *deprecated, char *metric_constraint),
> - void *data);
> + int (*func)(void *data, struct json_event *je),
> + void *data);
> +
> char *get_cpu_str(void);
>
> #ifndef min
>
next prev parent reply other threads:[~2020-08-25 8:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 7:40 [RFC] perf/jevents: Add new structure to pass json fields Kajol Jain
2020-08-25 8:14 ` John Garry [this message]
2020-08-26 11:00 ` Jiri Olsa
2020-08-26 11:24 ` kajoljain
2020-08-26 11:33 ` John Garry
2020-08-27 12:57 ` kajoljain
2020-08-25 15:47 ` Andi Kleen
2020-08-26 11:25 ` kajoljain
2020-08-26 10:56 ` Jiri Olsa
2020-08-26 11:32 ` kajoljain
2020-08-26 11:59 ` Jiri Olsa
2020-08-27 12:58 ` kajoljain
2020-08-26 10:57 ` Jiri Olsa
2020-08-26 11:28 ` kajoljain
2020-08-26 10:57 ` Jiri Olsa
2020-08-26 11:33 ` kajoljain
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=bc078472-e859-b7dc-c451-d737dd573edf@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.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=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