From: Songshan Gong <gongss@linux.vnet.ibm.com>
To: Jiri Olsa <jolsa@redhat.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: Mon, 11 Jul 2016 16:11:55 +0800 [thread overview]
Message-ID: <71b0ebd9-a50d-faef-933d-2258ae19236e@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160708151836.GG31763@krava>
在 7/8/2016 11:18 PM, Jiri Olsa 写道:
> On Thu, Jul 07, 2016 at 09:49:36AM +0800, Song Shan Gong wrote:
>> At preset, when creating module's map, perf gets 'start' address by parsing
>> 'proc/modules', but it's module base address, isn't the start address of
>> '.text' section. In most archs, it's OK. But for s390, it places 'GOT' and
>> 'PLT' relocations before '.text' section. So there exists an offset between
>> module base address and '.text' section, which will incur wrong symbol
>> resolution for modules.
>>
>> Fix this bug by getting 'start' address of module's map from parsing
>> '/sys/module/[module name]/sections/.text', not from '/proc/modules'.
>
> cool, does this fix the 'perf test 1' for s390? that'd be great
I've checked, 'perf test 1' is still failed. But the test is for testing
whether 'vmlinux symtab matches kallsyms'. For vmlinux, it's built when
compiling linux-kernel, so there's no any symbol info about module. For
kallsyms, when loading, it also splits kernel symbols with module
symbols. But this patch is intended to fix wrong symbol resolution for
modules, so I think there's no relationship between this patch and the
testcase 'perf test 1'.
I also debuged the reason why 'perf test 1' fails, there are two reasons
at least:
1. perf gets kernel start address by finding the first no-zero value of
symbols {'_text', '_stext'} in /proc/kallsyms; for s390, it's always
'_stext', but actually, '_stext' is not the first symbol in s390, there
are other symbols before '_stext', for example 'iplstart'.
2. In addition, when loading by parsing /proc/kallsyms, if the kernel
map start value is a non-zero value getting from '_stext', because
'_text' is zero, it will not be included in kernel map; but for vmlinux,
it always add '_text' to kernel map whether '_text' is zero or not. So
if '_text' is zero, whether adding '_text' to kernel map, it's
non-consistent for loading by /proc/kallsyms and vmlinux.
I'll try to fix this bug later.
Thanks for your comments.
> I'll send few coments shortly
>
> thanks,
> jirka
>
--
SongShan Gong
next prev parent reply other threads:[~2016-07-11 8:12 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
2016-07-08 15:18 ` Jiri Olsa
2016-07-11 8:11 ` Songshan Gong [this message]
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=71b0ebd9-a50d-faef-933d-2258ae19236e@linux.vnet.ibm.com \
--to=gongss@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--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).