Arjan van de Ven <[EMAIL PROTECTED]> writes: > Török Edwin wrote: >> [...] >> P.S.: LatencyTop could have a feature to ask for more details on unknown >> latency reasons, and it would generate a systemtap script itself, that >> would show the backtraces to help figure out whats going on. > > I've considered having an option inside the code itself that would print a > backtrace for, say, an unknown latency larger than 100msec > but the code got ugly (the accounting gets done in the scheduler path, > where you can't printk). [...]
Systemtap does not use printk, and can generate decent backtraces from the kernel (and into userspace before too long). (FWIW, it seems to be only a small stretch to implement tools like *top via systemtap rather than custom-written kernel code.) - FChE -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
