From: Yanmin Zhang <yanmin_zhang@linux.intel.com>
To: Chuansheng Liu <chuansheng.liu@intel.com>
Cc: tglx@linutronix.de, mingo@kernel.org, a.p.zijlstra@chello.nl,
linux-kernel@vger.kernel.org, fei.li@intel.com
Subject: Re: [PATCH V2] hrtimer: Printing timer info when hitting BUG_ON()
Date: Tue, 06 Nov 2012 09:07:27 +0800 [thread overview]
Message-ID: <1352164047.17919.1.camel@ymzhang.sh.intel.com> (raw)
In-Reply-To: <1351592820.15558.1450.camel@cliu38-desktop-build>
On Tue, 2012-10-30 at 18:27 +0800, Chuansheng Liu wrote:
> We encounted one BUG_ON() issue at function __run_hrtimer(),
> but the panic info is not enough to find out which hrtimer
> users use the hrtimer wrongly.
> (in this BUG_ON case, it is callback running at the same time
> hrtimer_start() is executed on different context.)
>
> We can print basic timer info before BUG(), it is easy to find
> out which hrtimer user has fault, the output info is like below:
>
> <3>[ 41.118552] timer info: state/3, func/test_timer_cb
> <3>[ 41.118618] timer stats: pid/786(sh), site/hrtimer_start
> <0>[ 41.118670] ------------[ cut here ]------------
> <2>[ 41.118691] kernel BUG at /root/r4_code/hardware/intel/linux-2.6/kernel/hrtimer.c:1260!
> <0>[ 41.118715] invalid opcode: 0000 [#1] PREEMPT SMP
>
> The infos of callback/state are very helpful for debugging this BUG_ON().
It's a useful patch.
Thomas,
Could you merge it into your testing tree, so other developers could also
benefit from it?
Thanks all.
Yanmin
>
> Signed-off-by: Li Fei <fei.li@intel.com>
> Signed-off-by: liu chuansheng <chuansheng.liu@intel.com>
> ---
> kernel/hrtimer.c | 21 ++++++++++++++++++++-
> 1 files changed, 20 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
> index 6db7a5e..0618eaf 100644
> --- a/kernel/hrtimer.c
> +++ b/kernel/hrtimer.c
> @@ -1204,6 +1204,22 @@ int hrtimer_get_res(const clockid_t which_clock, struct timespec *tp)
> }
> EXPORT_SYMBOL_GPL(hrtimer_get_res);
>
> +/*
> + * dump_hrtimer_callinfo - print hrtimer information including:
> + * state, callback function, pid and start_site.
> +*/
> +static void dump_hrtimer_callinfo(struct hrtimer *timer)
> +{
> +
> + pr_err("timer info: state/%lx, func/%pf\n",
> + timer->state, timer->function);
> +
> +#ifdef CONFIG_TIMER_STATS
> + pr_err("timer stats: pid/%d(%s), site/%pf\n",
> + timer->start_pid, timer->start_comm, timer->start_site);
> +#endif
> +}
> +
> static void __run_hrtimer(struct hrtimer *timer, ktime_t *now)
> {
> struct hrtimer_clock_base *base = timer->base;
> @@ -1235,7 +1251,10 @@ static void __run_hrtimer(struct hrtimer *timer, ktime_t *now)
> * hrtimer_start_range_ns() or in hrtimer_interrupt()
> */
> if (restart != HRTIMER_NORESTART) {
> - BUG_ON(timer->state != HRTIMER_STATE_CALLBACK);
> + if (timer->state != HRTIMER_STATE_CALLBACK) {
> + dump_hrtimer_callinfo(timer);
> + BUG();
> + }
> enqueue_hrtimer(timer, base);
> }
>
prev parent reply other threads:[~2012-11-06 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 10:27 Chuansheng Liu
2012-11-06 1:07 ` Yanmin Zhang [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=1352164047.17919.1.camel@ymzhang.sh.intel.com \
--to=yanmin_zhang@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=chuansheng.liu@intel.com \
--cc=fei.li@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®