From: Adrian Hunter <adrian.hunter@intel.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: linux-kernel@vger.kernel.org, acme@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 1/4] perf tests: take into account address of each objdump line
Date: Thu, 3 Sep 2015 14:35:29 +0300 [thread overview]
Message-ID: <55E83081.5030102@intel.com> (raw)
In-Reply-To: <786600d67e80b0b0229a4eb16134244b23783c43.1441275982.git.jstancek@redhat.com>
On 03/09/15 14:23, Jan Stancek wrote:
> objdump output can contain repeated bytes. At the moment test reads
> all output sequentially, assuming each address is represented in
> output only once:
>
> ffffffff8164efb3 <retint_swapgs+0x9>:
> ffffffff8164efb3: c1 5d 00 eb rcrl $0xeb,0x0(%rbp)
> ffffffff8164efb7: 00 4c 8b 5c add %cl,0x5c(%rbx,%rcx,4)
>
> ffffffff8164efb8 <restore_c_regs_and_iret>:
> ffffffff8164efb8: 4c 8b 5c 24 30 mov 0x30(%rsp),%r11
> ffffffff8164efbd: 4c 8b 54 24 38 mov 0x38(%rsp),%r10
>
> Store objdump output to buffer according to offset calculated
> from address on each line.
>
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> Cc: David Ahern <dsahern@gmail.com>
> Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Paul Mackerras <paulus@samba.org>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> ---
> tools/perf/tests/code-reading.c | 53 +++++++++++++++++++++++++++++++----------
> 1 file changed, 40 insertions(+), 13 deletions(-)
>
> Changes in v3:
> align read_objdump_line parameters on 2nd line
> fix multiline comment
> replace MIN with min
>
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
next prev parent reply other threads:[~2015-09-03 11:38 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
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 [this message]
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=55E83081.5030102@intel.com \
--to=adrian.hunter@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--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 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.