[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM9d7cgzkhCpLHGyFRi51G=qw1ijX28W2zu6G04dFGhP6n8TaA@mail.gmail.com>
Date: Thu, 2 Jun 2022 13:09:29 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Ian Rogers <irogers@...gle.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...nel.org>, Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-perf-users <linux-perf-users@...r.kernel.org>,
Will Deacon <will@...nel.org>,
Waiman Long <longman@...hat.com>,
Boqun Feng <boqun.feng@...il.com>,
Davidlohr Bueso <dave@...olabs.net>
Subject: Re: [PATCH 4/5] perf record: Allow to specify max stack depth of fp callchain
On Wed, Jun 1, 2022 at 11:30 PM Ian Rogers <irogers@...gle.com> wrote:
>
> On Tue, May 31, 2022 at 11:58 PM Namhyung Kim <namhyung@...nel.org> wrote:
> >
> > Currently it has no interface to specify the max stack depth for perf
> > record. Extend the command line parameter to accept a number after
> > 'fp' to specify the depth like '--call-graph fp,32'.
>
> It is valid to have call-graph=fp as a modifier on an event. To
> support a depth with that we couldn't use ',' as it is already the
> separator between modifiers. For consistency maybe a different
> separator should be used here?
But it's already there for dwarf stack dump size like
'--call-graph dwarf,4096'. Maybe we can add a new config term
for the event parser.
Thanks,
Namhyung
Powered by blists - more mailing lists