From: Mel Gorman <mgorman@suse.de>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
SystemTap <systemtap@sourceware.org>
Subject: systemtap broken by removal of register_timer_hook
Date: Wed, 3 Apr 2013 08:50:17 +0100 [thread overview]
Message-ID: <20130403075017.GA2534@suse.de> (raw)
Commit ba6fdda4 (profiling: Remove unused timer hook) removed
[un]register_timer_hook due to a lack of upstream users and a belief
that there were no out-of-tree users. However, systemtap uses it and
with that patch applied, some stap scripts fail with
WARNING: "unregister_timer_hook" [/tmp/stapJoLMxD/stap_de6e19eaf7bd94629aba9d6f56cdfca5_8156.ko] undefined!
WARNING: "register_timer_hook" [/tmp/stapJoLMxD/stap_de6e19eaf7bd94629aba9d6f56cdfca5_8156.ko] undefined!
Error inserting module '/tmp/stapJoLMxD/stap_de6e19eaf7bd94629aba9d6f56cdfca5_8156.ko': Unknown symbol in module
WARNING: /usr/bin/staprun exited with status: 1
Pass 5: run failed. Try again with another '--vp 00001' option.
Unexpected exit of STAP script at ./watch-dstate.pl line 305.
Can the patch be reverted or at least put a warning in place about it
being obsoleted until the systemtap folks come up with a replacement?
Systemtap folk, has his problem already been addressed?
--
Mel Gorman
SUSE Labs
next reply other threads:[~2013-04-03 7:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 7:50 Mel Gorman [this message]
2013-04-03 11:01 ` systemtap broken by removal of register_timer_hook Frederic Weisbecker
[not found] ` <CAFTL4hyYezB2ZxM-GJ70VoxOeRSG64V6u+nX2hTuhF30R-GdPg__32168.962484184$1364986928$gmane$org@mail.gmail.com>
2013-04-03 12:29 ` Frank Ch. Eigler
2013-04-03 12:49 ` Frederic Weisbecker
2013-04-03 14:44 ` Frank Ch. Eigler
2013-04-03 18:38 ` Josh Stone
2013-04-04 12:46 ` Frederic Weisbecker
2013-04-19 14:46 ` Frank Ch. Eigler
2013-04-30 0:19 ` Frederic Weisbecker
2013-04-30 17:27 ` Frank Ch. Eigler
2013-05-06 23:12 ` Frederic Weisbecker
2013-04-10 11:24 ` Ingo Molnar
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=20130403075017.GA2534@suse.de \
--to=mgorman@suse.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=systemtap@sourceware.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.