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: Sat, 8 Sep 2007 13:11:23 +0100 From: Christoph Hellwig <hch@...radead.org> To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [patch 6/6] Linux Kernel Markers - Port SPU to markers On Thu, Sep 06, 2007 at 04:07:39PM -0400, Mathieu Desnoyers wrote: > Andrew, any chance to get this into -mm ASAP so we can have it in > 2.6.24? > > Just in case anyone wonders what this is usefulfor I've ported my > hacking spu tracing code to it, and if markers get in I'd push a cleaned > up version of this in the tree of the benefit of everyone trying to > follow what's going on in the spufs code. Similarly I'd like to port > the xfs tracing code over to it which is very helpful in trying to > debug filesystem issues. > > Note that in this patch the actual logging code is rather nasty > hand-crafted code lifted from the tcp probe in tree which would benefit > of going away in favour of more general tracing code aswell. > > Changelog: > - Porting to 2.6.23-rc4-mm1 gave a reject (a trace point location disappeared) > from spufs_ps_nopfn() : spufs_ps_nopfn__sleep and spufs_ps_nopfn__wake. The subject is rather confusing. What I ported to markers is the spu _tracing_ support. And given it's never been public before adding the port part to the commit doesn't make much sense. Nevermind, I have updated version of this and would prefer to submit it myself through the spufs maintainer once markers make mainline (hopefully soon!) I'll also need more cleanups like adding a config option for it. - 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