From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Cc: Thomas Richter <tmricht@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com
Subject: Re: [PATCH] perf annotate: Fix unnecessary memory allocation for s390x
Date: Thu, 30 Nov 2017 16:05:25 -0300 [thread overview]
Message-ID: <20171130190525.GR3298@kernel.org> (raw)
In-Reply-To: <a5f06775-0d93-d57d-809a-cb198578ebfc@linux.vnet.ibm.com>
Em Wed, Nov 29, 2017 at 06:04:56PM +0530, Ravi Bangoria escreveu:
>
>
> On 11/24/2017 03:16 PM, Thomas Richter wrote:
> > This patch fixes a bug introduced with commit d9f8dfa9baf9
> > ("perf annotate s390: Implement jump types for perf annotate").
> >
> > Perf annotate displays annotated assembler output by reading
> > output of command objdump and parsing the disassembled lines. For
> > each shown mnemonic this function sequence is executed:
> >
> > disasm_line__new()
> > |
> > +--> disasm_line__init_ins()
> > |
> > +--> ins__find()
> > |
> > +--> arch->associate_instruction_ops()
> >
> > The s390x specific function assigned to function pointer
> > associate_instruction_ops refers to function
> > s390__associate_ins_ops(). This function checks for supported
> > mnemonics and assigns a NULL pointer to unsupported mnemonics.
> > However even the NULL pointer is added to the architecture
> > dependend instruction array.
> >
> > This leads to an extremely large architecture instruction array
> > (due to array resize logic in function arch__grow_instructions()).
> > Depending on the objdump output being parsed the array can end up
> > with several ten-thousand elements.
> >
> > This patch checks if a mnemonic is supported and only adds
> > supported ones into the architecture instruction array. The
> > array does not contain elements with NULL pointers anymore.
> >
> > Before the patch (With some debug printf output):
> > [root@s35lp76 perf]# time ./perf annotate --stdio > /tmp/xxxbb
> >
> > real 8m49.679s
> > user 7m13.008s
> > sys 0m1.649s
> > [root@s35lp76 perf]# fgrep '__ins__find sorted:1 nr_instructions:'
> > /tmp/xxxbb | tail -1
> > __ins__find sorted:1 nr_instructions:87433 ins:0x341583c0
> > [root@s35lp76 perf]#
> >
> > The number of different s390x branch/jump/call/return instructions
> > entered into the array is 87433.
> >
> > After the patch (With some printf debug output:)
> >
> > [root@s35lp76 perf]# time ./perf annotate --stdio > /tmp/xxxaa
> >
> > real 1m24.553s
> > user 0m0.587s
> > sys 0m1.530s
> > [root@s35lp76 perf]# fgrep '__ins__find sorted:1 nr_instructions:'
> > /tmp/xxxaa | tail -1
> > __ins__find sorted:1 nr_instructions:56 ins:0x3f406570
> > [root@s35lp76 perf]#
> >
> > The number of different s390x branch/jump/call/return instructions
> > entered into the array is 56 which is sensible.
>
> Ack-by: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Thanks, applied.
- Arnaldo
> > Signed-off-by: Thomas Richter <tmricht@linux.vnet.ibm.com>
> > Reviewed-by: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
> > ---
> > tools/perf/arch/s390/annotate/instructions.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/arch/s390/annotate/instructions.c b/tools/perf/arch/s390/annotate/instructions.c
> > index c9a81673e8aa..89f0b6c00e3f 100644
> > --- a/tools/perf/arch/s390/annotate/instructions.c
> > +++ b/tools/perf/arch/s390/annotate/instructions.c
> > @@ -16,7 +16,8 @@ static struct ins_ops *s390__associate_ins_ops(struct arch *arch, const char *na
> > if (!strcmp(name, "br"))
> > ops = &ret_ops;
> >
> > - arch__associate_ins_ops(arch, name, ops);
> > + if (ops)
> > + arch__associate_ins_ops(arch, name, ops);
> > return ops;
> > }
> >
prev parent reply other threads:[~2017-11-30 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 9:46 [PATCH] perf annotate: Fix unnecessary memory allocation for s390x Thomas Richter
2017-11-29 12:34 ` Ravi Bangoria
2017-11-30 19:05 ` Arnaldo Carvalho de Melo [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=20171130190525.GR3298@kernel.org \
--to=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=ravi.bangoria@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=tmricht@linux.vnet.ibm.com \
/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).