This patch fixes an infinite loop problem with perf annotate when
the TUI is not used. When the perfconfig file is not found use_browser
remains at -1, when found and tui is disabled use_browser = 0. Thus the
correct test for TUI is use_browser > 0.
Signed-off-by: Stephane Eranian
diff --git a/t
Hi,
I'm a college student who just start to use perfmon on my research. I
have studied the perfmon menu but I don't quite understand the exact
meaning of events. The information I want to get out of a program are
the counts of instruction executed, memory instruction executed,
instruction cache hit
Hi,
I ran into another problem while running more tests with
perf record, perf buildid-list.
I do the following:
$ perf record foo/noploop 5
$ perf buildid-list
54b1e7cc3cf52e0db255aab44ce7538eb62655b8 [kernel.kallsyms]
875ae61623e89f408b425ca0486a9ec99e3ac73e
/home/eranian/perfmon/official/tip/
Em Thu, May 27, 2010 at 02:50:01PM +0200, Stephane Eranian escreveu:
> This patch fixes an infinite loop problem with perf annotate when
> the TUI is not used. When the perfconfig file is not found use_browser
> remains at -1, when found and tui is disabled use_browser = 0. Thus the
> correct test
Em Thu, May 27, 2010 at 11:51:42AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, May 27, 2010 at 02:50:01PM +0200, Stephane Eranian escreveu:
> > This patch fixes an infinite loop problem with perf annotate when
> > the TUI is not used. When the perfconfig file is not found use_browser
> > re
On Thu, May 27, 2010 at 5:45 PM, Arnaldo Carvalho de Melo
wrote:
> Em Thu, May 27, 2010 at 11:51:42AM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Thu, May 27, 2010 at 02:50:01PM +0200, Stephane Eranian escreveu:
>> > This patch fixes an infinite loop problem with perf annotate when
>> > the TU
