All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	Namhyung Kim <namhyung@kernel.org>,
	David Ahern <dsahern@gmail.com>,
	"ak@linux.intel.com" <ak@linux.intel.com>
Subject: Re: [BUG] perf mem: perf mem report fails in TUI mode
Date: Wed, 10 Dec 2014 16:30:14 +0100	[thread overview]
Message-ID: <20141210153014.GC6877@krava.brq.redhat.com> (raw)
In-Reply-To: <CABPqkBTLjQPymwDgNKdOshZimKQ0DGWaqm0gC8uFbwPK7vWrsA@mail.gmail.com>

On Tue, Dec 09, 2014 at 11:15:13PM -0500, Stephane Eranian wrote:
> Hi,
> 
> I was running a couple of tests with perf mem from tip.git and
> found that perf mem -t load rep was failing only in TUI mode.
> With --stdio, it works fine. I did a bit of investigation and found
> out that the TUI mode is failing because some symbol (kernel)
> is showing up with a huge (negative) size. I don't understand
> the connection between the TUI vs. tty browser and symbols.
> 
> To reproduce:
>     $ perf mem -t load rec my_test_program
>     $ perf mem -t load rep
>     $ perf mem -t load rep --stdio

hi,
I couldn't reproduce any failure on the acme's perf/core

since you indicated it's data dependent, could you share
your perf.data?

thanks,
jirka

> 
> Debugging with TUI is a pain, so I stopped.
> 
> I have a patch to improve perf mem a bit but I'd like to get this problem
> fixed first.
> 
> Maybe you have a idea of what's going on.
> 
> Thanks.

  parent reply	other threads:[~2014-12-10 15:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10  4:15 [BUG] perf mem: perf mem report fails in TUI mode Stephane Eranian
2014-12-10  5:18 ` David Ahern
2014-12-10 15:21   ` Stephane Eranian
2014-12-10 15:30 ` Jiri Olsa [this message]
2014-12-10 15:46   ` Stephane Eranian
2014-12-10 16:12     ` Jiri Olsa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141210153014.GC6877@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.