From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Jin Yao <yao.jin@linux.intel.com>,
Song Liu <songliubraving@fb.com>,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 1/5] perf annotate: avoid reallocation in objdump parsing
Date: Mon, 14 Oct 2019 11:15:03 -0300 [thread overview]
Message-ID: <20191014141503.GF19627@kernel.org> (raw)
In-Reply-To: <20191010183649.23768-2-irogers@google.com>
Em Thu, Oct 10, 2019 at 11:36:45AM -0700, Ian Rogers escreveu:
> Objdump output is parsed using getline which allocates memory for the
> read. Getline will realloc if the memory is too small, but currently the
> line is always freed after the call.
> Simplify parse_objdump_line by performing the reading in symbol__disassemble.
Thanks, applied.
- Arnaldo
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/annotate.c | 26 ++++++++++++++------------
> 1 file changed, 14 insertions(+), 12 deletions(-)
>
> diff --git a/tools/perf/util/annotate.c b/tools/perf/util/annotate.c
> index e830eadfca2a..1487849a191a 100644
> --- a/tools/perf/util/annotate.c
> +++ b/tools/perf/util/annotate.c
> @@ -1485,24 +1485,17 @@ annotation_line__print(struct annotation_line *al, struct symbol *sym, u64 start
> * means that it's not a disassembly line so should be treated differently.
> * The ops.raw part will be parsed further according to type of the instruction.
> */
> -static int symbol__parse_objdump_line(struct symbol *sym, FILE *file,
> +static int symbol__parse_objdump_line(struct symbol *sym,
> struct annotate_args *args,
> - int *line_nr)
> + char *line, int *line_nr)
> {
> struct map *map = args->ms.map;
> struct annotation *notes = symbol__annotation(sym);
> struct disasm_line *dl;
> - char *line = NULL, *parsed_line, *tmp, *tmp2;
> - size_t line_len;
> + char *parsed_line, *tmp, *tmp2;
> s64 line_ip, offset = -1;
> regmatch_t match[2];
>
> - if (getline(&line, &line_len, file) < 0)
> - return -1;
> -
> - if (!line)
> - return -1;
> -
> line_ip = -1;
> parsed_line = strim(line);
>
> @@ -1539,7 +1532,6 @@ static int symbol__parse_objdump_line(struct symbol *sym, FILE *file,
> args->ms.sym = sym;
>
> dl = disasm_line__new(args);
> - free(line);
> (*line_nr)++;
>
> if (dl == NULL)
> @@ -1855,6 +1847,8 @@ static int symbol__disassemble(struct symbol *sym, struct annotate_args *args)
> int lineno = 0;
> int nline;
> pid_t pid;
> + char *line;
> + size_t line_len;
> int err = dso__disassemble_filename(dso, symfs_filename, sizeof(symfs_filename));
>
> if (err)
> @@ -1943,18 +1937,26 @@ static int symbol__disassemble(struct symbol *sym, struct annotate_args *args)
> goto out_free_command;
> }
>
> + /* Storage for getline. */
> + line = NULL;
> + line_len = 0;
> +
> nline = 0;
> while (!feof(file)) {
> + if (getline(&line, &line_len, file) < 0 || !line)
> + break;
> +
> /*
> * The source code line number (lineno) needs to be kept in
> * across calls to symbol__parse_objdump_line(), so that it
> * can associate it with the instructions till the next one.
> * See disasm_line__new() and struct disasm_line::line_nr.
> */
> - if (symbol__parse_objdump_line(sym, file, args, &lineno) < 0)
> + if (symbol__parse_objdump_line(sym, args, line, &lineno) < 0)
> break;
> nline++;
> }
> + free(line);
>
> if (nline == 0)
> pr_err("No output from %s\n", command);
> --
> 2.23.0.581.g78d2f28ef7-goog
--
- Arnaldo
next prev parent reply other threads:[~2019-10-14 14:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 18:36 [PATCH 0/5] Improve objdump parsing, fix LLVM objdump Ian Rogers
2019-10-10 18:36 ` [PATCH 1/5] perf annotate: avoid reallocation in objdump parsing Ian Rogers
2019-10-14 14:15 ` Arnaldo Carvalho de Melo [this message]
2019-10-21 23:19 ` [tip: perf/core] perf annotate: Avoid " tip-bot2 for Ian Rogers
2019-10-10 18:36 ` [PATCH 2/5] perf annotate: use run-command.h to fork objdump Ian Rogers
2019-10-14 14:18 ` Arnaldo Carvalho de Melo
2019-10-15 0:35 ` Ian Rogers
2019-10-21 23:19 ` [tip: perf/core] perf annotate: Use libsubcmd's " tip-bot2 for Ian Rogers
2019-10-10 18:36 ` [PATCH 3/5] perf annotate: don't pipe objdump output through grep Ian Rogers
2019-10-14 14:19 ` Arnaldo Carvalho de Melo
2019-10-21 23:19 ` [tip: perf/core] perf annotate: Don't pipe objdump output through 'grep' command tip-bot2 for Ian Rogers
2019-10-10 18:36 ` [PATCH 4/5] perf annotate: don't pipe objdump output through expand Ian Rogers
2019-10-14 14:24 ` Arnaldo Carvalho de Melo
2019-10-21 23:19 ` [tip: perf/core] perf annotate: Don't pipe objdump output through 'expand' command tip-bot2 for Ian Rogers
2019-10-10 18:36 ` [PATCH 5/5] perf annotate: fix objdump --no-show-raw-insn flag Ian Rogers
2019-10-14 14:24 ` Arnaldo Carvalho de Melo
2019-10-21 23:19 ` [tip: perf/core] perf annotate: Fix " tip-bot2 for Ian Rogers
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=20191014141503.GF19627@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=yao.jin@linux.intel.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