From: Alexander Holler <holler@ahsoftware.de>
To: linux-kernel@vger.kernel.org
Subject: work unwinding?
Date: Tue, 11 Feb 2014 16:30:02 +0100 [thread overview]
Message-ID: <52FA41FA.6030908@ahsoftware.de> (raw)
Hello,
Since the kernel has become more RT-aware and many stuff has moved into
works, dump_stack() has often become a bit useless, because it just
shows the call stack of a work, which quiet often is a bit short and
doesn't reveal the real source of a problem.
At least I would like it if there would be some mechanism to record the
call stack for works, so that dump_stack() could display what actually
queued a work (and it's call stack).
Not that I want to implement such, I'm just curious if someone already
has thought about implementing something like that, which I'm calling
here "work unwinding" ;)
Regards,
Alexander Holler
reply other threads:[~2014-02-11 15:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52FA41FA.6030908@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.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.