All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	linux-perf-users@vger.kernel.org,
	2nddept-manager@sdl.hitachi.co.jp
Subject: Re: perf-probe: issue with latest fedora kernel
Date: Fri, 10 Dec 2010 12:27:59 +0900	[thread overview]
Message-ID: <4D019E3F.4040902@hitachi.com> (raw)
In-Reply-To: <m2k4jiewhi.fsf@gmail.com>

(2010/12/10 1:34), Francis Moreau wrote:
> Arnaldo Carvalho de Melo <acme@ghostprotocols.net> writes:
> 
>> Em Thu, Dec 09, 2010 at 04:00:08PM +0100, Francis Moreau escreveu:
>>> I'm trying to use perf-probe(1) with the latest F14 kernel
>>> (2.6.35.9-64.fc14.x86_64).
>>>
>>
>>> I also installed kernel-debug-debuginfo-2.6.35.9-64.fc14.x86_64 which
>>> contains the running vmlinux image AFAICT.
>>>
>>> I added it to the buildid cache:
>>>
>>> $ perf buildid-cache -v -a /usr/lib/debug/lib/modules/2.6.35.9-64.fc14.x86_64.debug/vmlinux
>>> Adding 4d89e23415d8ab491cfc8ef8aa67764b91cc6787 /usr/lib/debug/lib/modules/2.6.35.9-64.fc14.x86_64.debug/vmlinux: OK
>>>
>>> But when running perf-probe(1) like the following:
>>>
>>>   $ perf probe schedule cpu
>>>   Failed to find path of kernel moduleFailed to open debuginfo file.
>>>   Error: Failed to add events. (-2)
>>>
>>> it fails.
>>>
>>> One strange thing is that when perf read the running kernel build id, it
>>> get: 882b1b53eb1d65320e8fa710273aa8493896c4.
>>>
>>> Could anybody tell me what I'm doing wrong ?
>>
>> Can you try using:
>>
>> $ perf probe -k /usr/lib/debug/lib/modules/2.6.35.9-64.fc14.x86_64.debug/vmlinux <rest of the probe definition>
>>
>> So that it tries it directly instead of looking into the buildid cache?
>>
> 
> Well that still fail:
> 
> $ perf probe -k /usr/lib/debug/lib/modules/2.6.35.9-64.fc14.x86_64.debug/vmlinux schedule cpu
> Failed to find path of kernel moduleFailed to open debuginfo file.
>   Error: Failed to add events. (-2)
> 
> but that's not really suprising if perf checks that the running kernel
> build-id is the same as the one in:
> /usr/lib/debug/lib/modules/2.6.35.9-64.fc14.x86_64.debug/vmlinux
> 
> It really looks like something is broken in the F14 kernel-debuginfo
> package.

Hmm, curious. I'll check it after setting up Fedora 14.
Thank you for reporting :-)


-- 
Masami HIRAMATSU
2nd Dept. Linux Technology Center
Hitachi, Ltd., Systems Development Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com

  reply	other threads:[~2010-12-10  3:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 15:00 perf-probe: issue with latest fedora kernel Francis Moreau
2010-12-09 15:35 ` Arnaldo Carvalho de Melo
2010-12-09 16:34   ` Francis Moreau
2010-12-10  3:27     ` Masami Hiramatsu [this message]
2010-12-10  7:53       ` Franck Bui-Huu
2010-12-10  8:26         ` Masami Hiramatsu
2010-12-10 13:00           ` Franck Bui-Huu
2010-12-10 13:06             ` [PATCH 1/2] perf-probe: do use the kernel image path given by 'k' option Franck Bui-Huu
2010-12-10 13:07             ` [PATCH 2/2] perf-probe: fail if the kernel image contains no symbol Franck Bui-Huu
2010-12-10  7:30   ` perf-probe: issue with latest fedora kernel Franck Bui-Huu
2010-12-12 14:08     ` Arnaldo Carvalho de Melo
2010-12-12 22:15       ` Franck Bui-Huu
2010-12-13 16:40         ` Arnaldo Carvalho de Melo
2010-12-13 10:02   ` Francis Moreau
2010-12-13 12:58     ` Arnaldo Carvalho de Melo
2010-12-13 13:08       ` Francis Moreau
2010-12-13 14:04         ` Masami Hiramatsu
2010-12-13 14:16           ` Francis Moreau
2010-12-13 19:08             ` Francis Moreau
2010-12-13 14:25           ` Arnaldo Carvalho de Melo
2010-12-13 14:21         ` Arnaldo Carvalho de Melo
2010-12-13 15:11           ` Francis Moreau
2010-12-13 16:40             ` Arnaldo Carvalho de Melo
2010-12-13 19:08               ` Francis Moreau
2010-12-13 19:17                 ` Arnaldo Carvalho de Melo
2010-12-13 19:32                   ` Francis Moreau
2010-12-15  8:57           ` Masami Hiramatsu
2010-12-15 18:53             ` Arnaldo Carvalho de Melo
2010-12-23 13:59             ` Franck Bui-Huu
2010-12-27 20:50               ` Franck Bui-Huu

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=4D019E3F.4040902@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=2nddept-manager@sdl.hitachi.co.jp \
    --cc=acme@ghostprotocols.net \
    --cc=francis.moro@gmail.com \
    --cc=linux-perf-users@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 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.