From: Christoph Hellwig <hch@infradead.org>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH, RFC 2/2] ext4: Convert instrumentation from markers to tracepoints
Date: Mon, 13 Apr 2009 06:14:56 -0400 [thread overview]
Message-ID: <20090413101456.GA4716@infradead.org> (raw)
In-Reply-To: <20090413065910.GA23795@skywalker>
On Mon, Apr 13, 2009 at 12:29:10PM +0530, Aneesh Kumar K.V wrote:
> We moved all the ext4 headers to fs/ext4/ Can this be
> fs/ext4/ext4_trace_types.h ?
With the current event tracer in mainline those files get included
into kernel/trace/events.o so it is required to be global. Steve
has some patches in his queue to allow TRACE_EVENT to work in
modules which losens that requirement. Last time I talked to him
he still wants to have the headers in include/trace/ as a policy
but I hope we can get away from that.
prev parent reply other threads:[~2009-04-13 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 19:46 [PATCH, RFC 1/2] jbd2: Convert instrumentation from markers to tracepoints Theodore Ts'o
2009-04-11 19:46 ` [PATCH, RFC 2/2] ext4: " Theodore Ts'o
2009-04-13 6:59 ` Aneesh Kumar K.V
2009-04-13 10:14 ` Christoph Hellwig [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=20090413101456.GA4716@infradead.org \
--to=hch@infradead.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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