From: Mike Kravetz <kravetz@us.ibm.com>
To: Jon Masters <jcm@redhat.com>
Cc: linux-rt-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
williams <williams@redhat.com>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Subject: Re: [RT] [RFC] simple SMI detector
Date: Sun, 25 Jan 2009 14:52:05 -0800 [thread overview]
Message-ID: <20090125225205.GA3783@monkey.beaverton.ibm.com> (raw)
In-Reply-To: <1232751312.3990.59.camel@perihelion.bos.jonmasters.org>
On Fri, Jan 23, 2009 at 05:55:12PM -0500, Jon Masters wrote:
> This patch adds the module smi_detector under drivers/misc
>
> Code from Jon Masters with small changes from Luis Goncalves and
> documentation from Clark Williams.
Good work Jon. I think something like this will be helpful.
Any reason why you could not do SMI detection in user level code running
at the highest RT priority? If something is running at the highest RT
priority, it should not be preempted by anything. Right? In the past,
we discoved discovered periodic SMIs on some hardware platforms by running
a user level process in an infinite loop sampling the clock and reporting
unexpected delays. Of course, this does hog an entire CPU.
--
Mike
next prev parent reply other threads:[~2009-01-25 22:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 22:55 [RT] [RFC] simple SMI detector Jon Masters
2009-01-24 2:33 ` Lee Revell
2009-01-24 16:30 ` Thomas Gleixner
2009-01-25 0:57 ` Jon Masters
2009-01-25 2:12 ` Sven-Thorsten Dietrich
2009-01-25 4:02 ` Theodore Tso
2009-01-25 9:40 ` Thomas Gleixner
2009-01-25 11:49 ` Bastien ROUCARIES
2009-01-25 15:04 ` Clark Williams
2009-01-25 21:41 ` Jon Masters
2009-01-25 21:38 ` Jon Masters
2009-01-25 9:34 ` Thomas Gleixner
2009-01-25 14:07 ` Henrique de Moraes Holschuh
2009-01-25 22:52 ` Mike Kravetz [this message]
2009-01-26 17:51 ` Jon Masters
2009-01-27 2:23 ` Lee Revell
2009-01-27 2:48 ` Keith Mannthey
2009-01-27 11:22 ` Pavel Machek
2009-01-27 15:17 ` Jon Masters
2009-01-27 18:00 ` Len Brown
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=20090125225205.GA3783@monkey.beaverton.ibm.com \
--to=kravetz@us.ibm.com \
--cc=jcm@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.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