[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200210180031.GY302770@tassilo.jf.intel.com>
Date: Mon, 10 Feb 2020 10:00:31 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Joe Perches <joe@...ches.com>, Kajol Jain <kjain@...ux.ibm.com>,
acme@...nel.org, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org, Jiri Olsa <jolsa@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Kan Liang <kan.liang@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Jin Yao <yao.jin@...ux.intel.com>,
Madhavan Srinivasan <maddy@...ux.vnet.ibm.com>,
Anju T Sudhakar <anju@...ux.vnet.ibm.com>,
Ravi Bangoria <ravi.bangoria@...ux.ibm.com>
Subject: Re: [PATCH v3] tools/perf/metricgroup: Fix printing event names of
metric group with multiple events incase of overlapping events
> > stack declarations of variable length arrays are not
> > a good thing.
> >
> > https://lwn.net/Articles/749089/
> >
> > and
> >
> > bool evlist_used[perf_evlist->core.nr_entries] = {};
>
> hum, I think we already have few of them in perf ;-)
For user space they don't really matter as long as the size is
not totally out of bound, it has a fairly large stack compared
to the kernel, and also is less security sensitive.
-Andi
Powered by blists - more mailing lists