From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Mark Santaniello <marksan@fb.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Support perf script -F brstackoff,dso
Date: Mon, 19 Jun 2017 15:12:50 -0300 [thread overview]
Message-ID: <20170619181250.GO3645@kernel.org> (raw)
In-Reply-To: <20170619163825.2012979-2-marksan@fb.com>
Em Mon, Jun 19, 2017 at 09:38:25AM -0700, Mark Santaniello escreveu:
> With the new "brstackoff,dso" we get what we need: a simple offset into a
> specific dso/binary that uniquely identifies a branch/target:
You forgot to update tools/perf/Documentation/perf-script.txt about
'brstackoff', I added a line using the above explanation, please check
later and improve/expand it.
Thanks,
- Arnaldo
next prev parent reply other threads:[~2017-06-19 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 16:38 [PATCH 1/2] Support perf script -F brstack,dso and brstacksym,dso Mark Santaniello
2017-06-19 16:38 ` [PATCH 2/2] Support perf script -F brstackoff,dso Mark Santaniello
2017-06-19 18:12 ` Arnaldo Carvalho de Melo [this message]
2017-06-20 15:10 ` Mark Santaniello
2017-06-20 9:04 ` [tip:perf/core] perf script: Support " tip-bot for Mark Santaniello
2017-06-20 9:04 ` [tip:perf/core] perf script: Support -F brstack,dso and brstacksym,dso tip-bot for Mark Santaniello
-- strict thread matches above, loose matches on Subject: below --
2017-06-12 22:51 [PATCH 1/2] Support perf script " Mark Santaniello
2017-06-12 22:51 ` [PATCH 2/2] Support perf script -F brstackoff,dso Mark Santaniello
2017-06-12 23:36 ` Arnaldo Carvalho de Melo
2017-06-13 3:53 ` Mark Santaniello
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=20170619181250.GO3645@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marksan@fb.com \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox