Em Wed, Sep 30, 2015 at 11:43:10AM +0300, Adrian Hunter escreveu:
> On 29/09/15 18:51, Arnaldo Carvalho de Melo wrote:
> > I'll add the patch below with your s-o-b, ack?
>
> Yes thank you.
Done, pushed out.
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
On 29/09/15 18:51, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 29, 2015 at 11:52:37AM +0300, Adrian Hunter escreveu:
>> On 28/09/15 23:03, Arnaldo Carvalho de Melo wrote:
>>> Em Fri, Sep 25, 2015 at 04:15:46PM +0300, Adrian Hunter escreveu:
perf report has an option (--max-stack) to set the
Em Tue, Sep 29, 2015 at 11:52:37AM +0300, Adrian Hunter escreveu:
> On 28/09/15 23:03, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Sep 25, 2015 at 04:15:46PM +0300, Adrian Hunter escreveu:
> >> perf report has an option (--max-stack) to set the maximum stack depth
> >> when processing callchains.
On 28/09/15 23:03, Arnaldo Carvalho de Melo wrote:
> Em Fri, Sep 25, 2015 at 04:15:46PM +0300, Adrian Hunter escreveu:
>> perf report has an option (--max-stack) to set the maximum stack depth
>> when processing callchains. The option defaults to the hard-coded
>> maximum definition PERF_MAX_STACK
Em Fri, Sep 25, 2015 at 04:15:46PM +0300, Adrian Hunter escreveu:
> perf report has an option (--max-stack) to set the maximum stack depth
> when processing callchains. The option defaults to the hard-coded
> maximum definition PERF_MAX_STACK_DEPTH which is 127. The intention of
> the option is t
perf report has an option (--max-stack) to set the maximum stack depth
when processing callchains. The option defaults to the hard-coded
maximum definition PERF_MAX_STACK_DEPTH which is 127. The intention of
the option is to allow the user to reduce the processing time by
reducing the amount of t
6 matches
Mail list logo