From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jan Stancek <jstancek@redhat.com>,
linux-kernel@vger.kernel.org, jolsa@kernel.org,
dsahern@gmail.com, cjashfor@linux.vnet.ibm.com,
fweisbec@gmail.com, mingo@kernel.org, namhyung@kernel.org,
paulus@samba.org, a.p.zijlstra@chello.nl
Subject: Re: [PATCH v3 2/4] perf tests: make objdump disassemble zero blocks
Date: Thu, 3 Sep 2015 12:14:10 -0300 [thread overview]
Message-ID: <20150903151410.GD11521@kernel.org> (raw)
In-Reply-To: <55E8309B.6040704@intel.com>
Em Thu, Sep 03, 2015 at 02:35:55PM +0300, Adrian Hunter escreveu:
> On 03/09/15 14:23, Jan Stancek wrote:
> > Add -z parameter to avoid skipping zero blocks:
> >
> > ffffffff816704fe <sysret_check+0x4b>:
> > ffffffff816704fe: 7b 34 jnp ffffffff81670534 <sysret_signal+0x1c>
> > ...
> > ffffffff81670501 <sysret_careful>:
> > ffffffff81670501: 0f ba e2 03 bt $0x3,%edx
> > ffffffff81670505: 73 11 jae ffffffff81670518 <sysret_signal>
>
> Acked-by: Adrian Hunter <adrian.hunter@intel.com>
Ok, I am applying this, but it would be nice to know in which systems,
with which objdump/binutils versions which 'perf test' entry fails, with
the output of such failure.
Jan, can you please provide this info?
- Arnaldo
next prev parent reply other threads:[~2015-09-03 15:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 8:19 [PATCH v2 1/4] perf tests: take into account address of each objdump line Jan Stancek
2015-09-02 8:19 ` [PATCH v2 2/4] perf tests: make objdump disassemble zero blocks Jan Stancek
2015-09-03 9:11 ` Adrian Hunter
2015-09-03 11:23 ` [PATCH v3 " Jan Stancek
2015-09-03 11:35 ` Adrian Hunter
2015-09-03 15:14 ` Arnaldo Carvalho de Melo [this message]
2015-09-03 16:19 ` Jan Stancek
2015-09-03 16:37 ` Arnaldo Carvalho de Melo
2015-09-15 6:58 ` [tip:perf/core] perf tests: Make " tip-bot for Jan Stancek
2015-09-02 8:19 ` [PATCH v2 3/4] perf tests: stop reading if objdump output crossed sections Jan Stancek
2015-09-03 9:12 ` Adrian Hunter
2015-09-15 6:58 ` [tip:perf/core] perf tests: Stop " tip-bot for Jan Stancek
2015-09-02 8:19 ` [PATCH v2 4/4] perf tests: print objdump/dso buffers if they don't match Jan Stancek
2015-09-03 9:12 ` Adrian Hunter
2015-09-15 6:58 ` [tip:perf/core] perf tests: Print objdump/dso buffers if they don 't match tip-bot for Jan Stancek
2015-09-03 9:08 ` [PATCH v2 1/4] perf tests: take into account address of each objdump line Adrian Hunter
2015-09-03 11:23 ` [PATCH v3 " Jan Stancek
2015-09-03 11:35 ` Adrian Hunter
2015-09-15 6:57 ` [tip:perf/core] perf tests: Take " tip-bot for Jan Stancek
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=20150903151410.GD11521@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adrian.hunter@intel.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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