From: Jiri Olsa <jolsa@redhat.com>
To: Ian Rogers <irogers@google.com>
Cc: 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>,
Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Jin Yao <yao.jin@linux.intel.com>,
John Garry <john.garry@huawei.com>, Paul Clarke <pc@us.ibm.com>,
kajoljain <kjain@linux.ibm.com>,
Stephane Eranian <eranian@google.com>,
Sandeep Dasgupta <sdasgup@google.com>
Subject: Re: [PATCH v7 1/5] perf metric: Restructure struct expr_parse_ctx.
Date: Fri, 15 Jan 2021 11:08:46 +0100 [thread overview]
Message-ID: <20210115100846.GC1478666@krava> (raw)
In-Reply-To: <20210112230434.2631593-2-irogers@google.com>
On Tue, Jan 12, 2021 at 03:04:30PM -0800, Ian Rogers wrote:
SNIP
> diff --git a/tools/perf/tests/pmu-events.c b/tools/perf/tests/pmu-events.c
> index 0ca6a5a53523..cf5afd126934 100644
> --- a/tools/perf/tests/pmu-events.c
> +++ b/tools/perf/tests/pmu-events.c
> @@ -478,9 +478,14 @@ static int test_parsing(void)
> struct pmu_event *pe;
> int i, j, k;
> int ret = 0;
> - struct expr_parse_ctx ctx;
> + struct expr_parse_ctx *ctx;
> double result;
>
> + ctx = expr__ctx_new();
> + if (!ctx) {
> + pr_debug("expr__ctx_new failed");
> + return TEST_FAIL;
> + }
> i = 0;
> for (;;) {
> map = &pmu_events_map[i++];
> @@ -496,8 +501,8 @@ static int test_parsing(void)
> break;
> if (!pe->metric_expr)
> continue;
> - expr__ctx_init(&ctx);
> - if (expr__find_other(pe->metric_expr, NULL, &ctx, 0)
> + expr__ctx_clear(ctx);
why move the clear from bottom in here?
SNIP
>
> -void expr__ctx_init(struct expr_parse_ctx *ctx)
> +struct expr_parse_ctx *expr__ctx_new(void)
> {
> - hashmap__init(&ctx->ids, key_hash, key_equal, NULL);
> + struct expr_parse_ctx *ctx;
> +
> + ctx = malloc(sizeof(struct expr_parse_ctx));
> + if (!ctx)
> + return NULL;
> +
> + ctx->ids = hashmap__new(key_hash, key_equal, NULL);
we should check for allocation failuer
jirka
> + ctx->parent = NULL;
> + return ctx;
> }
>
> void expr__ctx_clear(struct expr_parse_ctx *ctx)
> @@ -221,11 +229,24 @@ void expr__ctx_clear(struct expr_parse_ctx *ctx)
> struct hashmap_entry *cur;
> size_t bkt;
>
> - hashmap__for_each_entry((&ctx->ids), cur, bkt) {
> + hashmap__for_each_entry(ctx->ids, cur, bkt) {
> + free((char *)cur->key);
> + free(cur->value);
SNIP
next prev parent reply other threads:[~2021-01-15 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 23:04 [PATCH v7 0/5] Don't compute events that won't be used in a metric Ian Rogers
2021-01-12 23:04 ` [PATCH v7 1/5] perf metric: Restructure struct expr_parse_ctx Ian Rogers
2021-01-15 10:08 ` Jiri Olsa [this message]
2021-01-12 23:04 ` [PATCH v7 2/5] perf metric: Use NAN for missing event IDs Ian Rogers
2021-01-12 23:04 ` [PATCH v7 3/5] perf metric: Rename expr__find_other Ian Rogers
2021-01-12 23:04 ` [PATCH v7 4/5] perf metric: Add utilities to work on ids map Ian Rogers
2021-01-15 10:08 ` Jiri Olsa
2021-01-12 23:04 ` [PATCH v7 5/5] perf metric: Don't compute unused events Ian Rogers
2021-01-15 10:08 ` Jiri Olsa
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=20210115100846.GC1478666@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pc@us.ibm.com \
--cc=peterz@infradead.org \
--cc=sdasgup@google.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
all inboxes | Powered by JetHome®