All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jon Masters <jonathan@jonmasters.org>,
	linux-kernel@vger.kernel.org, jcm@redhat.com, tglx@linutronix.de,
	rostedt@goodmis.org
Subject: Re: [RFC PATCH 1/1] smi_detector: A System Management Interrupt detector
Date: Tue, 2 Jun 2009 09:54:50 +0200	[thread overview]
Message-ID: <20090602075450.GA12411@elte.hu> (raw)
In-Reply-To: <20090601205720.825d3048.akpm@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> On Sun, 31 May 2009 12:31:18 -0400 Jon Masters <jonathan@jonmasters.org> 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.
> > 
> 
> Neat-looking code.
> 
> AFACIT it can be used on any platform.  Suppose that powerpcs or ia64s
> also mysteriously go to lunch like PC's do - I think the code will work
> for them too?  In which case the "smi" name is excessively specific. 
> Not a big deal though.

Yes, i wondered about that too - this is really a generic method 
that detects and measures hardware latencies.

Many of the internal smi_ prefixes can go - such a prefix is really 
only needed within a .c module if the symbol is exported.

The rest (and the whole facility) could be renamed to hwlat_, 
hw_latency_ or so - prominently documenting that on x86 it can find 
SMI latencies, etc.?

	Ingo

  reply	other threads:[~2009-06-02  7:55 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 [this message]
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

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=20090602075450.GA12411@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=jcm@redhat.com \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.