From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 10/18] gfs2: Provide config option for enabling trace points
Date: Tue, 23 Mar 2010 12:01:07 +0000 [thread overview]
Message-ID: <1269345667.2438.12.camel@localhost> (raw)
In-Reply-To: <1269304340-25372-11-git-send-email-jack@suse.cz>
Hi,
Now in the GFS2 -nmw git tree. Thanks,
Steve.
On Tue, 2010-03-23 at 01:32 +0100, Jan Kara wrote:
> CC: cluster-devel at redhat.com
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/gfs2/Kconfig | 8 ++++++++
> fs/gfs2/trace_gfs2.h | 2 ++
> 2 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/fs/gfs2/Kconfig b/fs/gfs2/Kconfig
> index 4dcddf8..872ced2 100644
> --- a/fs/gfs2/Kconfig
> +++ b/fs/gfs2/Kconfig
> @@ -38,3 +38,11 @@ config GFS2_FS_LOCKING_DLM
> Most users of GFS2 will require this. It provides the locking
> interface between GFS2 and the DLM, which is required to use GFS2
> in a cluster environment.
> +
> +config GFS2_TRACER
> + bool "GFS2 tracing"
> + depends on GFS2_FS && EVENT_TRACING
> + help
> + Provide trace points in block allocation functions, locking, and
> + journaling code.
> +
> diff --git a/fs/gfs2/trace_gfs2.h b/fs/gfs2/trace_gfs2.h
> index 148d55c..5f4faf3 100644
> --- a/fs/gfs2/trace_gfs2.h
> +++ b/fs/gfs2/trace_gfs2.h
> @@ -1,5 +1,7 @@
> #undef TRACE_SYSTEM
> +#undef TRACE_CONFIG
> #define TRACE_SYSTEM gfs2
> +#define TRACE_CONFIG CONFIG_GFS2_TRACER
>
> #if !defined(_TRACE_GFS2_H) || defined(TRACE_HEADER_MULTI_READ)
> #define _TRACE_GFS2_H
next prev parent reply other threads:[~2010-03-23 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1269304340-25372-1-git-send-email-jack@suse.cz>
2010-03-23 0:32 ` [Cluster-devel] [PATCH 10/18] gfs2: Provide config option for enabling trace points Jan Kara
2010-03-23 12:01 ` Steven Whitehouse [this message]
[not found] ` <1269388565.5363.380.camel@localhost>
2010-03-24 11:20 ` Steven Whitehouse
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=1269345667.2438.12.camel@localhost \
--to=swhiteho@redhat.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