[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161206112634.GN3124@twins.programming.kicks-ass.net>
Date: Tue, 6 Dec 2016 12:26:34 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: kan.liang@...el.com
Cc: mingo@...hat.com, acme@...nel.org, linux-kernel@...r.kernel.org,
alexander.shishkin@...ux.intel.com, tglx@...utronix.de,
namhyung@...nel.org, jolsa@...nel.org, adrian.hunter@...el.com,
wangnan0@...wei.com, mark.rutland@....com, andi@...stfloor.org
Subject: Re: [PATCH V2 01/13] perf/core: Introduce PERF_RECORD_OVERHEAD
On Fri, Dec 02, 2016 at 04:19:09PM -0500, kan.liang@...el.com wrote:
> @@ -1221,6 +1225,11 @@ static inline bool has_addr_filter(struct perf_event *event)
> return event->pmu->nr_addr_filters;
> }
>
> +static inline bool needs_log_overhead(struct perf_event *event)
> +{
> + return !!event->attr.overhead;
> +}
There seems to be exactly one user of that, seems a tad pointless to
provide this function.
Powered by blists - more mailing lists