From: Bastien ROUCARIES <roucaries.bastien@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Theodore Tso <tytso@mit.edu>,
Sven-Thorsten Dietrich <sdietrich@novell.com>,
Jon Masters <jcm@redhat.com>, 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 12:49:18 +0100 [thread overview]
Message-ID: <195c7a900901250349t6c0cdc73gdbd71a9f87151d72@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0901251035050.3424@localhost.localdomain>
On Sun, Jan 25, 2009 at 10:40 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Sat, 24 Jan 2009, Theodore Tso wrote:
>> On Sun, Jan 25, 2009 at 01:12:45PM +1100, Sven-Thorsten Dietrich wrote:
>> I will also note that for some applications (i.e., military hardware
>> running under battle conditions), where it might be that running the
>> hardware beyond its thermal limits might actually be *desirable*.
>> After all, an extra 15 minutes of running beyond thermal limits that
>> eventually causes the CPU to get flakey might be worth it if the
>> alternative is the ship getting sunk because the BIOS decided that
>> shutting down the CPU to save it from thermal damage was more
>> important than say, running the anti-aircraft guns....
>
> In that case the system designer knows exactly what he is doing and he
> is aware of the consequences.
>
> My concern about the SMI disable module is that it can damage Joe
> users hardware. I have at least two reports where the CPU got fried
> and some others where people got confused because chips started
> behaving weird and it took quite a time to figure out that they used
> the SMI disabler. A big fat warning about this code is definitely
> necessary.
>
> Thanks,
I suppose the non joe user could flash their motherboard with
linuxcore and therefore do not distrub by SMI :)
Regards
Bastien
next prev parent reply other threads:[~2009-01-25 11:49 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 [this message]
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=195c7a900901250349t6c0cdc73gdbd71a9f87151d72@mail.gmail.com \
--to=roucaries.bastien@gmail.com \
--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=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