public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jason Baron <jbaron@redhat.com>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org, jistone@redhat.com
Subject: Re: [PATCH] export softirq_to_name symbol
Date: Sun, 3 May 2009 10:33:28 +0200	[thread overview]
Message-ID: <20090503083328.GC27707@elte.hu> (raw)
In-Reply-To: <20090501193022.GB3111@redhat.com>


* Jason Baron <jbaron@redhat.com> wrote:

> hi,
> 
> In response to a user request:
> 
> Export 'softirq_to_name' so that modules using the softirq 
> tracepoints can resolve the # to a name.
> 
> Signed-off-by: Jason Baron <jbaron@redhat.com>
> ---
>  kernel/softirq.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/softirq.c b/kernel/softirq.c
> index b76064b..1841ab7 100644
> --- a/kernel/softirq.c
> +++ b/kernel/softirq.c
> @@ -60,6 +60,7 @@ char *softirq_to_name[NR_SOFTIRQS] = {
>  	"HI", "TIMER", "NET_TX", "NET_RX", "BLOCK",
>  	"TASKLET", "SCHED", "HRTIMER",	"RCU"
>  };
> +EXPORT_SYMBOL_GPL(softirq_to_name);

Hm, that very much looks like as if someone was writing kernel 
tracing code without the intention to submitting it upstream. Not 
having exported that symbol is thus a subtle "dont do that please" 
warning sign ;-)

	Ingo

      parent reply	other threads:[~2009-05-03  8:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 19:30 [PATCH] export softirq_to_name symbol Jason Baron
2009-05-01 19:50 ` Christoph Hellwig
2009-05-01 20:07   ` Josh Stone
2009-05-01 20:10     ` Christoph Hellwig
2009-05-01 20:17       ` Josh Stone
2009-05-01 20:22         ` Christoph Hellwig
2009-05-01 21:25           ` Josh Stone
2009-05-03 18:36       ` Frederic Weisbecker
2009-05-03  8:33 ` Ingo Molnar [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=20090503083328.GC27707@elte.hu \
    --to=mingo@elte.hu \
    --cc=jbaron@redhat.com \
    --cc=jistone@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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