From: Jiri Olsa <jolsa@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
namhyung@kernel.org, kjain@linux.ibm.com, irogers@google.com,
yao.jin@linux.intel.com, yeyunfeng@huawei.com,
linux-kernel@vger.kernel.org, linuxarm@huawei.com,
=linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] perf jevents: Fix event code for events referencing std arch events
Date: Mon, 12 Oct 2020 12:54:30 +0200 [thread overview]
Message-ID: <20201012105430.GH1099489@krava> (raw)
In-Reply-To: <1602170368-11892-1-git-send-email-john.garry@huawei.com>
On Thu, Oct 08, 2020 at 11:19:28PM +0800, John Garry wrote:
> The event code for events referencing std arch events is incorrectly
> evaluated in json_events().
>
> The issue is that je.event is evaluated properly from try_fixup(), but
> later NULLified from the real_event() call, as "event" may be NULL.
>
> Fix by setting "event" same je.event in try_fixup().
>
> Also remove support for overwriting event code for events using std arch
> events, as it is not used.
>
> Signed-off-by: John Garry <john.garry@huawei.com>
>
> diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
> index 99df41a9543d..e47644cab3fa 100644
> --- a/tools/perf/pmu-events/jevents.c
> +++ b/tools/perf/pmu-events/jevents.c
> @@ -505,20 +505,15 @@ static char *real_event(const char *name, char *event)
> }
>
> static int
> -try_fixup(const char *fn, char *arch_std, unsigned long long eventcode,
> - struct json_event *je)
> +try_fixup(const char *fn, char *arch_std, struct json_event *je, char **event)
> {
> /* try to find matching event from arch standard values */
> struct event_struct *es;
>
> list_for_each_entry(es, &arch_std_events, list) {
> if (!strcmp(arch_std, es->name)) {
> - if (!eventcode && es->event) {
> - /* allow EventCode to be overridden */
> - free(je->event);
> - je->event = NULL;
> - }
> FOR_ALL_EVENT_STRUCT_FIELDS(TRY_FIXUP_FIELD);
> + *event = je->event;
I'm bit rusty on this code, but isn't je->event NULL at this point?
jirka
> return 0;
> }
> }
> @@ -678,7 +673,7 @@ static int json_events(const char *fn,
> * An arch standard event is referenced, so try to
> * fixup any unassigned values.
> */
> - err = try_fixup(fn, arch_std, eventcode, &je);
> + err = try_fixup(fn, arch_std, &je, &event);
> if (err)
> goto free_strings;
> }
> --
> 2.26.2
>
next prev parent reply other threads:[~2020-10-12 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 15:19 John Garry
2020-10-09 11:26 ` kajoljain
2020-10-09 11:38 ` John Garry
2020-10-12 10:54 ` Jiri Olsa [this message]
2020-10-12 11:15 ` John Garry
2020-10-12 11:24 ` Jiri Olsa
2020-10-13 8:41 ` John Garry
2020-10-14 16:49 ` Arnaldo Carvalho de Melo
2020-10-14 17:46 ` John Garry
2020-10-15 12:25 ` Arnaldo Carvalho de Melo
2020-10-15 15:42 ` John Garry
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=20201012105430.GH1099489@krava \
--to=jolsa@redhat.com \
--cc==linux-arm-kernel@lists.infradead.org \
--cc=acme@kernel.org \
--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=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.com \
--cc=yeyunfeng@huawei.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
Powered by JetHome