From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Jason Baron <jbaron@redhat.com>
Cc: mingo@elte.hu, rostedt@goodmis.org, linux-kernel@vger.kernel.org,
acme@ghostprotocols.net, fweisbec@gmail.com, fche@redhat.com,
peterz@infradead.org
Subject: Re: [Patch 1/2] tracepoints for softirq entry/exit - add softirq-to-name array
Date: Fri, 13 Mar 2009 22:53:21 -0400 [thread overview]
Message-ID: <20090314025321.GB22526@Krystal> (raw)
In-Reply-To: <20090312183336.GB3352@redhat.com>
* Jason Baron (jbaron@redhat.com) wrote:
>
> create a 'softirq_to_name' array, which is indexed by softirq #, so
> that we can easily convert between the softirq index # and its name, in
> order to get more meaningful output messages.
>
> Signed-off-by: Jason Baron <jbaron@redhat.com>
>
> ---
>
> include/linux/interrupt.h | 5 +++++
> kernel/softirq.c | 9 ++++++++-
> 2 files changed, 13 insertions(+), 1 deletions(-)
>
>
> diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h
> index e7bcfd7..da82ee4 100644
> --- a/include/linux/interrupt.h
> +++ b/include/linux/interrupt.h
> @@ -258,6 +258,11 @@ enum
> NR_SOFTIRQS
> };
>
> +/* map softirq index to softirq name. update 'softirq_to_name' in
> + * kernel/softirq.c when adding a new softirq.
> + */
> +extern char *softirq_to_name[NR_SOFTIRQS];
> +
> /* softirq mask and active fields moved to irq_cpustat_t in
> * asm/hardirq.h to get better cache usage. KAO
> */
> diff --git a/kernel/softirq.c b/kernel/softirq.c
> index 40ff3cf..ba1511f 100644
> --- a/kernel/softirq.c
> +++ b/kernel/softirq.c
> @@ -53,6 +53,12 @@ static struct softirq_action softirq_vec[NR_SOFTIRQS] __cacheline_aligned_in_smp
>
> static DEFINE_PER_CPU(struct task_struct *, ksoftirqd);
>
> +char *softirq_to_name[NR_SOFTIRQS] = {
> + "HI_SOFTIRQ", "TIMER_SOFTIRQ", "NET_TX_SOFTIRQ", "NET_RX_SOFTIRQ",
> + "BLOCK_SOFTIRQ", "TASKLET_SOFTIRQ", "SCHED_SOFTIRQ", "HRTIMER_SOFTIRQ",
> + "RCU_SOFTIRQ"
> +};
> +
Small nit :
this should be a const char *.
Besides that it looks good, and very useful to a tracer. We just have to
make sure this table can eventually be saved into a trace.
Mathieu
> /*
> * we cannot loop indefinitely here to avoid userspace starvation,
> * but we also don't want to introduce a worst case 1/HZ latency
> @@ -209,9 +215,10 @@ restart:
> h->action(h);
>
> if (unlikely(prev_count != preempt_count())) {
> - printk(KERN_ERR "huh, entered softirq %td %p"
> + printk(KERN_ERR "huh, entered softirq %td %s %p"
> "with preempt_count %08x,"
> " exited with %08x?\n", h - softirq_vec,
> + softirq_to_name[h - softirq_vec],
> h->action, prev_count, preempt_count());
> preempt_count() = prev_count;
> }
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-03-14 2:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 18:33 [Patch 1/2] tracepoints for softirq entry/exit - add softirq-to-name array Jason Baron
2009-03-12 18:45 ` Frederic Weisbecker
2009-03-12 22:44 ` Steven Rostedt
2009-03-13 4:02 ` [tip:tracing/ftrace] tracing: " Jason Baron
2009-03-14 2:53 ` Mathieu Desnoyers [this message]
2009-03-16 18:58 ` [Patch 1/2] " Jason Baron
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=20090314025321.GB22526@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=acme@ghostprotocols.net \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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