From: Jiri Olsa <jolsa@redhat.com>
To: Songshan Gong <gongss@linux.vnet.ibm.com>
Cc: acme@kernel.org, jolsa@kernel.org, dsahern@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC V1]s390/perf: fix 'start' address of module's map
Date: Fri, 8 Jul 2016 17:20:37 +0200 [thread overview]
Message-ID: <20160708152037.GH31763@krava> (raw)
In-Reply-To: <5c24562a-17ee-d30e-0308-5ec141ff52f1@linux.vnet.ibm.com>
On Fri, Jul 08, 2016 at 10:17:30AM +0800, Songshan Gong wrote:
SNIP
> > diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
> > index b177218..e5c2721 100644
> > --- a/tools/perf/util/machine.c
> > +++ b/tools/perf/util/machine.c
> > @@ -1091,12 +1091,18 @@ static int machine__set_modules_path(struct machine *machine)
> >
> > return map_groups__set_modules_path_dir(&machine->kmaps, modules_path, 0);
> > }
> > +int __weak arch__fix_module_baseaddr(struct machine *machine __maybe_unused,
> > + u64 *start __maybe_unused, const char *name __maybe_unused)
> > +{
> > + return 0;
> > +}
> >
> > static int machine__create_module(void *arg, const char *name, u64 start)
> > {
> > struct machine *machine = arg;
> > struct map *map;
> >
> > + arch__fix_module_baseaddr(machine, &start, name);
>
> As the description says, I would change the function name to
> 'arch__fix_module_text_start';
both of them sound good to me
jirka
next prev parent reply other threads:[~2016-07-08 15:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 1:49 [PATCH] [RFC V1]s390/perf: fix 'start' address of module's map Song Shan Gong
2016-07-08 2:17 ` Songshan Gong
2016-07-08 15:20 ` Jiri Olsa [this message]
2016-07-08 15:18 ` Jiri Olsa
2016-07-11 8:11 ` Songshan Gong
2016-07-13 3:32 ` Songshan Gong
2016-07-08 15:20 ` Jiri Olsa
2016-07-08 15:21 ` Jiri Olsa
2016-07-08 15:21 ` Jiri Olsa
2016-07-11 11:06 ` Songshan Gong
2016-07-11 12:01 ` Jiri Olsa
2016-07-13 6:39 ` Songshan Gong
2016-07-13 9:07 ` Jiri Olsa
2016-07-15 7:45 ` Songshan Gong
2016-07-15 8:27 ` Jiri Olsa
2016-07-15 13:23 ` 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=20160708152037.GH31763@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=gongss@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.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).