On Fri, Oct 24, 2014 at 10:56 AM, Arnaldo Carvalho de Melo
wrote:
> Em Fri, Oct 24, 2014 at 09:44:17AM +0900, Namhyung Kim escreveu:
>> On Thu, 23 Oct 2014 20:35:42 -0300, Arnaldo Carvalho de Melo wrote:
>> > I'll push later and will drop you a note, so that you can, please, check
>> > if the end
Em Fri, Oct 24, 2014 at 09:44:17AM +0900, Namhyung Kim escreveu:
> On Thu, 23 Oct 2014 20:35:42 -0300, Arnaldo Carvalho de Melo wrote:
> > I'll push later and will drop you a note, so that you can, please, check
> > if the end result is sane.
>
> Thank you!
It should be on my perf/core branch by
On Thu, 23 Oct 2014 20:35:42 -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Oct 22, 2014 at 10:34:27AM +0900, Namhyung Kim escreveu:
>> Hi Arnaldo,
>>
>> On Wed, 15 Oct 2014 17:06:30 -0300, Arnaldo Carvalho de Melo wrote:
>> > Next time please run: (I'm fixing this up this time)
>> >
>> >
Em Wed, Oct 22, 2014 at 10:34:27AM +0900, Namhyung Kim escreveu:
> Hi Arnaldo,
>
> On Wed, 15 Oct 2014 17:06:30 -0300, Arnaldo Carvalho de Melo wrote:
> > Next time please run: (I'm fixing this up this time)
> >
> > [acme@zoo linux]$ time make -C tools/perf build-test
> ...
> > In file included
Em Wed, Oct 22, 2014 at 10:34:27AM +0900, Namhyung Kim escreveu:
Hi Arnaldo,
On Wed, 15 Oct 2014 17:06:30 -0300, Arnaldo Carvalho de Melo wrote:
Next time please run: (I'm fixing this up this time)
[acme@zoo linux]$ time make -C tools/perf build-test
...
In file included from
On Thu, 23 Oct 2014 20:35:42 -0300, Arnaldo Carvalho de Melo wrote:
Em Wed, Oct 22, 2014 at 10:34:27AM +0900, Namhyung Kim escreveu:
Hi Arnaldo,
On Wed, 15 Oct 2014 17:06:30 -0300, Arnaldo Carvalho de Melo wrote:
Next time please run: (I'm fixing this up this time)
[acme@zoo linux]$
Em Fri, Oct 24, 2014 at 09:44:17AM +0900, Namhyung Kim escreveu:
On Thu, 23 Oct 2014 20:35:42 -0300, Arnaldo Carvalho de Melo wrote:
I'll push later and will drop you a note, so that you can, please, check
if the end result is sane.
Thank you!
It should be on my perf/core branch by now.
On Fri, Oct 24, 2014 at 10:56 AM, Arnaldo Carvalho de Melo
a...@kernel.org wrote:
Em Fri, Oct 24, 2014 at 09:44:17AM +0900, Namhyung Kim escreveu:
On Thu, 23 Oct 2014 20:35:42 -0300, Arnaldo Carvalho de Melo wrote:
I'll push later and will drop you a note, so that you can, please, check
if
Em Wed, Oct 22, 2014 at 10:34:27AM +0900, Namhyung Kim escreveu:
> Hi Arnaldo,
>
> On Wed, 15 Oct 2014 17:06:30 -0300, Arnaldo Carvalho de Melo wrote:
> > Next time please run: (I'm fixing this up this time)
> >
> > [acme@zoo linux]$ time make -C tools/perf build-test
> ...
> > In file included
Hi Arnaldo,
On Wed, 15 Oct 2014 17:06:30 -0300, Arnaldo Carvalho de Melo wrote:
> Next time please run: (I'm fixing this up this time)
>
> [acme@zoo linux]$ time make -C tools/perf build-test
...
> In file included from util/machine.c:14:0:
> util/unwind.h: In function ‘unwind__prepare_access’:
>
Hi Arnaldo,
On Wed, 15 Oct 2014 17:06:30 -0300, Arnaldo Carvalho de Melo wrote:
Next time please run: (I'm fixing this up this time)
[acme@zoo linux]$ time make -C tools/perf build-test
...
In file included from util/machine.c:14:0:
util/unwind.h: In function ‘unwind__prepare_access’:
Em Wed, Oct 22, 2014 at 10:34:27AM +0900, Namhyung Kim escreveu:
Hi Arnaldo,
On Wed, 15 Oct 2014 17:06:30 -0300, Arnaldo Carvalho de Melo wrote:
Next time please run: (I'm fixing this up this time)
[acme@zoo linux]$ time make -C tools/perf build-test
...
In file included from
Hi Arnaldo,
On Thu, Oct 16, 2014 at 5:06 AM, Arnaldo Carvalho de Melo
wrote:
> Em Wed, Oct 15, 2014 at 04:24:41PM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Mon, Oct 13, 2014 at 08:11:58PM +0200, Jiri Olsa escreveu:
>> > On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
>> > >
Hi Arnaldo,
On Thu, Oct 16, 2014 at 5:06 AM, Arnaldo Carvalho de Melo
a...@kernel.org wrote:
Em Wed, Oct 15, 2014 at 04:24:41PM -0300, Arnaldo Carvalho de Melo escreveu:
Em Mon, Oct 13, 2014 at 08:11:58PM +0200, Jiri Olsa escreveu:
On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
Em Wed, Oct 15, 2014 at 04:24:41PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, Oct 13, 2014 at 08:11:58PM +0200, Jiri Olsa escreveu:
> > On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
> > > Hello,
> > >
> > > This is v4 for libunwind callchain post processing speed up. It
Em Mon, Oct 13, 2014 at 08:11:58PM +0200, Jiri Olsa escreveu:
> On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
> > Hello,
> >
> > This is v4 for libunwind callchain post processing speed up. It was
> > able to reduce 50% of processing time by using global cache provided
> > in
Em Mon, Oct 13, 2014 at 08:11:58PM +0200, Jiri Olsa escreveu:
On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
Hello,
This is v4 for libunwind callchain post processing speed up. It was
able to reduce 50% of processing time by using global cache provided
in libunwind. In
Em Wed, Oct 15, 2014 at 04:24:41PM -0300, Arnaldo Carvalho de Melo escreveu:
Em Mon, Oct 13, 2014 at 08:11:58PM +0200, Jiri Olsa escreveu:
On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
Hello,
This is v4 for libunwind callchain post processing speed up. It was
able
Em Mon, Oct 13, 2014 at 08:11:58PM +0200, Jiri Olsa escreveu:
> On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
> > Namhyung Kim (5):
> > perf report: Set callchain_param.record_mode for future use
> > perf callchain: Create an address space per thread
> > perf callchain: Use
Em Mon, Oct 13, 2014 at 08:11:58PM +0200, Jiri Olsa escreveu:
On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
Namhyung Kim (5):
perf report: Set callchain_param.record_mode for future use
perf callchain: Create an address space per thread
perf callchain: Use global
On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
> Hello,
>
> This is v4 for libunwind callchain post processing speed up. It was
> able to reduce 50% of processing time by using global cache provided
> in libunwind. In this version, I decided to use the existing
>
On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
Hello,
This is v4 for libunwind callchain post processing speed up. It was
able to reduce 50% of processing time by using global cache provided
in libunwind. In this version, I decided to use the existing
Hello,
This is v4 for libunwind callchain post processing speed up. It was
able to reduce 50% of processing time by using global cache provided
in libunwind. In this version, I decided to use the existing
callchain_param.record_mode instead of adding a new field in the
symbol_conf.
The patch 4
Hello,
This is v4 for libunwind callchain post processing speed up. It was
able to reduce 50% of processing time by using global cache provided
in libunwind. In this version, I decided to use the existing
callchain_param.record_mode instead of adding a new field in the
symbol_conf.
The patch 4
24 matches
Mail list logo
