From: "jcastillo at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/16493] New: Improve bkl.stp to add backtrace and timeout
Date: Wed, 22 Jan 2014 10:46:00 -0000 [thread overview]
Message-ID: <bug-16493-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16493
Bug ID: 16493
Summary: Improve bkl.stp to add backtrace and timeout
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: systemtap at sourceware dot org
Reporter: jcastillo at redhat dot com
Created attachment 7366
--> https://sourceware.org/bugzilla/attachment.cgi?id=7366&action=edit
Proposed patch
Hello,
Most of the times, when we use bkl.stp to investigate BKL issues, we've found
useful to have the backtrace of the function that holds the BKL.
The patch attached adds a new command line option, "backtrace=N", that when
used enables the use of print_backtrace(). The value of <N>, if present, is
taken as useconds, and it is the limit of time the task or tasks have been
waiting to acquire the lock i.e.:
# stap blk.stp backtrace=100
That would enable printing of backtrace on all tasks holding the kernel
big lock for more than 100us.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-01-22 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 10:46 jcastillo at redhat dot com [this message]
2014-01-24 8:58 ` [Bug testsuite/16493] Improve bkl.stp to add backtrace jcastillo at redhat dot com
2014-03-05 22:05 ` dsmith at redhat dot com
2015-08-24 19:49 ` flu 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-16493-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).