From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH v3] tools/perf/metricgroup: Fix printing event names of metric group with multiple events incase of overlapping events Date: Mon, 10 Feb 2020 10:00:31 -0800 Message-ID: <20200210180031.GY302770@tassilo.jf.intel.com> References: <20200131052522.7267-1-kjain@linux.ibm.com> <20200206184510.GA1669706@krava> <51a4b570eb47e80801a460c89acf20d13a269600.camel@perches.com> <20200210121135.GI1907700@krava> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20200210121135.GI1907700@krava> Sender: linux-kernel-owner@vger.kernel.org To: Jiri Olsa Cc: Joe Perches , Kajol Jain , acme@kernel.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, Jiri Olsa , Alexander Shishkin , Kan Liang , Peter Zijlstra , Jin Yao , Madhavan Srinivasan , Anju T Sudhakar , Ravi Bangoria List-Id: linux-perf-users.vger.kernel.org > > 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