From: jolsa@redhat.com (Jiri Olsa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] perf tools: Store ids for events with their own cpus perf_event__synthesize_event_update_cpus
Date: Tue, 9 Oct 2018 12:00:49 +0200 [thread overview]
Message-ID: <20181009100049.GF6499@krava> (raw)
In-Reply-To: <d071bb27-5533-da2f-9f8f-808183e04794@huawei.com>
On Thu, Oct 04, 2018 at 10:20:39AM +0100, John Garry wrote:
SNIP
> > We synthesize an update event that needs to touch the evsel
> > id array, which is not defined at that time. Fixing this by
> > forcing the id allocation for events with theeir own cpus.
> >
> > Reported-by: John Garry <john.garry@huawei.com>
> > Link: http://lkml.kernel.org/n/tip-8x4n7o34yheigoxm1jibflm6 at git.kernel.org
>
> Tested-by: John Garry <john.garry@huawei.com>
>
> In terms of adding to stable, LT v4.14 is not affected, but 4.18.x is.
>
> Thanks,
> John
Arnaldo, could you please pick up this one
thanks,
jirka
>
> > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > ---
> > tools/perf/builtin-report.c | 1 +
> > tools/perf/util/evsel.c | 3 +++
> > 2 files changed, 4 insertions(+)
> >
> > diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
> > index c0703979c51d..257c9c18cb7e 100644
> > --- a/tools/perf/builtin-report.c
> > +++ b/tools/perf/builtin-report.c
> > @@ -980,6 +980,7 @@ int cmd_report(int argc, const char **argv)
> > .id_index = perf_event__process_id_index,
> > .auxtrace_info = perf_event__process_auxtrace_info,
> > .auxtrace = perf_event__process_auxtrace,
> > + .event_update = perf_event__process_event_update,
> > .feature = process_feature_event,
> > .ordered_events = true,
> > .ordering_requires_timestamps = true,
> > diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
> > index ac6cfb8b085e..7a0d5fbaf3c1 100644
> > --- a/tools/perf/util/evsel.c
> > +++ b/tools/perf/util/evsel.c
> > @@ -1088,6 +1088,9 @@ void perf_evsel__config(struct perf_evsel *evsel, struct record_opts *opts,
> > attr->exclude_user = 1;
> > }
> >
> > + if (evsel->own_cpus)
> > + evsel->attr.read_format |= PERF_FORMAT_ID;
> > +
> > /*
> > * Apply event specific term settings,
> > * it overloads any global configuration.
> >
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Olsa <jolsa@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: Andi Kleen <ak@linux.intel.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Linuxarm <linuxarm@huawei.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] perf tools: Store ids for events with their own cpus perf_event__synthesize_event_update_cpus
Date: Tue, 9 Oct 2018 12:00:49 +0200 [thread overview]
Message-ID: <20181009100049.GF6499@krava> (raw)
In-Reply-To: <d071bb27-5533-da2f-9f8f-808183e04794@huawei.com>
On Thu, Oct 04, 2018 at 10:20:39AM +0100, John Garry wrote:
SNIP
> > We synthesize an update event that needs to touch the evsel
> > id array, which is not defined at that time. Fixing this by
> > forcing the id allocation for events with theeir own cpus.
> >
> > Reported-by: John Garry <john.garry@huawei.com>
> > Link: http://lkml.kernel.org/n/tip-8x4n7o34yheigoxm1jibflm6@git.kernel.org
>
> Tested-by: John Garry <john.garry@huawei.com>
>
> In terms of adding to stable, LT v4.14 is not affected, but 4.18.x is.
>
> Thanks,
> John
Arnaldo, could you please pick up this one
thanks,
jirka
>
> > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > ---
> > tools/perf/builtin-report.c | 1 +
> > tools/perf/util/evsel.c | 3 +++
> > 2 files changed, 4 insertions(+)
> >
> > diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
> > index c0703979c51d..257c9c18cb7e 100644
> > --- a/tools/perf/builtin-report.c
> > +++ b/tools/perf/builtin-report.c
> > @@ -980,6 +980,7 @@ int cmd_report(int argc, const char **argv)
> > .id_index = perf_event__process_id_index,
> > .auxtrace_info = perf_event__process_auxtrace_info,
> > .auxtrace = perf_event__process_auxtrace,
> > + .event_update = perf_event__process_event_update,
> > .feature = process_feature_event,
> > .ordered_events = true,
> > .ordering_requires_timestamps = true,
> > diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
> > index ac6cfb8b085e..7a0d5fbaf3c1 100644
> > --- a/tools/perf/util/evsel.c
> > +++ b/tools/perf/util/evsel.c
> > @@ -1088,6 +1088,9 @@ void perf_evsel__config(struct perf_evsel *evsel, struct record_opts *opts,
> > attr->exclude_user = 1;
> > }
> >
> > + if (evsel->own_cpus)
> > + evsel->attr.read_format |= PERF_FORMAT_ID;
> > +
> > /*
> > * Apply event specific term settings,
> > * it overloads any global configuration.
> >
>
>
next prev parent reply other threads:[~2018-10-09 10:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 15:53 perf segmentation fault from NULL dereference John Garry
2018-09-25 15:53 ` John Garry
2018-09-27 3:00 ` Andi Kleen
2018-09-27 3:00 ` Andi Kleen
2018-10-02 10:20 ` John Garry
2018-10-02 10:20 ` John Garry
2018-09-27 16:02 ` Jiri Olsa
2018-09-27 16:02 ` Jiri Olsa
2018-10-02 10:41 ` John Garry
2018-10-02 10:41 ` John Garry
2018-10-02 11:16 ` Jiri Olsa
2018-10-02 11:16 ` Jiri Olsa
2018-10-03 11:36 ` [PATCH] perf tools: Allocate id array in perf_event__synthesize_event_update_cpus Jiri Olsa
2018-10-03 11:36 ` Jiri Olsa
2018-10-03 14:08 ` John Garry
2018-10-03 14:08 ` John Garry
2018-10-03 14:16 ` Jiri Olsa
2018-10-03 14:16 ` Jiri Olsa
2018-10-03 21:20 ` [PATCH] perf tools: Store ids for events with their own cpus perf_event__synthesize_event_update_cpus Jiri Olsa
2018-10-03 21:20 ` Jiri Olsa
2018-10-04 9:20 ` John Garry
2018-10-04 9:20 ` John Garry
2018-10-09 10:00 ` Jiri Olsa [this message]
2018-10-09 10:00 ` Jiri Olsa
2018-10-12 13:25 ` John Garry
2018-10-12 13:25 ` John Garry
2018-10-15 19:15 ` Arnaldo Carvalho de Melo
2018-10-15 19:15 ` Arnaldo Carvalho de Melo
2018-10-16 9:10 ` John Garry
2018-10-16 9:10 ` John Garry
2018-10-16 10:47 ` Jiri Olsa
2018-10-16 10:47 ` Jiri Olsa
2018-10-18 6:18 ` [tip:perf/urgent] perf evsel: " tip-bot for 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=20181009100049.GF6499@krava \
--to=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.