Re: [Cluster-devel] [PATCH 10/18] gfs2: Provide config option forenabling trace points

[Steven Rostedt]

On Tue, 2010-03-23 at 12:01 +0000, Steven Whitehouse wrote:
> Hi,
> 
> Now in the GFS2 -nmw git tree. Thanks,
> 

Note, this depends on patch 1 which we have not yet determined if it
should be applied or not.

-- Steve

> Steve.
> 
> On Tue, 2010-03-23 at 01:32 +0100, Jan Kara wrote:
> > CC: cluster-devel@xxxxxxxxxx
> > Signed-off-by: Jan Kara <jack@xxxxxxx>
> > ---
> >  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
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/