[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20201202065526.GE1363814@tassilo.jf.intel.com>
Date: Tue, 1 Dec 2020 22:55:26 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: Ian Rogers <irogers@...gle.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Jin Yao <yao.jin@...ux.intel.com>,
John Garry <john.garry@...wei.com>,
Paul Clarke <pc@...ibm.com>, kajoljain <kjain@...ux.ibm.com>,
Stephane Eranian <eranian@...gle.com>,
Sandeep Dasgupta <sdasgup@...gle.com>
Subject: Re: [PATCH v4 5/5] perf metric: Don't compute unused events.
> Can't this be all in a macro? It's still a lot of duplication.
>
> I'm still not a fan, but I think with a macro it wouldn't be too bad.
>
> Ugh, not a fan of macros. They expand to a single line of code and make
> debugging hard. I'll do a v5 with a macro :-/
I suppose you could inlines with callbacks too, with one liner functions for
the operands.
-Andi
Powered by blists - more mailing lists