From: Jiri Olsa <jolsa@redhat.com>
To: Vladimir Nikulichev <nvs@tbricks.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Correctly handle symbols in VDSO
Date: Tue, 8 Apr 2014 17:41:01 +0200 [thread overview]
Message-ID: <20140408154101.GA21094@krava.brq.redhat.com> (raw)
In-Reply-To: <3C60FB26-A78B-4E37-B4A6-E6F7283CEB4C@tbricks.com>
On Tue, Apr 08, 2014 at 07:24:22PM +0400, Vladimir Nikulichev wrote:
> Hi Namhyung,
>
> On Apr 7, 2014, at 10:14 AM, Namhyung Kim <namhyung@kernel.org> wrote:
>
> > Just one question below..
> >
> >>
> >> ---------------------------------------------------------------------------------------------------------------------------
> >>
> >> perf tools: Adjust symbols in VDSO
> >>
> >> Signed-off-by: Vladimir Nikulichev <nvs@tbricks.com>
> >>
> >> diff --git a/tools/perf/util/symbol-elf.c b/tools/perf/util/symbol-elf.c
> >> index 3b7dbf5..9c8b23b 100644
> >> --- a/tools/perf/util/symbol-elf.c
> >> +++ b/tools/perf/util/symbol-elf.c
> >> @@ -6,6 +6,7 @@
> >> #include <inttypes.h>
> >>
> >> #include "symbol.h"
> >> +#include "vdso.h"
> >> #include <symbol/kallsyms.h>
> >> #include "debug.h"
> >>
> >> @@ -618,6 +619,8 @@ int symsrc__init(struct symsrc *ss, struct dso *dso, const char *name,
> >> GElf_Shdr shdr;
> >> ss->adjust_symbols = (ehdr.e_type == ET_EXEC ||
> >> ehdr.e_type == ET_REL ||
> >> + (dso->symsrc_filename == NULL &&
> >
> > Is this really needed? Just checking is_vdso_map() seems to work well
> > for me. Did you have a specific reason to add it?
> >
>
> Nothing specific, just to don't call string operations in most cases. But here it is only a matter of coding style, of course.
> Attaching shorter version of the patch.
>
> ----------------------------
>
> perf tools: Adjust symbols in VDSO
hi,
could you please put explanation from first email
into the patch changelog?
cc-ing lkml
thanks,
jirka
next prev parent reply other threads:[~2014-04-08 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 19:15 [PATCH] Correctly handle symbols in VDSO Vladimir Nikulichev
2014-04-07 6:14 ` Namhyung Kim
2014-04-08 15:24 ` Vladimir Nikulichev
2014-04-08 15:41 ` Jiri Olsa [this message]
[not found] ` <A7CC2084-4F71-436C-9AEC-394F66A4981E@tbricks.com>
2014-04-09 15:35 ` Jiri Olsa
2014-04-09 16:13 ` Jiri Olsa
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=20140408154101.GA21094@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nvs@tbricks.com \
--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;
as well as URLs for NNTP newsgroup(s).