From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752438AbcDZQd2 (ORCPT ); Tue, 26 Apr 2016 12:33:28 -0400 Received: from mail.kernel.org ([198.145.29.136]:57320 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751757AbcDZQd1 (ORCPT ); Tue, 26 Apr 2016 12:33:27 -0400 Date: Tue, 26 Apr 2016 13:33:21 -0300 From: Arnaldo Carvalho de Melo To: Brendan Gregg Cc: Alexei Starovoitov , David Ahern , Peter Zijlstra , Frederic Weisbecker , Ingo Molnar , Adrian Hunter , Alexander Shishkin , Alexei Starovoitov , He Kuang , Jiri Olsa , Masami Hiramatsu , Milian Wolff , Namhyung Kim , Stephane Eranian , Thomas Gleixner , Vince Weaver , Wang Nan , Zefan Li , Linux Kernel Mailing List Subject: Re: [PATCH/RFC v3] perf core: Allow setting up max frame stack depth via sysctl Message-ID: <20160426163321.GI11033@kernel.org> References: <20160425192229.GC25218@kernel.org> <20160425200646.GA23875@ast-mbp.thefacebook.com> <20160425201750.GD25218@kernel.org> <20160425215947.GA25915@ast-mbp.thefacebook.com> <20160425234138.GA16708@kernel.org> <20160426000724.GA28705@ast-mbp.thefacebook.com> <20160426002928.GB16708@kernel.org> <20160426004358.GA29875@ast-mbp.thefacebook.com> <20160426004747.GC16708@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Mon, Apr 25, 2016 at 05:49:38PM -0700, Brendan Gregg escreveu: > On Mon, Apr 25, 2016 at 5:47 PM, Arnaldo Carvalho de Melo > wrote: > > Em Mon, Apr 25, 2016 at 05:44:00PM -0700, Alexei Starovoitov escreveu: > >> On Mon, Apr 25, 2016 at 09:29:28PM -0300, Arnaldo Carvalho de Melo wrote: > >> > Because we only allocate the callchain percpu data structures when there > >> > is a user, which allows for changing the max easily, its just a matter > >> > of having no callchain users at that point. > >> > > >> > Reported-and-Tested-by: Brendan Gregg > >> > Acked-by: Alexei Starovoitov > >> > >> yep :) > >> hopefully Brendan can give it another spin. > > > > Agreed, and I'm calling it a day anyway, Brendan, please consider > > retesting, thanks, > Will do, thanks! > Brendan So, for completeness, further testing it to see how far it goes on a 8GB machine I got: [root@emilia ~]# echo 131100 > /proc/sys/kernel/perf_event_max_stack [root@emilia ~]# perf record -g ls Error: The sys_perf_event_open() syscall returned with 12 (Cannot allocate memory) for event (cycles). /bin/dmesg may provide additional information. No CONFIG_PERF_EVENTS=y kernel support configured? [root@emilia ~]# [root@emilia ~]# echo 131000 > /proc/sys/kernel/perf_event_max_stack [root@emilia ~]# perf record -g usleep [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.013 MB perf.data (9 samples) ] [root@emilia ~]# ls -la perf.data -rw-------. 1 root root 15736 Apr 26 13:33 perf.data [root@emilia ~]# - Arnaldo