From: David Ahern <daahern@cisco.com>
To: Arun Sharma <arun@sharma-home.net>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-perf-users@vger.kernel.org
Subject: Re: [RFC] --dump-sym-trace
Date: Mon, 14 Feb 2011 17:03:47 -0700 [thread overview]
Message-ID: <4D59C2E3.1030306@cisco.com> (raw)
In-Reply-To: <AANLkTimuEQVDdR7kZeDG0O3UUpyXd2+wA73b6HtrhTVU@mail.gmail.com>
On 02/14/11 17:00, Arun Sharma wrote:
> On Fri, Feb 4, 2011 at 6:38 PM, David Ahern <daahern@cisco.com> wrote:
>
>> I take it your mileage varied from the above.
>
> I can't reproduce the issue anymore and the code looks just fine. The
> issue I had was:
>
> perf record -a -T + perf report --timehist produced samples where:
> perf record --timehist + perf report --timehist didn't.
You need the --timehist on both to work properly. If you add it to
report but not record then you are asking for information that was not
recorded. Something to be addressed for proper inclusion.
I've been wanting to use this time history option to record/analyze
syscall events lately. I'll see if I can spend some time on it this week.
David
>
> -Arun
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-02-15 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 1:47 [RFC] --dump-sym-trace Arun Sharma
2011-01-26 2:29 ` David Ahern
2011-01-28 21:18 ` Arun Sharma
2011-01-28 21:41 ` David Ahern
2011-01-29 20:50 ` Arnaldo Carvalho de Melo
2011-02-05 1:48 ` Arun Sharma
2011-02-05 2:38 ` David Ahern
2011-02-15 0:00 ` Arun Sharma
2011-02-15 0:03 ` David Ahern [this message]
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=4D59C2E3.1030306@cisco.com \
--to=daahern@cisco.com \
--cc=acme@ghostprotocols.net \
--cc=arun@sharma-home.net \
--cc=linux-perf-users@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).