From: Clark Williams <williams@redhat.com>
To: Bastien ROUCARIES <roucaries.bastien@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
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>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Subject: Re: [RT] [RFC] simple SMI detector
Date: Sun, 25 Jan 2009 09:04:54 -0600 [thread overview]
Message-ID: <20090125090454.753c05dd@torg> (raw)
In-Reply-To: <195c7a900901250349t6c0cdc73gdbd71a9f87151d72@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 25 Jan 2009 12:49:18 +0100
Bastien ROUCARIES <roucaries.bastien@gmail.com> wrote:
> On Sun, Jan 25, 2009 at 10:40 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > 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 :)
>
Except for the fact that linuxcore is unaware of the specific
requirements a particular motherboard has for thermal management.
Turning off SMI's unconditionally is a *bad* idea. Better to start
telling hardware vendors that we can't use their platform because of
unexplained latencies (which we presume to be SMI's).
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
iEYEARECAAYFAkl8f5oACgkQHyuj/+TTEp0JuwCfQaaugU+MY8nWHKsvXuVNmE6X
IEYAoMFn70BK9NczzHI1XnnQwy7bx/Ja
=aRKl
-----END PGP SIGNATURE-----
WARNING: multiple messages have this Message-ID (diff)
From: Clark Williams <williams@redhat.com>
To: Bastien ROUCARIES <roucaries.bastien@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
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>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Subject: Re: [RT] [RFC] simple SMI detector
Date: Sun, 25 Jan 2009 09:04:54 -0600 [thread overview]
Message-ID: <20090125090454.753c05dd@torg> (raw)
In-Reply-To: <195c7a900901250349t6c0cdc73gdbd71a9f87151d72@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=US-ASCII, Size: 1416 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 25 Jan 2009 12:49:18 +0100
Bastien ROUCARIES <roucaries.bastien@gmail.com> wrote:
> On Sun, Jan 25, 2009 at 10:40 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > 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 :)
>
Except for the fact that linuxcore is unaware of the specific
requirements a particular motherboard has for thermal management.
Turning off SMI's unconditionally is a *bad* idea. Better to start
telling hardware vendors that we can't use their platform because of
unexplained latencies (which we presume to be SMI's).
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
iEYEARECAAYFAkl8f5oACgkQHyuj/+TTEp0JuwCfQaaugU+MY8nWHKsvXuVNmE6X
IEYAoMFn70BK9NczzHI1XnnQwy7bx/Ja
=aRKl
-----END PGP SIGNATURE-----
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2009-01-25 15:05 UTC|newest]
Thread overview: 21+ 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 [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=20090125090454.753c05dd@torg \
--to=williams@redhat.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=roucaries.bastien@gmail.com \
--cc=sdietrich@novell.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.