From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13479] New: ARM tapset/scheduler.stp refers to kernel.function("__switch_to")
Date: Wed, 07 Dec 2011 15:28:00 -0000 [thread overview]
Message-ID: <bug-13479-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13479
Bug #: 13479
Summary: ARM tapset/scheduler.stp refers to
kernel.function("__switch_to")
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap@sourceware.org
ReportedBy: mjw@redhat.com
Classification: Unclassified
kernel.function("__switch_to") doesn't seem to exist on ARM, but gets selected
in tapset/scheduler.stp because of:
probe __scheduler.ctxswitch.kp =
%( arch != "x86_64" && arch != "ia64" %?
kernel.function("__switch_to")
%:
kernel.function("context_switch")
%)
Running /root/systemtap/testsuite/buildok/scheduler-ctxswitch.stp
starting /root/systemtap/testsuite/buildok/scheduler-ctxswitch.stp
spawn1 stap -p4 /root/systemtap/testsuite/buildok/scheduler-ctxswitch.stp
spawn stap -p4 /root/systemtap/testsuite/buildok/scheduler-ctxswitch.stp
semantic error: no match while resolving probe point
kernel.function("__switch_to")
semantic error: no match while resolving probe point
kernel.function("__switch_to")
semantic error: no match while resolving probe point __scheduler.ctxswitch.kp
semantic error: no match while resolving probe point __scheduler.ctxswitch.kp
Pass 2: analysis failed. Try again with another '--vp 01' option.
Pass 2: analysis failed. Try again with another '--vp 01' option.
wait results: 1471 exp16 0 1
KFAIL: buildok/scheduler-ctxswitch.stp (PRMS: GCC)
Hmmmm, that isn't really a KFAIL...
But the same is true for:
Running /root/systemtap/testsuite/systemtap.stress/current.exp ...
executing: stap -v -g /root/systemtap/testsuite/systemtap.stress/current.stp
spawn stap -v -g /root/systemtap/testsuite/systemtap.stress/current.stp
Pass 1: parsed user script and 75 library script(s) using
16592virt/12656res/161
6shr kb, in 710usr/10sys/717real ms.
semantic error: no match while resolving probe point
kernel.function("__switch_to").callFAIL: systemtap.stress/current.stp
compilation
testcase /root/systemtap/testsuite/systemtap.stress/current.exp completed in 3
seconds
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-12-07 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 15:28 mjw at redhat dot com [this message]
2011-12-07 15:59 ` [Bug tapsets/13479] " dsmith at redhat dot com
2011-12-17 2:14 ` mjw at redhat dot com
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=bug-13479-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).