From: Jon Masters <jonathan@jonmasters.org>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@elte.hu,
rostedt@goodmis.org
Subject: Re: [RFC PATCH 1/1] smi_detector: A System Management Interrupt detector
Date: Tue, 02 Jun 2009 16:32:31 -0400 [thread overview]
Message-ID: <1243974751.31439.62.camel@localhost.localdomain> (raw)
In-Reply-To: <20090602183231.GA13213@linux.vnet.ibm.com>
On Tue, 2009-06-02 at 11:32 -0700, Paul E. McKenney wrote:
> On Sun, May 31, 2009 at 12:31:18PM -0400, Jon Masters wrote:
> > This patch introduces a new SMI (System Management Interrupt) detector module
> > that can be used to detect high latencies within the system. It was originally
> > written for use in the RT kernel, but has wider applications.
>
> This would have been extremely handy a few years back when we were
> chasing some latency issues!!! ;-)
Thanks. One guy on IRC already asked why it didn't find all his SMIs.
I'll add to the docs that this can obviously only detect when it's
sampling - since we can't constantly sample without "locking up" the
machine, it's a tradeoff. The defaults are intended so you could put
them on a laptop and not notice - in practice, I've been running with 1
second window size and .5 second sample width - i.e. very meaty and
highly disruptive, but great at catching the little so and sos :)
> I don't see how this handles CPU hotplug operations (see interspersed),
> but I am OK with "don't do CPU-hotplug operations while running this
> test."
It doesn't, good catch. Though in fairness, I don't think that's big
issue - but having said that, the ring_buffer handles cpu hotplug nicely
and I just need to think a bit harder, so I'll possibly do that in my
next v3 posting...gonna go get that one ready now.
Thanks guys,
Jon.
prev parent reply other threads:[~2009-06-02 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-31 16:31 [RFC PATCH 0/1] SMI Detector (v2) Jon Masters
2009-05-31 16:31 ` [RFC PATCH 1/1] smi_detector: A System Management Interrupt detector Jon Masters
2009-06-02 3:57 ` Andrew Morton
2009-06-02 7:54 ` Ingo Molnar
2009-06-02 13:41 ` Jon Masters
2009-06-09 21:50 ` Jon Masters
2009-06-09 21:56 ` Andrew Morton
2009-06-09 22:53 ` Jon Masters
2009-06-02 18:32 ` Paul E. McKenney
2009-06-02 20:32 ` Jon Masters [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=1243974751.31439.62.camel@localhost.localdomain \
--to=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.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