[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190118161708.GE28346@krava>
Date: Fri, 18 Jan 2019 17:17:08 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: Andi Kleen <andi@...stfloor.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
David Ahern <dsahern@...il.com>, linux-kernel@...r.kernel.org,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [RFC] Don't print sample_type bits in non-group events not set
in the group's was Re: [PATCH] perf, script: Fix crash with printing mixed
trace point and other events
On Fri, Jan 18, 2019 at 08:11:42AM -0800, Andi Kleen wrote:
> > +static bool perf_evsel__should_skip(struct perf_evsel *evsel)
> > +{
> > + struct perf_event_attr *attr = &evsel->attr;
> > + struct perf_evsel *leader = evsel->leader;
> > +
> > + return (leader != evsel) && !attr->freq && !attr->sample_freq;
> > +}
> > +
> > static int process_sample_event(struct perf_tool *tool,
> > union perf_event *event,
> > struct perf_sample *sample,
> > @@ -1934,6 +1942,9 @@ static int process_sample_event(struct perf_tool *tool,
> > struct perf_script *scr = container_of(tool, struct perf_script, tool);
> > struct addr_location al;
> >
> > + if (perf_evsel__should_skip(evsel))
> > + return 0;
>
> That just skips, but surely it has to be displayed somewhere?
>
yea as I wrote in that email:
....... we should probably skip (something like below) that and
add script field that would output the sample_read values for the
leader
jirka
Powered by blists - more mailing lists