| 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
| ||
|
Message-Id: <200805231129.54027.arnd@arndb.de> Date: Fri, 23 May 2008 11:29:53 +0200 From: Arnd Bergmann <arnd@...db.de> To: Peter Oberparleiter <peter.oberparleiter@...ibm.com> Cc: linux-kernel@...r.kernel.org, ltp-coverage@...ts.sourceforge.net, Andrew Morton <akpm@...ux-foundation.org>, Sam Ravnborg <sam@...nborg.org>, Peter Oberparleiter <oberparleiter@...glemail.com> Subject: Re: [PATCH 5/7] gcov: add gcov profiling infrastructure On Monday 19 May 2008, Peter Oberparleiter wrote: > From: Peter Oberparleiter <peter.oberparleiter@...ibm.com> > > gcov profiling infrastructure: > > * change kbuild to include profiling flags > * provide functions needed by profiling code > * present profiling data as files in debugfs Good stuff, thanks for finally pushing this upstream! Regarding the use of debugfs, have you considered making your own file system independent of that? Currently, you'd need a lot of boilerplate code (basically a copy of debugs/inode.c), but I think it'd be appropriate since you're adding more than just a few simple files in debugfs. Maybe we can talk next monday when I'm in the office, because some time ago, I have already started a patch set that would make it trivial to add a new debugfs-like file system. Arnd <>< -- 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