From: David Miller <davem@davemloft.net>
To: david.ahern@oracle.com
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: maps mismatch in /proc/kcore for sparc
Date: Wed, 18 Mar 2015 19:43:59 +0000 [thread overview]
Message-ID: <20150318.154359.1325469409095627387.davem@davemloft.net> (raw)
In-Reply-To: <5509AE36.8040902@oracle.com>
From: David Ahern <david.ahern@oracle.com>
Date: Wed, 18 Mar 2015 10:56:22 -0600
> I am trying to understand why the perf tool on sparc fails to convert
> kernel symbols when /proc/kcore is used. I have instrumented perf to
> the point I can see that it drops symbols from kallsyms because it
> cannot find a corresponding map when the kernel maps are created based
> on parsing /proc/kcore.
I'm looking into this, I think we need to set ARCH_PROC_KCORE_TEXT in
arch/sparc/Kconfig
I have an even worse problem on my T4 system, /proc/kcore is zero
length. Looking into that now as well.
next prev parent reply other threads:[~2015-03-18 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 16:56 maps mismatch in /proc/kcore for sparc David Ahern
2015-03-18 19:43 ` David Miller [this message]
2015-03-18 19:57 ` David Ahern
2015-03-18 20:14 ` David Miller
2015-03-18 21:22 ` David Ahern
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=20150318.154359.1325469409095627387.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david.ahern@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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).