From: fche@redhat.com (Frank Ch. Eigler)
To: "Stone, Joshua I" <joshua.i.stone@intel.com>
Cc: systemtap@sources.redhat.com
Subject: Re: Stress testing - all functions
Date: Sat, 01 Apr 2006 02:44:00 -0000 [thread overview]
Message-ID: <y0mk6aaypy8.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <CBDB88BFD06F7F408399DBCF8776B3DC06D3C343@scsmsx403.amr.corp.intel.com>
joshua.i.stone wrote:
> 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
Good stuff.
> [...]
> d*: system reboots - there was no OOPS or BUG or anything printed to the
> console.
Given time, one can try d[a-m]* and d[n-z]* to recursively subdivide
the namespace. It would be great if this were done automatically. (A
full search would of course take lots of time due to reboots.)
> 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?
That's right, for routines that are linked into vmlinux (not in a
module).
- FChE
next prev parent reply other threads:[~2006-04-01 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 1:39 Stone, Joshua I
2006-04-01 2:44 ` Frank Ch. Eigler [this message]
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=y0mk6aaypy8.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=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).