From: Arnd Bergmann <arnd@arndb.de>
To: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, ltp-coverage@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
Peter Oberparleiter <oberparleiter@googlemail.com>
Subject: Re: [PATCH 5/7] gcov: add gcov profiling infrastructure
Date: Fri, 23 May 2008 11:29:53 +0200 [thread overview]
Message-ID: <200805231129.54027.arnd@arndb.de> (raw)
In-Reply-To: <48313DE6.30802@de.ibm.com>
On Monday 19 May 2008, Peter Oberparleiter wrote:
> From: Peter Oberparleiter <peter.oberparleiter@de.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 <><
prev parent reply other threads:[~2008-05-23 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 8:44 [PATCH 5/7] gcov: add gcov profiling infrastructure Peter Oberparleiter
2008-05-23 7:11 ` Andrew Morton
2008-05-23 8:45 ` Ralf Baechle
2008-05-27 8:41 ` Peter Oberparleiter
2008-05-23 9:29 ` Arnd Bergmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200805231129.54027.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-coverage@lists.sourceforge.net \
--cc=oberparleiter@googlemail.com \
--cc=peter.oberparleiter@de.ibm.com \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox