lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 19 Jan 2008 14:40:11 -0500 From: fche@...hat.com (Frank Ch. Eigler) To: Arjan van de Ven <arjan@...ux.intel.com> Cc: =?ISO-8859-1?Q?T=F6r=F6k_Edwin?= <edwintorok@...il.com>, Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] LatencyTop: make reason (blk_execute_rq+0x7a/0xd) known Arjan van de Ven <arjan@...ux.intel.com> 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 majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists