From: Alexis Berlemont <alexis.berlemont@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com
Subject: Re: [PATCH] perf annotate: check that objdump correctly works
Date: Sat, 10 Dec 2016 00:57:26 +0100 [thread overview]
Message-ID: <20161209235726.GC22075@therese> (raw)
In-Reply-To: <20161206193805.GB8257@kernel.org>
Arnaldo Carvalho de Melo wrote:
> Em Thu, Dec 01, 2016 at 01:04:36AM +0100, Alexis Berlemont escreveu:
> > Before disassembling, the tool objdump is called just to be sure:
> > * objdump is available in the path;
> > * objdump is an executable binary;
> > * objdump has no dependency issue or anything else.
> >
> > This objdump "pre-"command is only necessary because the real objdump
> > command is followed by some " | grep ..."; this prevents the shell
> > from returning the exit code of objdump execution.
> >
> > Signed-off-by: Alexis Berlemont <alexis.berlemont@gmail.com>
> > ---
> > tools/perf/util/annotate.c | 79 +++++++++++++++++++++++++++++++++++++++++++++-
> > tools/perf/util/annotate.h | 3 ++
> > 2 files changed, 81 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/util/annotate.c b/tools/perf/util/annotate.c
> > index 3e34ee0..9d6c3a0 100644
> > --- a/tools/perf/util/annotate.c
>
> > +static int annotate__check_objdump(void)
> > +{
> > + char command[PATH_MAX * 2];
> > + int wstatus, err;
> > + pid_t pid;
> > +
> > + snprintf(command, sizeof(command),
> > + "%s -v > /dev/null 2>&1",
> > + objdump_path ? objdump_path : "objdump");
> > +
> > + pid = fork();
> > + if (pid < 0) {
> > + pr_err("Failure forking to run %s\n", command);
> > + return -1;
> > + }
> > +
> > + if (pid == 0) {
> > + execl("/bin/sh", "sh", "-c", command, NULL);
> > + exit(-1);
> > + }
> > +
> > + err = waitpid(pid, &wstatus, 0);
> > + if (err < 0) {
> > + pr_err("Failure calling waitpid: %s: (%s)\n",
> > + strerror(errno), command);
> > + return -1;
> > + }
> > +
> > + pr_err("%s: %d %d\n", command, pid, WEXITSTATUS(wstatus));
>
> So this will appear in all cases, no need for that, i.e. in the success
> case we don't need to get that flashing on the screen, on the last line.
>
Many thanks for your answer and your time.
Sorry for the late anwser and such an obvious error.
> > + switch (WEXITSTATUS(wstatus)) {
> > + case 0:
> > + /* Success */
> > + err = 0;
> > + break;
>
> So probably you want to return 0; here instead and then at the error
> case, i.e. when you set err to !0 you do that pr_err() call above, but I
> think it would be better to use pr_debug(), the warning on the popup box
> is what by default is more polished to tell the user, the details are
> for developers or people wanting to dig in.
>
> But while doing this I thought that you could instead call this only
> after objdump fails, i.e. if all is right, no need for checking what
> went wrong.
>
> I.e. you would do the grep step separately, after checking objdump's
> error.
>
> If you think that is too much work, then please just do the
> pr_err->pr_debug conversion, which would remove the flashing for the
> success case.
I will do the grep separately; no problem.
Alexis.
>
> I tested it, btw, using:
>
> perf annotate --objdump /dev/null page_fault
>
> Which produced a better output than what we have now (nothing):
>
> ??????Error:????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
> ???Couldn't annotate page_fault: ???
> ???The objdump tool found in $PATH cannot be executed???
> ??? ???
> ??? ???
> ???Press any key... ???
> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
>
>
>
> /dev/null -v > /dev/null 2>&1: 10336 126
>
>
> -------------------
>
> summary: make that last line appear only when -v is used (pr_debug) and
> consider covering the case where --objdump was used, where talking about $PATH
> is misleading.
>
>
> > + case 127:
> > + /* The shell did not find objdump in the path */
> > + err = SYMBOL_ANNOTATE_ERRNO__NO_OBJDUMP;
> > + break;
> > + default:
> > + /*
> > + * In the default case, we consider that objdump
> > + * cannot be executed; so it gathers many fault
> > + * scenarii:
> > + * - objdump is not an executable (126);
> > + * - objdump has some dependency issue;
> > + * - ...
> > + */
> > + err = SYMBOL_ANNOTATE_ERRNO__NO_EXEC_OBJDUMP;
> > + break;
> > + }
> > +
> > + return err;
> > +}
> > +
> > static const char *annotate__norm_arch(const char *arch_name)
> > {
> > struct utsname uts;
> > @@ -1351,6 +1424,10 @@ int symbol__disassemble(struct symbol *sym, struct map *map, const char *arch_na
> > if (err)
> > return err;
> >
> > + err = annotate__check_objdump();
> > + if (err)
> > + return err;
> > +
> > arch_name = annotate__norm_arch(arch_name);
> > if (!arch_name)
> > return -1;
> > @@ -1482,7 +1559,7 @@ int symbol__disassemble(struct symbol *sym, struct map *map, const char *arch_na
> > delete_last_nop(sym);
> >
> > fclose(file);
> > - err = 0;
> > + err = nline == 0 ? SYMBOL_ANNOTATE_ERRNO__NO_OUTPUT : 0;
> > out_remove_tmp:
> > close(stdout_fd[0]);
> >
> > diff --git a/tools/perf/util/annotate.h b/tools/perf/util/annotate.h
> > index 87e4cad..123f60c 100644
> > --- a/tools/perf/util/annotate.h
> > +++ b/tools/perf/util/annotate.h
> > @@ -172,6 +172,9 @@ enum symbol_disassemble_errno {
> > __SYMBOL_ANNOTATE_ERRNO__START = -10000,
> >
> > SYMBOL_ANNOTATE_ERRNO__NO_VMLINUX = __SYMBOL_ANNOTATE_ERRNO__START,
> > + SYMBOL_ANNOTATE_ERRNO__NO_EXEC_OBJDUMP,
> > + SYMBOL_ANNOTATE_ERRNO__NO_OBJDUMP,
> > + SYMBOL_ANNOTATE_ERRNO__NO_OUTPUT,
> >
> > __SYMBOL_ANNOTATE_ERRNO__END,
> > };
> > --
> > 2.10.2
next prev parent reply other threads:[~2016-12-09 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 0:04 [PATCH] perf: check that objdump correctly works Alexis Berlemont
2016-12-01 0:04 ` [PATCH] perf annotate: " Alexis Berlemont
2016-12-06 19:38 ` Arnaldo Carvalho de Melo
2016-12-09 23:57 ` Alexis Berlemont [this message]
2016-12-20 0:11 ` [PATCH v2 0/1] perf: " Alexis Berlemont
2016-12-20 0:11 ` [PATCH v2 1/1] perf annotate: " Alexis Berlemont
2016-12-06 14:44 ` [PATCH] perf: " Arnaldo Carvalho de Melo
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=20161209235726.GC22075@therese \
--to=alexis.berlemont@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.