The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Chuansheng Liu <chuansheng.liu@intel.com>
Cc: tglx@linutronix.de, mingo@kernel.org,
	linux-kernel@vger.kernel.org, fei.li@intel.com,
	yanmin_zhang@linux.intel.com
Subject: Re: [PATCH] hrtimer: Printing timer info when hitting BUG_ON()
Date: Mon, 29 Oct 2012 10:05:41 +0100	[thread overview]
Message-ID: <1351501541.24721.1.camel@twins> (raw)
In-Reply-To: <1351508551.15558.1428.camel@cliu38-desktop-build>

On Mon, 2012-10-29 at 19:02 +0800, Chuansheng Liu wrote:
> +/*
> + * dump_hrtimer_callinfo - print hrtimer information including:
> + * state, callback function, pid and start_site.
> +*/
> +static void dump_hrtimer_callinfo(struct hrtimer *timer)
> +{
> +
> +       char symname[KSYM_NAME_LEN];
> +
> +       if (lookup_symbol_name((unsigned long)(timer->function), symname) < 0) {
> +               pr_err("timer info: state/%lx, func/%pK\n",
> +                       timer->state, timer->function);
> +       } else {
> +               pr_err("timer info: state/%lx, func/%s",
> +                       timer->state, symname);
> +       }
> +
> +#ifdef CONFIG_TIMER_STATS
> +       if (lookup_symbol_name((unsigned long)(timer->start_site),
> +                                               symname) < 0) {
> +               pr_err("timer stats: pid/%d(%s), site/%pK\n",
> +                       timer->start_pid, timer->start_comm, timer->start_site);
> +       } else {
> +               pr_err("timer stats: pid/%d(%s), site/%s\n",
> +                       timer->start_pid, timer->start_comm, symname);
> +       }
> +#endif
> +} 

What's wrong with %pf ?

  reply	other threads:[~2012-10-29  9:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 11:02 [PATCH] hrtimer: Printing timer info when hitting BUG_ON() Chuansheng Liu
2012-10-29  9:05 ` Peter Zijlstra [this message]
2012-10-30  4:55   ` Liu, Chuansheng

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=1351501541.24721.1.camel@twins \
    --to=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 \
    --cc=yanmin_zhang@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox