public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Jon Masters <jcm@redhat.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: Sat, 24 Jan 2009 17:30:30 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.0901241716540.3424@localhost.localdomain> (raw)
In-Reply-To: <75b66ecd0901231833j2fda4554sb0f47457ab838566@mail.gmail.com>

On Fri, 23 Jan 2009, Lee Revell wrote:
> 
> FYI the RTAI project has a patch to allow disabling of SMI:
> 
> https://listas.upv.es/pipermail/rtlinuxgpl/2007-April/000609.html

FYI, this patch should be removed from the internet archives and the
author should be made liable for the damage which can happen when
innocent users try to use it for fixing things which simply can not be
fixed.

>> .... disabled SMIs with RTAI code the latencies of cyclictest were
>> good, but after about 20 minutes my system stopped working and now
>> it does not even boot anymore. :( Any hint?
>
> Yeah. Buy a new CPU. You deep-fried your P4 because you disabled the
> thermal protection.

Aside of this worst case scenario, disabling SMIs is problematic as
SMI is used to emulate devices, to fix chip bugs and necessary for
enhanced features.

The only reasonable thing you can do on a SMI plagued system is to
identify the device which makes use of SMIs. Legacy ISA devices and
USB are usually good candidates. If that does not help, don't use it
for real-time :)

Thanks,

	tglx

  reply	other threads:[~2009-01-24 16:30 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 [this message]
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
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=alpine.LFD.2.00.0901241716540.3424@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=jcm@redhat.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --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