All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Zhaolei <zhaolei@cn.fujitsu.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Tom Zanussi <tzanussi@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tracing, boottrace: Move include/trace/boot.h to include/linux/boottrace.h
Date: Mon, 13 Apr 2009 16:25:34 +0200	[thread overview]
Message-ID: <20090413142531.GC5977@nowhere> (raw)
In-Reply-To: <49E2B763.8060706@cn.fujitsu.com>

On Mon, Apr 13, 2009 at 11:54:11AM +0800, Zhaolei wrote:
> Impact: refactor code, no functionality changed
> 
> Files in include/trace/ should be definition of tracepoints, and header
> file for boot trace should put to include/linux/.
> 
> Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> ---



Until now I had the opinion that it's good to let every tracing headers
to be placed in include/trace/* because they are not useful for anything
else than the tracer itself so that we don't encumber include/linux for
private things.

So that we have both tracepoints/trace_events plus the low-level tracers
headers in include/trace/*

I'm not opposite to this change, but seeing this patch and the recent divide
of kmemtrace headers, I would like to know the opinion of Ingo and Steven
about the strict role of include/trace/*
Is it only for tracepoints-like bits, or oslo intended for every private tracing
purposes?


Thanks.


>  include/{trace/boot.h => linux/boottrace.h} |    0 
>  init/main.c                                 |    2 +-
>  kernel/trace/trace.h                        |    2 +-
>  3 files changed, 2 insertions(+), 2 deletions(-)
>  rename include/{trace/boot.h => linux/boottrace.h} (100%)
> 
> diff --git a/include/trace/boot.h b/include/linux/boottrace.h
> similarity index 100%
> rename from include/trace/boot.h
> rename to include/linux/boottrace.h
> diff --git a/init/main.c b/init/main.c
> index 694a563..d7d4741 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -66,7 +66,7 @@
>  #include <linux/ftrace.h>
>  #include <linux/async.h>
>  #include <linux/kmemtrace.h>
> -#include <trace/boot.h>
> +#include <linux/boottrace.h>
>  
>  #include <asm/io.h>
>  #include <asm/bugs.h>
> diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
> index ce6bdc4..5b654ce 100644
> --- a/kernel/trace/trace.h
> +++ b/kernel/trace/trace.h
> @@ -8,7 +8,7 @@
>  #include <linux/ring_buffer.h>
>  #include <linux/mmiotrace.h>
>  #include <linux/ftrace.h>
> -#include <trace/boot.h>
> +#include <linux/boottrace.h>
>  #include <linux/kmemtrace.h>
>  #include <trace/power.h>
>  
> -- 
> 1.5.5.3
> 
> 


  parent reply	other threads:[~2009-04-13 14:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13  3:54 [PATCH 1/2] tracing, boottrace: Move include/trace/boot.h to include/linux/boottrace.h Zhaolei
2009-04-13  3:55 ` [PATCH 2/2] tracing, syscalltrace: Move include/trace/syscall.h to include/linux/syscalltrace.h Zhaolei
2009-04-13 14:28   ` Frederic Weisbecker
2009-04-13 14:25 ` Frederic Weisbecker [this message]
2009-04-13 22:24   ` [PATCH 1/2] tracing, boottrace: Move include/trace/boot.h to include/linux/boottrace.h Ingo Molnar
2009-04-13 23:11     ` Steven Rostedt
2009-04-13 23:28       ` Ingo Molnar
2009-04-13 23:34         ` Steven Rostedt
2009-04-13 23:40           ` Ingo Molnar
2009-04-13 23:51             ` Steven Rostedt
2009-04-13 23:53               ` Ingo Molnar

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=20090413142531.GC5977@nowhere \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tzanussi@gmail.com \
    --cc=zhaolei@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.