public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "SystemTap" <systemtap@sources.redhat.com>
Subject: Stress testing - all functions
Date: Sat, 01 Apr 2006 01:39:00 -0000	[thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC06D3C343@scsmsx403.amr.corp.intel.com> (raw)

I just added a new stress test that tries to run probes on all kernel
functions that start with the same letter.  The test script is in:
    tests/testsuite/systemtap.stress/all_kernel_functions.stp

As you might expect this does cause problems, so what I checked into CVS
is disabled with an 'if 0'.  Just change it to 'if 1' if you want to try
it.  Here are my initial test results:

a*: ERROR: probe 1 registration failed, rc=1,
kernel.function("acpi_cpufreq_exit@arch/i386/kernel/cpu/cpufreq/acpi.c:5
27")

b*: OK!

c*: probe 1 registration failed, rc=1,
kernel.function("centrino_exit@arch/i386/kernel/cpu/cpufreq/speedstep-ce
ntrino.c:692")

d*: system reboots - there was no OOPS or BUG or anything printed to the
console.


So d* was as far as I got - later I will try removing d to see what else
fails.  And of course, just because b* passed this test doesn't mean
that all b* functions are necessarily safe.

The two that failed in a* and c* are both functions that are decorated
with __exit.  Perhaps the translator needs to disallow __exit functions,
just as it disallows __init?


Josh

             reply	other threads:[~2006-04-01  1:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-01  1:39 Stone, Joshua I [this message]
2006-04-01  2:44 ` Frank Ch. Eigler
2006-04-03 19:21 Stone, Joshua I

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=CBDB88BFD06F7F408399DBCF8776B3DC06D3C343@scsmsx403.amr.corp.intel.com \
    --to=joshua.i.stone@intel.com \
    --cc=systemtap@sources.redhat.com \
    /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).