mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Lochmann <alexander.lochmann@tu-dortmund.de>
To: linux-kernel@vger.kernel.org
Subject: [RFC] perf record: missing buildid for callstack modules -- again
Date: Sat, 25 Jun 2016 17:46:55 +0200	[thread overview]
Message-ID: <576EA76F.8040509@tu-dortmund.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1275 bytes --]

Hi folks!

As mentioned by this discussion https://lkml.org/lkml/2016/1/7/661, perf
does not record the build id for modules, which are hit on the way down
the callstack.
Sadly that issue is not completely fixed by the cmd argument --buildid-all.
In my case, I have my own kernel module starting a kernel thread. It
does some stuff, and calls schedule from time to time.
If I start perf like this

	perf record -e sched:sched_stat_sleep -e sched:sched_switch -a -g -o
perf.data.raw -p <pid> -- sleep 10

, it records the callstacks for those three events.
Afterwards I want to do some post processing to generate a cold graph:

	perf inject -v -s -i perf.data.raw -o perf.data

That step fails ('failed to write feature 2') due to the lack of a
build-id for my module, which isn't included in perf.data.raw.

Can anyone confirm that this is a bug?
Does anyone have a workaround for it?

Thanks in advance!

Cheers,
Alex

P.S.: Pls put me in CC, because I'm not subscribed to the mailinglist.
-- 
Technische Universität Dortmund
Alexander Lochmann                PGP key: 0xBC3EF6FD
Otto-Hahn-Str. 16                 phone:  +49.231.7556141
D-44227 Dortmund                  fax:    +49.231.7556116
http://ess.cs.tu-dortmund.de/Staff/al


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2016-06-25 16:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=576EA76F.8040509@tu-dortmund.de \
    --to=alexander.lochmann@tu-dortmund.de \
    --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

all inboxes | Powered by JetHome®