public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
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
Date: Tue, 27 Jan 2009 13:00:42 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0901271249460.19655@localhost.localdomain> (raw)
In-Reply-To: <1232751312.3990.59.camel@perihelion.bos.jonmasters.org>

Is it possible that if the detector is running,
it may prevent (delay) the thing it is trying to detect?

Eg. some random AML gets interpreted by the kernel,
it needs to touch an MSR, but MSRs are not accessible
from AML, so it triggeres an SMI by touching a magic IO address
with a magic value.

So in this case, the random AML may not run until after
the detector has stopped running, because the detector
prevented some random user-space distro value-add
from polling the battery or the temperature or something...

The other example that comes to mind is that dreaded
USB PS/2 emulation done via SMM.

FWIW I detest SMM as much as any OS person should.
But I also acknowledge that it is virtually impossible to prevent
BIOS developers from giving it up.  We OS types have proposed an
"SMI has happened bit or counter" many times,
even though we'd rather have a "SMM disable" bit:-)

cheers,
--
Len Brown, Intel Open Source Technology Center

      parent reply	other threads:[~2009-01-27 18:00 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
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 [this message]

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.0901271249460.19655@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=jcm@redhat.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --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