[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190118161140.z45vl3milw2vk4hy@two.firstfloor.org>
Date: Fri, 18 Jan 2019 08:11:42 -0800
From: Andi Kleen <andi@...stfloor.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...nel.org>, Andi Kleen <andi@...stfloor.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
> +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?
-Andi
Powered by blists - more mailing lists