Date: Sun, 25 Jan 2009 14:52:05 -0800
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
Message-ID: <20090125225205.GA3783@monkey.beaverton.ibm.com>
References: <1232751312.3990.59.camel@perihelion.bos.jonmasters.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1232751312.3990.59.camel@perihelion.bos.jonmasters.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 972
Lines: 22

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/