public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Sven-Thorsten Dietrich <sdietrich@novell.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Lee Revell <rlrevell@joe-job.com>,
	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 16:41:20 -0500	[thread overview]
Message-ID: <1232919680.1326.11.camel@jcmlaptop> (raw)
In-Reply-To: <20090125040246.GE9216@mit.edu>

On Sat, 2009-01-24 at 23:02 -0500, Theodore Tso wrote:

> I'm not sure exactly how one would do this certification, but I agree
> that some kind of "real-time ready" logo/certification program would
> make a huge amount of sense, with some standardized metrics of maximum
> time spent in an SMI routine, and under what circumstances (in some
> cases it occurs every 30-60 minutes; on other cases, only when the CPU
> is about to melt itself into slag, or when there are ECC errors, etc.)
> There is a huge difference between a system which stops the OS on all
> CPU's dead in its tracks for milliseconds once every 45 minutes,
> versus one which only triggers an SMI in extreme situations when the
> hardware is about to destroy itself.

I actually already talked to a certain industry group about a different
program but will mention this idea also - some kind of industry notion
of "real time platform" probably wouldn't be a bad idea. I'm not sure
what the vendors would say/think, but it's probably worth having the
discussion anyway. I think we're all right now having to do a lot of
legwork in testing/certifying that systems have acceptable latencies.

Jon.

  parent reply	other threads:[~2009-01-25 21:41 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 [this message]
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
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=1232919680.1326.11.camel@jcmlaptop \
    --to=jonathan@jonmasters.org \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=sdietrich@novell.com \
    --cc=tglx@linutronix.de \
    --cc=tytso@mit.edu \
    --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