* work unwinding?
@ 2014-02-11 15:30 Alexander Holler
0 siblings, 0 replies; only message in thread
From: Alexander Holler @ 2014-02-11 15:30 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-02-11 15:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-11 15:30 work unwinding? Alexander Holler
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.