From: Ingo Molnar <mingo@kernel.org>
To: Dave Hansen <dave@sr71.net>
Cc: a.p.zijlstra@chello.nl, mingo@redhat.com, paulus@samba.org,
acme@ghostprotocols.net, tglx@linutronix.de, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [v3][PATCH 2/4] x86: warn when NMI handlers take large amounts of time
Date: Thu, 30 May 2013 10:33:15 +0200 [thread overview]
Message-ID: <20130530083315.GA14913@gmail.com> (raw)
In-Reply-To: <20130529222759.6D8C68B2@viggo.jf.intel.com>
* Dave Hansen <dave@sr71.net> wrote:
> @@ -96,8 +106,24 @@ static int __kprobes nmi_handle(unsigned
> * can be latched at any given time. Walk the whole list
> * to handle those situations.
> */
> - list_for_each_entry_rcu(a, &desc->head, list)
> + list_for_each_entry_rcu(a, &desc->head, list) {
> + u64 before, delta, whole_msecs;
> + int decimal_msecs;
> +
> + before = local_clock();
> handled += a->handler(type, regs);
> + delta = local_clock() - before;
> +
> + if (delta < nmi_longest_ns)
> + continue;
> +
> + nmi_longest_ns = delta;
> + whole_msecs = delta / (1000 * 1000);
> + decimal_msecs = (delta / 1000) % 1000;
> + printk_ratelimited(KERN_INFO
> + "INFO: NMI handler took too long to run: "
> + "%lld.%03d msecs\n", whole_msecs, decimal_msecs);
> + }
One more thing, would it make sense to print the symbol name of the
->handler here? That way the message would be more actionable:
INFO: NMI handler (nmi_handler_foo) took too long to run: 12.613 msecs
(Note, printk() has a '%ps' format string extension to print function
pointer symbolic names, so it's easy to add.)
Thanks,
Ingo
next prev parent reply other threads:[~2013-05-30 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 22:27 [v3][PATCH 0/4] Work around perf NMI-induced hangs Dave Hansen
2013-05-29 22:27 ` [v3][PATCH 1/4] perf/x86: only print PMU state when also WARN()'ing Dave Hansen
2013-05-29 22:27 ` [v3][PATCH 2/4] x86: warn when NMI handlers take large amounts of time Dave Hansen
2013-05-30 8:33 ` Ingo Molnar [this message]
2013-05-30 9:37 ` Peter Zijlstra
2013-05-29 22:28 ` [v3][PATCH 3/4] perf: drop sample rate when sampling is too slow Dave Hansen
2013-05-29 22:28 ` [v3][PATCH 4/4] x86: nmi length tracepoints Dave Hansen
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=20130530083315.GA14913@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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