| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 09 Aug 2006 20:10:48 +0200 From: Jes Sorensen <jes@....com> To: "Luck, Tony" <tony.luck@...el.com> Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org Subject: Re: How to lock current->signal->tty Luck, Tony wrote: > On Wed, Aug 09, 2006 at 11:44:10AM +0100, Alan Cox wrote: >> Jes, read up on kprobes a little if you think its of no use in these >> kind of situations. A systemtap script to count/measure alignment fault >> rates and see who is causing the load isn't very hard to write. > > But this does make sense ... the system administrator of a mainframe or > super-computer can (and arguably should) be monitoring resource > utilization and providing feedback to users on how to get the best > performance from their applications. Actually perfmon would probably be better suited for this on ia64 than kprobes/systemtap. You can do it on hackish way with a [jk]probe, but it isn't going to be all that pretty. > -Tony (currently at 90% rip out this message, 10% add the mutex lock/unlock). Nuke it! Jes - 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