From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Reinhard.Tartler@informatik.uni-erlangen.de,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com, hch@infradead.org,
xfs-masters@oss.sgi.com,
Christoph Egger <siccegge@stud.informatik.uni-erlangen.de>
Subject: Re: Obsolete config in kernel build system (XFS_TRACE)
Date: Thu, 21 Jan 2010 07:19:04 -0500 [thread overview]
Message-ID: <20100121121904.GA1082@infradead.org> (raw)
In-Reply-To: <20100120224626.GP14035@discord.disaster>
On Thu, Jan 21, 2010 at 09:46:26AM +1100, Dave Chinner wrote:
> Christoph's conversion to use the kernel trace infrastructure is
> a work in progress. It's no small task - he's converted around 220
> trace points points so far.
>
> However, the btree tracing code has not been converted yet. IIRC
> this is because the kernel trace code didn't have the required
> infrastructure at the time of initial conversion. Hence the old code
> has not yet been completely removed because the conversion is not
> yet complete. It will go away when the conversion is completed.
The btree ones are rather difficult because it will require attaching
difference events to a single tracepoint and filter on which one
we want, so it may take a bit of time.
The existing xfs_btree_trace.c won't be much use for that and if we
really need it we can look at it in git history.
Christoph, can you send a properly signed off patch to kill
xfs_btree_trace.c and and the #ifdef XFS_BTREE_TRACE code in
xfs_btree_trace.h?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-01-21 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 12:52 Obsolete config in kernel build system (XFS_TRACE) Christoph Egger
2010-01-20 12:57 ` Robert P. J. Day
2010-01-20 22:46 ` Dave Chinner
2010-01-21 12:19 ` 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=20100121121904.GA1082@infradead.org \
--to=hch@infradead.org \
--cc=Reinhard.Tartler@informatik.uni-erlangen.de \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=siccegge@stud.informatik.uni-erlangen.de \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.com \
/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